Fort Benning, Georgia

John Simkin · February 17, 2010

I have just tried to visit the Fort Benning website.

https://www.benning.army.mil/

I got the following message:

"The security certificate presented by this website was not issued by a trusted certificate authority."

Evan Burton · February 17, 2010

I have just tried to visit the Fort Benning website.
https://www.benning.army.mil/

I got the following message:

"The security certificate presented by this website was not issued by a trusted certificate authority."

Ditto

David G. Healy · February 17, 2010

I have just tried to visit the Fort Benning website.
https://www.benning.army.mil/

I got the following message:

"The security certificate presented by this website was not issued by a trusted certificate authority."

perhaps its been hacked?

Evan Burton · February 18, 2010

The US was conducting an exercise yesterday, a simulated cyber-attack.

That might have something to do with it but I still get the untrusted warning.

February 18, 2010

I guess the US army is uninterested in fixing the problem, as the article describing it is 18 months old. I get the same result as those who posted here prior to this post, and I have a southern US IP address.

http://royal.pingdom.com/2008/08/19/new-ss...sands-of-sites/

Michael Hogan · February 18, 2010

I have just tried to visit the Fort Benning website.
https://www.benning.army.mil/

I got the following message:

"The security certificate presented by this website was not issued by a trusted certificate authority."

I was able to access the website by selecting the "Continue to this website (not recommended)" option.

John Dolva · February 18, 2010

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE html [

<!ENTITY % htmlDTD

PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"

"DTD/xhtml1-strict.dtd">

%htmlDTD;

<!ENTITY % globalDTD

SYSTEM "chrome://global/locale/global.dtd">

%globalDTD;

<!ENTITY % certerrorDTD

SYSTEM "chrome://browser/locale/aboutCertError.dtd">

%certerrorDTD;

<!-- These strings are used by Firefox's custom about:certerror page,

a replacement for the standard security certificate errors produced

by NSS/PSM via netError.xhtml. -->

<!ENTITY certerror.pagetitle "Untrusted Connection">

<!ENTITY certerror.longpagetitle "This Connection is Untrusted">

<!-- Localization note (certerror.introPara1) - The string "#1" will

be replaced at runtime with the name of the server to which the user

was trying to connect. -->

<!ENTITY certerror.introPara1 "You have asked &brandShortName; to connect

securely to <b>#1</b>, but we can't confirm that your connection is secure.">

<!ENTITY certerror.introPara2 "Normally, when you try to connect securely,

sites will present trusted identification to prove that you are

going to the right place. However, this site's identity can't be verified.">

<!ENTITY certerror.whatShouldIDo.heading "What Should I Do?">

<!ENTITY certerror.whatShouldIDo.content "If you usually connect to

this site without problems, this error could mean that someone is

trying to impersonate the site, and you shouldn't continue.">

<!ENTITY certerror.getMeOutOfHere.label "Get me out of here!">

<!ENTITY certerror.expert.heading "I Understand the Risks">

<!ENTITY certerror.expert.content "If you understand what's going on, you

can tell &brandShortName; to start trusting this site's identification.

<b>Even if you trust the site, this error could mean that someone is

tampering with your connection.</b>">

<!ENTITY certerror.expert.contentPara2 "Don't add an exception unless

you know there's a good reason why this site doesn't use trusted identification.">

<!ENTITY certerror.addException.label "Add Exception…">

<!ENTITY certerror.technical.heading "Technical Details">

]>

<!-- ***** BEGIN LICENSE BLOCK *****

- Version: MPL 1.1/GPL 2.0/LGPL 2.1

-

- The contents of this file are subject to the Mozilla Public License Version

- 1.1 (the "License"); you may not use this file except in compliance with

- the License. You may obtain a copy of the License at

- http://www.mozilla.org/MPL/

-

- Software distributed under the License is distributed on an "AS IS" basis,

- WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License

- for the specific language governing rights and limitations under the

- License.

-

- The Original Code is netError.xhtml.

-

- The Initial Developer of the Original Code is

- Netscape Communications Corporation.

-

- Contributor(s):

- Adam Lock <adamlock@netscape.com>

- William R. Price <wrprice@alumni.rice.edu>

- Henrik Skupin <mozilla@hskupin.info>

- Jeff Walden <jwalden+code@mit.edu>

- Johnathan Nightingale <johnath@mozilla.com>

- Ehsan Akhgari <ehsan.akhgari@gmail.com>

-

- Alternatively, the contents of this file may be used under the terms of

- either the GNU General Public License Version 2 or later (the "GPL"), or

- the GNU Lesser General Public License Version 2.1 or later (the "LGPL"),

- in which case the provisions of the GPL or the LGPL are applicable instead

- of those above. If you wish to allow use of your version of this file only

- under the terms of either the GPL or the LGPL, and not to allow others to

- use your version of this file under the terms of the MPL, indicate your

- decision by deleting the provisions above and replace them with the notice

- and other provisions required by the LGPL or the GPL. If you do not delete

- the provisions above, a recipient may use your version of this file under

- the terms of any one of the MPL, the GPL or the LGPL.

-

- ***** END LICENSE BLOCK ***** -->

<head>

<title>Untrusted Connection</title>

<!-- This page currently uses the same favicon as neterror.xhtml.

If the location of the favicon is changed for both pages, the

FAVICON_ERRORPAGE_URL symbol in toolkit/components/places/src/nsFaviconService.h

should be updated. If this page starts using a different favicon

than neterrorm nsFaviconService->DoSetAndLoadFaviconForPage

should be updated to ignore this one as well. -->

// Error url MUST be formatted like this:

// about:certerror?e=error&u=url&d=desc

// Note that this file uses document.documentURI to get

// the URL (with the format from above). This is because

// document.location.href gets the current URI off the docshell,

// which is the URL displayed in the location bar, i.e.

// the URI that the user attempted to load.

function getCSSClass()

{

var url = document.documentURI;

var matches = url.match(/s\=([^&]+)\&/);

// s is optional, if no match just return nothing

if (!matches || matches.length < 2)

return "";

// parenthetical match is the second entry

return decodeURIComponent(matches[1]);

}

function getDescription()

{

var url = document.documentURI;

var desc = url.search(/d\=/);

// desc == -1 if not found; if so, return an empty string

// instead of what would turn out to be portions of the URI

if (desc == -1)

return "";

return decodeURIComponent(url.slice(desc + 2));

}

function initPage()

{

// Replace the "#1" string in the intro with the hostname. Trickier

// than it might seem since we want to preserve the <b> tags, but

// not allow for any injection by just using innerHTML. Instead,

// just find the right target text node.

var intro = document.getElementById('introContentP1');

function replaceWithHost(node) {

if (node.textContent == "#1")

node.textContent = location.host;

else

for(var i = 0; i < node.childNodes.length; i++)

replaceWithHost(node.childNodes);

};

replaceWithHost(intro);

if (getCSSClass() == "expertBadCert") {

toggle('technicalContent');

toggle('expertContent');

}

var tech = document.getElementById("technicalContentText");

if (tech)

tech.textContent = getDescription();

addDomainErrorLink();

}

/* In the case of SSL error pages about domain mismatch, see if

we can hyperlink the user to the correct site. We don't want

to do this generically since it allows MitM attacks to redirect

users to a site under attacker control, but in certain cases

it is safe (and helpful!) to do so. Bug 402210

*/

function addDomainErrorLink() {

// Rather than textContent, we need to treat description as HTML

var sd = document.getElementById("technicalContentText");

if (sd) {

var desc = getDescription();

// sanitize description text - see bug 441169

// First, find the index of the <a> tag we care about, being careful not to

// use an over-greedy regex

var re = /<a id="cert_domain_link" title="([^"]+)">/;

var result = re.exec(desc);

if(!result)

return;

// Remove sd's existing children

sd.textContent = "";

// Everything up to the link should be text content

sd.appendChild(document.createTextNode(desc.slice(0, result.index)));

// Now create the link itself

var anchorEl = document.createElement("a");

anchorEl.setAttribute("id", "cert_domain_link");

anchorEl.setAttribute("title", result[1]);

anchorEl.appendChild(document.createTextNode(result[1]));

sd.appendChild(anchorEl);

// Finally, append text for anything after the closing </a>

sd.appendChild(document.createTextNode(desc.slice(desc.indexOf("</a>") + "</a>".length)));

}

var link = document.getElementById('cert_domain_link');

if (!link)

return;

var okHost = link.getAttribute("title");

var thisHost = document.location.hostname;

var proto = document.location.protocol;

// If okHost is a wildcard domain ("*.example.com") let's

// use "www" instead. "*.example.com" isn't going to

// get anyone anywhere useful. bug 432491

okHost = okHost.replace(/^\*\./, "www.");

/* case #1:

* example.com uses an invalid security certificate.

*

* The certificate is only valid for www.example.com

*

* Make sure to include the "." ahead of thisHost so that

* a MitM attack on paypal.com doesn't hyperlink to "notpaypal.com"

*

* We'd normally just use a RegExp here except that we lack a

* library function to escape them properly (bug 248062), and

* domain names are famous for having '.' characters in them,

* which would allow spurious and possibly hostile matches.

*/

if (endsWith(okHost, "." + thisHost))

link.href = proto + okHost;

/* case #2:

* browser.garage.maemo.org uses an invalid security certificate.

*

* The certificate is only valid for garage.maemo.org

*/

if (endsWith(thisHost, "." + okHost))

link.href = proto + okHost;

// If we set a link, meaning there's something helpful for

// the user here, expand the section by default

if (link.href && getCSSClass() != "expertBadCert")

toggle("technicalContent");

}

function endsWith(haystack, needle) {

return haystack.slice(-needle.length) == needle;

}

function toggle(id) {

var el = document.getElementById(id);

if (el.getAttribute("collapsed"))

el.removeAttribute("collapsed");

else

el.setAttribute("collapsed", true);

}

]]></script>

</head>

<body dir="ltr">

<div id="errorPageContainer">

<div id="errorTitle">

<h1 id="errorTitleText">This Connection is Untrusted</h1>

</div>

<div id="errorLongContent">

<div id="introContent">

<p id="introContentP1">You have asked Firefox to connect

securely to <b>www.benning.army.mil</b>, but we can't confirm that your connection is secure.</p>

<p>Normally, when you try to connect securely,

sites will present trusted identification to prove that you are

going to the right place. However, this site's identity can't be verified.</p>

</div>

<div id="whatShouldIDoContent">

<h2>What Should I Do?</h2>

<div id="whatShouldIDoContentText">

<p>If you usually connect to

this site without problems, this error could mean that someone is

trying to impersonate the site, and you shouldn't continue.</p>

<xul:button xmlns:xul="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul" id="getMeOutOfHereButton" label="Get me out of here!"/>

</div>

<!-- The following sections can be unhidden by default by setting the

"browser.xul.error_pages.expert_bad_cert" pref to true -->

<div id="technicalContent" collapsed="true">

<h2 onclick="toggle('technicalContent');" id="technicalContentHeading">Technical Details</h2>

<p id="technicalContentText">www.benning.army.mil uses an invalid security certificate.

The certificate is not trusted because the issuer certificate is unknown.

(Error code: sec_error_unknown_issuer)

</p>

</div>

<div id="expertContent" collapsed="true">

<h2 onclick="toggle('expertContent');" id="expertContentHeading">I Understand the Risks</h2>

<div>

<p>If you understand what's going on, you

can tell Firefox to start trusting this site's identification.

<b>Even if you trust the site, this error could mean that someone is

tampering with your connection.</b></p>

<p>Don't add an exception unless

you know there's a good reason why this site doesn't use trusted identification.</p>

<xul:button xmlns:xul="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul" id="exceptionDialogButton" label="Add Exception…"/>

</div>

<!--

- Note: It is important to run the script this way, instead of using

- an onload handler. This is because error pages are loaded as

- LOAD_BACKGROUND, which means that onload handlers will not be executed.

-->

<script type="application/x-javascript">initPage();</script>

</body>

</html>

John Dolva · February 18, 2010

http://www.army.mil/news/jumparchive/benning/

add: http://www.army.mil/-news/2010/02/11/34321...to-get-it-done/

Edited February 18, 2010 by John Dolva

February 18, 2010

http://www.army.mil/news/jumparchive/benning/
add: http://www.army.mil/-news/2010/02/11/34321...to-get-it-done/

John,

One problem is also that the two links you posted, begin with "http", not "https", which is the prefix that the Ft. Benning URL requires:

http://www.google.com/#hl=en&safe=off&...95f0d161f018361
he United States Army | Fort Benning

- 3:30am

Benning, MCOE, Maneuver Center, Armor, Infantry, schools at Benning, Basic Training, Airborne, Ranger, OCS, Army.

https://www.benning.army.mil/ -

John Dolva · February 19, 2010

Yes. Curious. Which is the dummy gateway?

Sign In

Fort Benning, Georgia

Recommended Posts

John Simkin

Evan Burton

David G. Healy

Evan Burton

Guest Tom Scully

Michael Hogan

John Dolva

John Dolva

Guest Tom Scully

John Dolva

Please sign in to comment

Browse

Activity

Support

Store