64th inert character

64th inert character

Secure Home | Search | About
 General Computer Security    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content add this group's latest topics to your Google content
Subject Author Date
64th inert character Mike - EMAIL IGNORED 05-07-2005
Posted by Mike - EMAIL IGNORED on May 7, 2005, 3:14 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
As far as I know, these characters are inert, in that
they have no interpretation on must systems or the net.
I represent them as a regex: [a-zA-Z0-9_].
That is 63 characters. To create a base 64 encoding, I
need one more. Any suggestions?
Mike.


Posted by Walter Roberson on May 7, 2005, 7:28 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
:As far as I know, these characters are inert, in that
:they have no interpretation on must systems or the net.

No interpretation as special control characters, I think you
mean. Not entirely true, in that in Unix systems using the
older traditional "line discipline", _ is a delete character.

:I represent them as a regex: [a-zA-Z0-9_].
:That is 63 characters. To create a base 64 encoding, I
:need one more. Any suggestions?

http://www.freesoft.org/CIE/RFC/1521/7.htm

Uses [a-zA-Z0-9+/] with = as the pad.
--
Oh, to be a Blobel!


Similar ThreadsPosted
Brute Force Attack Password Discovery With Defined Character Set March 1, 2008, 1:02 pm

The site map in XML format XML site map

Contact Us | Privacy Policy