7 Jan 2010 16:20
This Message is Untrusted
Milko Krachounov <milko <at> 3mhz.net>
2010-01-07 15:20:05 GMT
2010-01-07 15:20:05 GMT
You have asked your mail client to open this email message, but we can't confirm that its contents are friendly and polite. Normally, within a mailing list message, the sender would use kind words to prove that he is peaceful and loyal. However, this message contained tons of bitter words directed at the addressees, so the good intentions of the sender couldn't be verified. What Should I Do? If you usually read messages on this mailing list without problems, this error could mean that someone just got very angry at you because some of your latest moronic decisions, and you shouldn't continue. [Get me out of here!] Technical Details The mailing message contained 89 mild curse words, 17 strong curse words, and 4 curse words exceeding the threshold of pain. (Error code: sec_error_too_many_cursewords) I Understand the Risks If you understand what's going on, you can tell the mailing system to start trusting the sender by performing a short five-minute exorcism. You should do this for every message. *Even if you trust the sender, this error could mean that he still wants to insult you, attack you, nuke you from orbit or force you to listen to Rick Astley.* Don't do this unless you know for certain that the sender doesn't have a reason to come down rudely upon you.(Continue reading)
I would think that moving toward HTTP authentication schemes, such as
digest, would make it much easier to automate a good identity manager.
Would you agree?
> I have a quibble with your section on HTTPOnly cookies. By mentioning
> only IE by name when you follow with "other browsers have been slow to
> adopt this feature" people will naturally assume that includes Firefox,
> the only other browser with significant marketshare. Firefox has
> supported HTTPOnly since 2007. Although perhaps "slow" compared to when
> Microsoft invented the feature that's pretty irrelevant for a paper
> written three years later when nearly all Firefox users will have
> support for it.
>
> Continuing that quote with "and continue to have difficulties fully
> enforcing this rule in light of newer features (such as AJAX
I remembered the topic came up
on the httpbis mailing list recently so I went to see if they had
reached any kind of consensus in the group.
RSS Feed