Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Department of Defense Now Blocking HTML Email

Posted by Zonk on Sun Dec 24, 2006 04:20 PM
from the nuke-them-from-orbit-only-way-to-be-sure dept.
oKAMi-InfoSec writes "The Department of Defense (DoD) has taken the step of blocking HTML-based email. They are also banning the use of Outlook Web Access email clients. The DoD is making this move because HTML messages can easily be infected with spyware and executable lines of code that enable hackers to access DoD networks, according to an article in Federal Computer Week by Bob Brewin . A spokesman for the Joint Task Force for Global Network Operations (JTF-GNO) claims that this is a response to an increased network threat condition. The network threat condition has risen from Information Condition 5 to Information Condition 4 (also called Infocon 4). InfoCon 5 is normal operating conditions and Infocon 4 comes as a result of 'continuing and sophisticated threats' against DoD Networks. The change to Infocon 4 came in mid-November, after the Naval War College suffered devastating attacks that required their entire system be taken offline, but the JTF-GNO spokesman claims there is no connection."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • Good call (Score:5, Insightful)

    by MostAwesomeDude (980382) on Sunday December 24 2006, @04:22PM (#17355618) Homepage
    Reduced bandwidth, less entry vectors, less spam entering mailboxes. I guess the only losers are the people who send those annoying Flash giftcards through email.
    • Re: (Score:3, Informative)

      by Anonymous Coward
      I for one certainly don't miss the annoying pink backgrounds and purple text. But, you forget that a lot of internet based applications send out emails. So you should really include the developers in the losers category here.

      I don't know how many email templates I've gone though in the past week converting them to be plain text (where necessary). This mainly applies to processes that include sending tabular data to a person.
            • Re: (Score:3, Informative)

              you like your Italics, no?

              Bad typing. There's actually a <?i> instead of </i> at the end of the first line. Preview is pretty slow, I usually just wing it.

    • Too late... (Score:4, Funny)

      by myowntrueself (607117) on Sunday December 24 2006, @05:57PM (#17356194)
      the only losers are the people who send those annoying Flash giftcards through email

      Don't worry, they were already losers!

    • Re: (Score:3, Interesting)

      Yes, this was absolutely the right choice. I just wonder what took them so long!

      I also wonder when other organizations will follow suit.
    • My workplace recently did something similiar. I was never crazy about flashy colors and zillion font options. But I do miss the ability to send tables as part of the email. My job frequently involves info that is best represented in a table, and the ability to copy/paste a table into an email was very helpful. Even allowing for the limitations of plain text,

      Outlook did me the favor the other day of removing the "extra" line breaks, screwing up the already limited formatting I was stuck with. People

      • Re:Good call (Score:5, Interesting)

        by cluckshot (658931) on Monday December 25 2006, @08:25AM (#17359452)

        If you are DOD and you want to get Commercial Off the Shelf (COTS) products to resolve your problems without hiring the massively expensive solutions of 1 off stuff built to design, you must be able to accept attachments such as .zip and html mail. Sorry but the commercial guys cannot even tell you what they are doing anymore without this stuff. DOD costs just got higher!

        I worked one DOD site where we had to email files of code. The volume of the attachments was beyond the Email limits so we had to zip the files. The filters blocked .zip. So we renamed the files .aaa or something like that. Then the filters didn't catch the files. That way we could get the emails. We had to break our own security just to do our job. This stuff is a real problem.

        The US DOD needs to can Microsoft. If they were to run Linux or Apple systems and then to sandbox all emails and web browser stuff under the OS a lot could be done and things would be much more secure. The basic problem is a Microsoft logical design construct. Microsoft thought that they should own your computer and you should rent it from them. Under these conditions they wanted "their" computers to be remotely controlled by various means. The means they designed into their constructs also leave sucking security holes which hackers and other malware designers just walk right through.

        There is a real reason most DOD people stick like glue to Microsoft. For Network security people in the DOD they are as worried that some subordinate might actually control his machine as they are of having foreign control. (Foreign to their system) As such they must keep central control. This is the Microsoft construct at a second level. The DOD system I worked on had an entire base having one root password that didn't change folks because of this demand. Linux etc doesn't conform to this as naturally as MS systems. Another level of this sticking like glue to MS systems comes from the fact that most of the people who program (contractors etc) for the Government like to keep their jobs. MS systems do not support legacy software well. As such they are continually "re-inventing the wheel" so to speak and it makes for lots of jobs that last a lifetime. It holds the DOD hostage to continually hiring the same contractor because his software is proprietary and cannot be easily "reverse engineered" without risk of software copyright violations. In the end this synergy of profits and control leaves the US DOD bleeding money, never able to do its job as effectively and wedded to MS systems.

        If the taxpayers get involved they will ban such OS like Microsoft because this is completely contrary to the interest of the taxpayers. It however; requires the US DOD to recognize that its only true security lies in the loyalty of its people. In doing so it will have to retract from foreign (non-USA) suppliers and contractors. It will have to seriously look into who it is hiring and it will have to weed out those it has on payroll who are being more selfish than loyal. Let me assure you that if this situation is dealt with properly it will be a top to bottom 10 on the Richter Scale earthquake in US Government operations. Imagine if you will actually not being able to have the management read every document in someones computer without them knowing. Imagine having someone who works for you who you actually have to be able to trust! Imagine real government security! (WOW!)
  • As They Should (Score:5, Insightful)

    by deKernel (65640) <timfbarber@yahoo . c om> on Sunday December 24 2006, @04:26PM (#17355648)
    This I guess will just show my age, but I am soooo OK with this. Email should be just text, period. I personally believe that people should spend more time using complete sentences which includes punctuation and correct capitalization.

    I guess I should get back to chiseling my notes on stone slabs now.....
    • by theMerovingian (722983) on Sunday December 24 2006, @04:52PM (#17355808) Journal

      Email should be just text, period.

      In my day email was dashes and dots, and we liked it that way.

    • Re:As They Should (Score:5, Interesting)

      by MobileTatsu-NJG (946591) on Sunday December 24 2006, @04:53PM (#17355816)
      "Email should be just text, period."

      Personally I'd miss the formatting features of HTML. Bold, Italic, etc. I'm a little surprised there hasn't been a middle ground estbalished at some point. You know... pretty text, no exploits. Well, I can dream. In the mean time, gotta give kudos to GMail. One of my favorite features is that it disables images until you turn them on. That's a feature Outlook 2000 could have used.
      • When I first started using email, it was only within the company's WAN. Most people had exactly the same model of printer, so I figured out how to embed printer control characters into emails to make parts appear bold or in italics when printed (most employees printed out their email to read it at that time)
      • by Anonymous Coward on Sunday December 24 2006, @05:10PM (#17355916)
        Personally I'd miss the formatting features of HTML. Bold, Italic, etc. I'm a little surprised there hasn't been a middle ground estbalished at some point. You know... pretty text, no exploits. Well, I can dream.



        I think that you have /really/ hit the nail on the proverbial head there. To make plain text emails usable we need a STRONG and well defined _SYNTAX_ for visually communicating "text style". Until then, this email thing will _never_ catch on.
        • Re: (Score:3, Insightful)

          you know i use to read /. for the interesting perspectives of the fellow geeks on here, but i've given up. I now read it for the comedians. wish i had my mod points.
        • Re: (Score:3, Interesting)

          I think that you have /really/ hit the nail on the proverbial head there. To make plain text emails usable we need a STRONG and well defined _SYNTAX_ for visually communicating "text style". Until then, this email thing will _never_ catch on.

          LOL. If the OP wants bold and underlining in his emails, I'd suggest he starts with reading

          T^HTh^Hhe^He M^HMu^Hut^Htt^Ht E^HE-^H-M^HMa^Hai^Hil^Hl^HCl^Hli^Hie^Hen^Hnt^Ht

          Personally, I'd find that annoying, like every other attempt to be interesting, or creative or otherw
      • Re: (Score:3, Interesting)

        Personally I'd miss the formatting features of HTML. Bold, Italic, etc. I'm a little surprised there hasn't been a middle ground estbalished at some point.

        You should be aware that there has been such a format [wikipedia.org] for quite a while, using the MIME type of text/enriched. I used to receive quite a few emails that used it (no, I don't remember what the originating client was and I'm not interested in looking it up right now) but it never seemed to catch on more widely. (At a wild guess, that's because Outlook didn'

      • As an old boss once used to say, when presented with options - "Do Both!"

        I read all my e-mail as "plain text". After all, HTML is plain-text too.

        95% of the time that is all you need. Yeah, I can see they marked it italics or bold, but they are the same words.

        If, after looking at the "raw" text, and I really think the formatting will convey some additional info, I might look at it as "html". Looking at the raw text gives you a pretty good idea if there is anything sinister about it.

        In my experience,

    • But I just finished writing this inspirational xmas email in 32-point Comic Sans font with animated gifs of kittens and reindeer and attached 30-meg screensaver that I was going to sent to Everyone@dod.gov
    • All I can say is, the war in Iraq must be going really badly if the DoD is this desperate for additional recruits.
  • At least then people will know why their email never got through. So many people use HTML email without being aware of it and don't realize that's what makes formatting possible.

    Although the focus is on Outlook, it seems like there's an outside chance there may be other clients and web interfaces (namely all of them) that are vulnerable to most of the same problems....
  • Stupid (Score:3, Interesting)

    by Nicopa (87617) <nick@noSPAM.reloco.com.ar> on Sunday December 24 2006, @04:33PM (#17355686)
    That's stupid. The problem is not with HTML mail (which is generated by many people unknowingly). They could just standarize in a safe mail program, with some mandatory defaults. They could force the use of a modified version of Thunderbird forcing the (already existing) oprion of "Disable JavaScript" off. Another interesting Thunderbird feature is the ability to "sanitize HTML", that is, remove from the HTML view anything that isn't strictly formatting (paragraphs, bullet lists, etc.).
    • Re:Stupid (Score:5, Insightful)

      by Beryllium Sphere(tm) (193358) on Sunday December 24 2006, @04:40PM (#17355744) Homepage Journal
      But even without Javascript there are still web bugs, image file parsing exploits, and remember what engine is probably parsing the HTML on a Windows client. A "safe" email client is one that disables most of the features of HTML, and unless it's guaranteed to catch everything dangerous then it's safer to prevent HTML in the first place.

      Up-to-date patches would mitigate those, but do you think somebody might be saving some zero-days for the DoD?
    • No, it's not stupid.... doing nothing is stupid. The simple fact remains. No matter what client your using, be it proprietary or some open source variety all the nastiest that can be placed in HTML is simply a hassle to block. Sure you can run things like spamassassin, razor and any number of things but those are just extra things that have to be maintained, updated, etc. The simplest is to dump HTML altogether. I have never been a fan of HTML email because it's a colossal waste of bandwith.
    • What's stupid is that they were not aware of the obviously better solution you know of. That's where targeted information needs to be supplied. Google is everyone's friend but sometimes it's still not easy enough to find the answers to your specific situation. The challenge being connecting the right answers with unknown information in the search queries. Google's next biggest challenge is finding what you didn't know you needed!
        • Wow. Everytime I read a comment like the stupid trash you just posted it makes me want to scream DO YOU KNOW WHAT THE FUCK EMAIL IS? Why do Windows users feel it necessary to cram 50 different applications' functions into one super crappy, insecure piece of bloatware and then rave on about how superior it is? Me, personally, I'm using mutt in an enterprise environment because I'm just crazy enough to believe you should read email with, you know, a fucking email client.
    • No. Its the KISS principle. Code complexity itself endangers security.

      Rendering engines aren't rewritten frequently. Typically the code you have available for reuse supports many features you don't want: embedding, javascript, images (don't forget the GDI exploit). It is true that you can provide knobs to disable these dangerous features in the rendering engine. *BUT* have you ever been involved in real software verification efforts? Too many knobs means too little coverage.

      Writing good tests is hard.
    • Re: (Score:3, Interesting)

      There are ways in HTML email of inserting 1-pixel transparent gifs which have unique load addresses based on who opens the email so that the sender know which people they mail read it. That's how spammers know if you open the spam they send. It's a sort of tracking cookie image.
  • If the DoD cannot find a solution to this kind of email, they should outsource its management to countries like India and Russia. Isn't it true that a good amount of our defense contracts are outsourced?
    • If the DoD cannot find a solution to this kind of email, they should outsource its management to countries like India and Russia. Isn't it true that a good amount of our defense contracts are outsourced?

      Um, they just did enact a solution.

      And, no. You don't really have Indian outsourcing operations involved in the day-to-day admin of communications to and from the Pentagon. No.
  • by erroneus (253617) on Sunday December 24 2006, @04:36PM (#17355718) Homepage
    That's as obvious as the department of homeland security closing the borders!

    I applaud the effort, but why did they take so long to wise up even this much?
  • by Sepodati (746220) on Sunday December 24 2006, @04:43PM (#17355758) Homepage
    Although vanilla access to OWA is being blocked, there are still ways to get to your email from outside of the network (mainly what OWA was used for, anyhow). You can VPN into the network, log on to OWA using your CAC (common access card, smart card, etc), use your Blackberry (assuming your rank is high enough to get one ;)).

    So instead of just plain old OWA sitting out there waiting for anyone to type in a username and password, they've upped the security a little bit. Yes, it's making us jump through hoops a little (for myself, need to stand up an ASA5510 as a VPN concentrator to receive outside connections), but it's not impossible.

    Besides... not being able to check your work email from home can only be a good thing, no?? I know, I know, it's for people on travel, leave, etc. too...

    As for the "blocking" of HTML email, can't say that I've seen that at all. Maybe it's only for emails that originate from outside of the network since we use HTML email all the time from within Outlook (formatting is useful in this case).

    ---John Holmes...
  • As long as stupid users dictate policy (and it always seems to be the most idiotic, uninformed, timetable pounding and ego-blinded of all users usually are in the upper echelons of an organization), security problems do to software choice will prevail. This is how microsnot products usually get pushed into an organization. Score one for the DoD getting rid of freaking html-mail and outhouse web access. One can only hope they s**tcan ms-exchange while they're at it.
  • Good! (Score:5, Informative)

    by porkThreeWays (895269) on Sunday December 24 2006, @04:51PM (#17355806)
    Good! HTML email is very annoying. Most of the time it doesn't display as intended anyway. Many clients will only support a safer reduced set of html thus only parts of the page will display properly. This makes the page even harder to decipher. HTML email is really only useful for spammers and advertisers usually anyway. If something needs to be that heavily formatted, attach it as a word processor document. If you can't get a basic idea across in plain-text, then the problem probably isn't because you are missing your bold tag.
  • Temporary? (Score:5, Interesting)

    by Bluesman (104513) on Sunday December 24 2006, @04:52PM (#17355812) Homepage
    This appears to be a temporary measure based on the current threat level.

    If the Infocon levels work anything like the other readiness levels in the DoD, then a shift to Infocon 4 requires a change (temporary) in policy. So it seems that a shift back to level 5 would mean HTML e-mail is no longer blocked.

    It's like after 9-11, when all DoD installations had much stricter physical access rules and extra guards at the gates.

    Which is a shame, because saying goodbye to html email entirely would be fine by me.
  • I work as a contractor to the Navy, and we received e-mails a few weeks back saying that HTML e-mail would no longer be allowed. However, they weren't blocking it, merely converting anything that was HTML to plain-text or RTF. I've not tested by sending an HTML e-mail to my .mil address (gonna try that in a few minutes), but I don't think they're actually blocking it.
  • I determined a couple of years ago that in order for the small IT department of one (me), to be able to keep up with potential Outlook security problems, I had to filter HTML down to Plain Text. When you've got a program that can be used to infect a computer just be previewing a message, you have to do _something_. Now that we've install Exchange (bleh), internal messages are no longer filtered, but thankfully the old filters for stuff going in (and out) of the company remain in use.
  • If you know how to use HTML, you should know how to be able to write an email without using any HTML.

    If you don't know how to use HTML, you shouldn't use it, period.
  • HTML wouldn't be such an exploitable thing with e-mail if Microsoft's mail software weren't so full of holes. If Outlook/Exchange is really that important to some organizations, why not offer support for [b]internal[/b] mail to be sent in Microsoft Word format?

  • I block html email myself simply because it is annoying and 90+% is spam anyway. Why is this a problem?
  • by LibertineR (591918) on Sunday December 24 2006, @06:01PM (#17356212)
    Folks, the DOD is NOT blocking HTML mail, just converting it to plain text and disabling scripts, something ANY Exchange admin should already be doing in addition to Sender ID.

    Instead of facts, we get just another bash Microsoft thread. Figures.

  • by truckaxle (883149) on Sunday December 24 2006, @06:09PM (#17356246) Homepage
    Any here that are forced to use the NMCI (Navy/Marine Corps Intranet) network know that reading any email at all can be a challenge.

    A NMCI laptop takes over 10 minutes to boot and load the dozens of background processes and roving preferences. Once booted the machine is near useless performance wise.

    Most, including middle management, refer to NMCI as No More Computing In-house.

    In order to get idea just how bad things are, upper management conducted "customer satisfaction surveys". Even though the NMCI program office controlled the content, distribution, and analysis of the survey the results indicated overwhelming dissatisfaction. The NMCI program office has declined to release the raw data from the survey, instead issuing a release about the results. Rear Admiral J. B. Godwin III said releasing the results would challenge the "integrity of our data." Hmmm....

    Most Navy labs that are under the burden of the NMCI contract maintain two networks, the legacy and the NMCI - the one to get work done on an the other to read email. This leads to double the costs and double the vulnerability exposure, and halves the resources to concentrate on security and usability.

    Worst I hear that the Navy just extended the contract to 2010. Your tax dollars at work.

  • From: Donald Rumsfield
    To: General Whosit
    Subject: My final Orders

    This email contains a computer trogan.

    You are so pwned!!!

    Sincerely
    Osama Bin Ladin.
    ____

    Yeah... Typos are on purpose

    • by commodoresloat (172735) * on Sunday December 24 2006, @04:48PM (#17355784) Homepage
      Put the pictures on a web page and send your friends a link to the web page. I can't stand getting pictures via email. If you must show me a photo of your new kid, put it on a website and send me the link. I still won't look at it, but I'll respond telling you how cute he/she is and we will both feel better. As for bulleted lists,

      * what
      * the
      * hell
      * is
      * wrong
      * with
      * asterisks?
        • by commodoresloat (172735) * on Sunday December 24 2006, @06:26PM (#17356342) Homepage
          I don't see the point of taking security risks and wasting bandwidth on email that "looks nicer." You want a nice looking email, format it as a webpage, and send your friend a link to the web page. Or print it out and stick it in the post box. My email program is instructed to display all email as text only and if it is full of crappy html that isn't filtered out, I hope it wasn't an important email because I deleted it. But I shouldn't have to bother; this junk should be filtered out at the server level and I'm glad the DoD at least recognizes that email security is more important than how nice it looks. I only wish my university would do the same :) Don't get me wrong, I love html, but it's not made for pretty-ing up email. It's made for hyper-text, which email should not be. Most email programs allow you to follow links that are part of an email message pretty easily, so what's wrong with sending the link to your browser?