Leythos said:
In the way that I view it, you are mixing two things and not just
looking at one.
I don't like HTML email because of the exploits that are available in
the application that some users choose to use. This does not make
HTML itself malicious, only the scripting embedded in it, and the
intent. If the exploit was not available, the embedded script would
be of no consequence.
You still aren't reading the posts that you are replying to. HTML can be
used to knock your machine over, without any script being involved.
Actually, you can configure XP to open an HTML file in any
application you want, Word, NotePad, DreamWeaver, IE, FireFox, VS.Net
IDE, etc...
Big deal, it sounds as if youve discovered the XP equivalent of the
"File Types" taskbar tab from earlier versions of Windows. The question
was: Does your OS, however you have it configured, launch HTML in a
vulnerable application, or in a text-editor?
look at it from this angle, since the Exploit we're talking about is
something that impacts Outlook/OE and IE, do you see MS sending out
service patches for HTML to the world? No, they are patching
exploits in the applications.
And are they patching Notepad? Answer: not to my knowledge. They are
expecting the HTML vulnerabilities to be a bit more problematic for
people who open HTML documents with an HTML renderer.
You could click on a link on the web that takes you directly to the
script,
What ****ing script? I gave you two links to current vulnerabilities,
with exploits in the field, that rely on nothing more than HTML/1.0 - no
script, no executables. You have ignored them; you appear to be arguing
with yourself, so why are you posting your comments as replies to my posts?
I think I'm being trolled, and I'm guess I'm going to have to do the
appropriate thing.
without ANY HTML IN THE LINK, and it would run the script if you
didn't have a secure browser. Now, take the script of of the HTML,
try the same thing, nothing to worry about. HTML is only what get's
blamed, it's the script and the exploit in the browser. In the case
of an IFRAME exploit, again, it's an exploit, not a flaw in HTML.
Damn, you're sharp! How did you figure out that an exploit is an exploit?
The question is, does the exploit target your email client, your
text-viewer, or the HTML renderer that the email client relies on to
render HTML-formatted messages?
BTW: I've never said there was a 'flaw' in HTML. But I take the view
that HTML in email is unnecessary and stupid; and sending a multipart
MIME email message with just one part - text/html - is rude, spammy and
not acceptable here, since my email client is set to not render HTML.
(Kiddies, that means something like "MrDemeanour has left the chatroom")