in reply to encrypt/decrypt string

What are you trying to accomplish by passing the encrypted strings in the URL? Is this for session management? Login info?

I think there may be some good strategies out there, but need more information. I'm not so much interested in how you want to implement the encryption. I'm asking what it's for.


Dave

Replies are listed 'Best First'.
Re^2: encrypt/decrypt string
by artist (Parson) on Oct 19, 2006 at 18:05 UTC
    I am passing the login info and like to publish RSS feed for given user. I like to have fix number of characters in the encrypted string.
    --Artist

      I thought you might be passing login info. Once the client has logged in, you don't need to pass the info back and forth anymore; just pass an encrypted session ID, and store any other sensitive info on the server. You would probably benefit from CGI::Session, and one of its session ID helper modules such as CGI::Session::ID::MD5 (which uses Digest::MD5).


      Dave

        You might have slightly misunderstood. I have a link for RSS feed. When user clicks on RSS feed, it gives the URL for the RSS feed, particularly for that user. URL should be of the form: server/cgi-bin/rss.pl?feed_id=ABCDEF123456787980". They can take this feed id and plugin into their favorite RSS reader. Now, I should be able to decode the feed_id on the backend, whenever they call and genrate live RSS feed for them.
        --Artist