Roy Smith wrote:
> In article <[EMAIL PROTECTED]>,
> Steve Holden <[EMAIL PROTECTED]> wrote:
>
>> Of course, but ROT13 ^ (2n*1) is equivalent to ROT13 for all positive
>> integer n.
>
> Why restrict that to positive integers? I believe it works for all
> integers. But I do think you meant 2n
In article <[EMAIL PROTECTED]>,
Steve Holden <[EMAIL PROTECTED]> wrote:
> Of course, but ROT13 ^ (2n*1) is equivalent to ROT13 for all positive
> integer n.
Why restrict that to positive integers? I believe it works for all
integers. But I do think you meant 2n+1, not 2n*1.
--
http://mail.p
David H Wild wrote:
> In article <[EMAIL PROTECTED]>,
>Steven D'Aprano <[EMAIL PROTECTED]> wrote:
>>> I really don't recommend the ROT13 cipher, as this is extremely easy to
>>> crack. Most grade school kids could break this one in seconds. ;-)
>
>
>> I think you missed the point. Any recom
In article <[EMAIL PROTECTED]>,
Steven D'Aprano <[EMAIL PROTECTED]> wrote:
> > I really don't recommend the ROT13 cipher, as this is extremely easy to
> > crack. Most grade school kids could break this one in seconds. ;-)
> I think you missed the point. Any recommendation to use ROT13 is lik
On Tue, 19 Feb 2008 09:25:52 -0700, Brian wrote:
> Hi Erik,
>
> I really don't recommend the ROT13 cipher, as this is extremely easy to
> crack. Most grade school kids could break this one in seconds. ;-)
I think you missed the point. Any recommendation to use ROT13 is likely
to be a joke. A
Hi Erik,
I really don't recommend the ROT13 cipher, as this is extremely easy to
crack. Most grade school kids could break this one in seconds. ;-)
If the project that you are working upon has low security needs, (in
other words, it's not a financial institution), than you might try
somethin
Lie wrote:
> There is a simple encryption, called ROT13 (Rotate 13). This is
> very unsecure for any cryptographical purpose,
For enhanced security use TROT13 (triple ROT13).
> but enough to make uninformed user to think it's just a random
> piece of letters.
Security by obscurity doesn't wor
On Feb 12, 2:45 am, erikcw <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm trying to devise a scheme to encrypt/obfuscate a short string that
> basically contains the user's username and record number from the
> database. I'm using this encrypted string to identify emails from a
> user. (the string will
erikcw <[EMAIL PROTECTED]> writes:
> In essence what I'm doing is trying to manage tickets for a helpdesk.
> I want the ticket identifier to be short enough to fit in the subject
> line along with the normal subject chosen by the user.
I think you should use a database to maintain the email addre
On Feb 11, 4:19 pm, erikcw <[EMAIL PROTECTED]> wrote:
> On Feb 11, 4:07 pm, [EMAIL PROTECTED] wrote:
> > erikcw napisal(a):> But that can't be reversed, right? I'd like to be able
> > to decrypt the
> > > data instead of having to store the hash in my database...
>
> > In such case it seems you ha
En Mon, 11 Feb 2008 19:19:00 -0200, erikcw <[EMAIL PROTECTED]>
escribió:
> In essence what I'm doing is trying to manage tickets for a helpdesk.
> I want the ticket identifier to be short enough to fit in the subject
> line along with the normal subject chosen by the user. So
> cryptographic se
Hi,
On 2/11/08, erikcw <[EMAIL PROTECTED]> wrote:
> In essence what I'm doing is trying to manage tickets for a helpdesk.
> I want the ticket identifier to be short enough to fit in the subject
> line along with the normal subject chosen by the user. So
> cryptographic security isn't really impor
On Feb 11, 4:07 pm, [EMAIL PROTECTED] wrote:
> erikcw napisal(a):> But that can't be reversed, right? I'd like to be able to
> decrypt the
> > data instead of having to store the hash in my database...
>
> In such case it seems you have no choice but to use a symmetric
> encryption algorithm - in
erikcw napisal(a):
> But that can't be reversed, right? I'd like to be able to decrypt the
> data instead of having to store the hash in my database...
In such case it seems you have no choice but to use a symmetric
encryption algorithm - in other words, your original method. If the
strings are ~20
erikcw <[EMAIL PROTECTED]> writes:
> database. I'm using this encrypted string to identify emails from a
> user. (the string will be in the subject line of the email).
1. I hope you're not trying to spam anyone.
2. What happens if the user edits the subject line?
> I'm trying to figure out which
On Feb 11, 3:07 pm, [EMAIL PROTECTED] wrote:
> erikcw napisal(a):
>
>
>
> > Hi,
>
> > I'm trying to devise a scheme to encrypt/obfuscate a short string that
> > basically contains the user's username and record number from the
> > database. I'm using this encrypted string to identify emails from a
erikcw napisal(a):
> Hi,
>
> I'm trying to devise a scheme to encrypt/obfuscate a short string that
> basically contains the user's username and record number from the
> database. I'm using this encrypted string to identify emails from a
> user. (the string will be in the subject line of the email
17 matches
Mail list logo
