full-disclosure - Re: %5BFull-disclosure%5D%2018%20ways%20to%20escalate%20privileges%20in%20Zone%20Labs%0A%09ZoneAlarm%20Security%20Suite%20build%206.1.744.000&In-Reply-To=

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <dupdci$t8d$1@sea.gmane.org>
Date: Thu Mar  9 14:19:12 2006
From: davek_throwaway at hotmail.com (Dave Korn)
Subject: 
	Re: %5BFull-disclosure%5D%2018%20ways%20to%20escalate%20privileges%20in%20Zone%20Labs%0A%09ZoneAlarm%20Security%20Suite%20build%206.1.744.000&In-Reply-To=

Reed Arvin wrote:
> It appears that some of the characters in the previous post were not
> "HTML safe". The original article can be found at: <a
> href="http://reedarvin.thearvins.com/20060308-01.html">http://reedarvin.thearvins.com/20060308-01.html</a>

  If you check the list archive, you see that it's fine in the original:

http://lists.grok.org.uk/pipermail/full-disclosure/2006-March/042813.html

It also arrived unmangled at gmane.

http://permalink.gmane.org/gmane.comp.security.full-disclosure/41830

  Where are you seeing this URL-encoding?  I think your mailer must have 
borked it on receipt rather than on sending.  Do you still see it when you 
view the source?

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....