Re: encrypt but with normal characters for result?

This WebDNA talk-list message is from

2005

It keeps the original formatting. numero = 62342
interpreted = N
texte = WebDNA 6.0aRedhat Enterprise 3.x----Hi Gary,Gary Krockover wrote:> Dale,> > Does it need to be "super secretive" or why the encryption? Or do you just need a method to generate "generic" folder/file names on the fly?This is related to the topic of protecting images. The encryption was only to kind of mess up the folder name to make it less easy to guess. And to make it unique.I have a unique ID for each member and figured to encrypt the name of the folder with a seed of their member ID. That way the coding would be easy and consistent, yet the folder name for each user would be unique. It won't really be super secret, but it would make it much more difficult for people to guess the image path (those that are not allowed to view the content that is).> A simple convertchars database could be used to "scramble" the existing letters into an alpha-numeric scheme - even using upper/lower case which would make a difference on a *nix server of course.for user id 12345678 (also using a hash folder with the first xx chars of the member id)/images/1234/12345678/folder1/file.gif (filename created with [cart])for user id 8756234 (also using a hash folder with the first xx chars of the member id)/images/8756/8756234/folder1/file.gif (filename created with [cart])To make it more difficult to guess the paths (if used as above once they have the member ID they would know the next step is called 'folder1'), I would like to randomize the name of 'folder1' yet keep it simple to know what it is programatically.Hence the idea to encrypt using the same text - folder1 - but making it different by using the member ID as the seed value. I figured that would make things simple, except base64 and apop won't take a seed.> You could even get fancy and make a function, if you have v5.0+. Recently upgraded to 6.0, and on RH Enterprise 3 - haven't used any functions yet though.> The online doc's even have an example called "backwards" that rewrites the text string backwards. You could modify that as needed.> > http://webdna.smithmicro.com/ref/pages.html?context=Function.htmlWill check that out.> Here's a simple example with just convertchars:> > [text show=T]first_folder=[convertchars db=foldernamer1.db]first_folder[/convertchars][/text]> > [CREATEFOLDER path=[first_folder]]> > [!][/!]> [!][/!]I think the above would result in each instance of 'folder1' being the same. Maybe using the function you referenced above, I could grab the last 5-6 chars of the member ID, then reverse them and name the folder with that result.> GJKThanks for the suggestions! It is getting my feeble mind working :)Dale> > At 09:30 PM 6/24/2005, you wrote:> I can, although the goal though is to use the encrypted value to create either a file or folder that needs to be accessible via a webpage.-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: encrypt but with normal characters for result? ( John Peacock 2005)
Re: encrypt but with normal characters for result? ( Gary Krockover 2005)
Re: encrypt but with normal characters for result? ( eLists 2005)
Re: encrypt but with normal characters for result? ( "WebDna @ Inkblot Media" 2005)
Re: encrypt but with normal characters for result? ( Gary Krockover 2005)
Re: encrypt but with normal characters for result? ( eLists 2005)
Re: encrypt but with normal characters for result? ( "WebDna @ Inkblot Media" 2005)
Re: encrypt but with normal characters for result? ( "Dale's Lists" 2005)
Re: encrypt but with normal characters for result? ( Gary Krockover 2005)
encrypt but with normal characters for result? ( "Dale's Lists" 2005)

WebDNA 6.0aRedhat Enterprise 3.x----Hi Gary,Gary Krockover wrote:> Dale,> > Does it need to be "super secretive" or why the encryption? Or do you just need a method to generate "generic" folder/file names on the fly?This is related to the topic of protecting images. The encryption was only to kind of mess up the folder name to make it less easy to guess. And to make it unique.I have a unique ID for each member and figured to encrypt the name of the folder with a seed of their member ID. That way the coding would be easy and consistent, yet the folder name for each user would be unique. It won't really be super secret, but it would make it much more difficult for people to guess the image path (those that are not allowed to view the content that is).> A simple convertchars database could be used to "scramble" the existing letters into an alpha-numeric scheme - even using upper/lower case which would make a difference on a *nix server of course.for user id 12345678 (also using a hash folder with the first xx chars of the member id)/images/1234/12345678/folder1/file.gif (filename created with [cart])for user id 8756234 (also using a hash folder with the first xx chars of the member id)/images/8756/8756234/folder1/file.gif (filename created with [cart])To make it more difficult to guess the paths (if used as above once they have the member ID they would know the next step is called 'folder1'), I would like to randomize the name of 'folder1' yet keep it simple to know what it is programatically.Hence the idea to encrypt using the same text - folder1 - but making it different by using the member ID as the seed value. I figured that would make things simple, except base64 and apop won't take a seed.> You could even get fancy and make a function, if you have v5.0+. Recently upgraded to 6.0, and on RH Enterprise 3 - haven't used any functions yet though.> The online doc's even have an example called "backwards" that rewrites the text string backwards. You could modify that as needed.> > http://webdna.smithmicro.com/ref/pages.html?context=Function.htmlWill check that out.> Here's a simple example with just convertchars:> > [text show=T]first_folder=[convertchars db=foldernamer1.db]first_folder[/convertchars][/text]> > [CREATEFOLDER path=[first_folder]]> > [!][/!]> [!][/!]I think the above would result in each instance of 'folder1' being the same. Maybe using the function you referenced above, I could grab the last 5-6 chars of the member ID, then reverse them and name the folder with that result.> GJKThanks for the suggestions! It is getting my feeble mind working :)Dale> > At 09:30 PM 6/24/2005, you wrote:> I can, although the goal though is to use the encrypted value to create either a file or folder that needs to be accessible via a webpage.-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ eLists

DOWNLOAD WEBDNA NOW!

Re: encrypt but with normal characters for result?

2005

Top Articles:

Related Readings: