Date: Wed, 19 Jan 2011 23:18:23 +0000 From: Freddie Witherden <freddie@...herden.org> To: john-users@...ts.openwall.com Subject: Re: Plain Text/No-op Password Format On 19/01/11 23:02, Solar Designer wrote: > 4. URL-like %-encoding. That is, always encode chars that need encoding > (only the percent and the colon characters), but optionally encode any > other characters as well. Maybe this brings us the best of both worlds > because it lets us use either the substitution approach (just substitute > the two "bad" characters) or the encode-all approach. It also allows > for embedded and encoded linefeeds and terminal control characters. The > prefix could be "$plain$" or maybe "$percent$" or even "$%$". URL encoding is quite nice and easy to procure from either `perl` or `curl`. IIRC it also allows one to be quite aggressive with regards to whitespace ' ' => %20. Regards, Freddie. Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.