Re: users.db
This WebDNA talk-list message is from 1999
It keeps the original formatting.
numero = 22596
interpreted = N
texte = >Hi Folks. A webcat server of mine is asking me if I want to encrypt my>users.db yet when I look at users.db in bbedit I see it is already>encrypted. What could be causing this.Did you manually (or otherwise) remove the UPDATEDONE record from the users.db? If so, that is what has caused this problem. When webcat does not find that record in the db, it assumes that the passwords are NOT encrypted, thus it asks you if you'd like to encrypt them. But since they are already encrypted in your case, it's a mistake to encrypt them again ...>I went ahead with the encryption link after backing up users.db and>then webcat would not leave any users in.It's a good thing you made a backup copy first, because you will need that backup copy to fix things. When you clicked the encryption link, you re-encrypted the previously-encrypted passwords, so now all the passwords in the current users.db are double-encrypted -- that's why they don't work ... :(>Should I recreate my users.db?You should quit webcat, then replace the current users.db with the backup copy you made. You should also add the missing UPDATEDONE record to the users.db manually, with a text editor -- so webcat doesn't ask you to encrypt your previously-encrypted passwords again some day ... :)Sincerely,Ken Grome808-737-6499WebDNA Solutionsmailto:ken@webdna.nethttp://www.webdna.net
Associated Messages, from the most recent to the oldest:
>Hi Folks. A webcat server of mine is asking me if I want to encrypt my>users.db yet when I look at users.db in bbedit I see it is already>encrypted. What could be causing this.Did you manually (or otherwise) remove the UPDATEDONE record from the users.db? If so, that is what has caused this problem. When webcat does not find that record in the db, it assumes that the passwords are NOT encrypted, thus it asks you if you'd like to encrypt them. But since they are already encrypted in your case, it's a mistake to encrypt them again ...>I went ahead with the encryption link after backing up users.db and>then webcat would not leave any users in.It's a good thing you made a backup copy first, because you will need that backup copy to fix things. When you clicked the encryption link, you re-encrypted the previously-encrypted passwords, so now all the passwords in the current users.db are double-encrypted -- that's why they don't work ... :(>Should I recreate my users.db?You should quit webcat, then replace the current users.db with the backup copy you made. You should also add the missing UPDATEDONE record to the users.db manually, with a text editor -- so webcat doesn't ask you to encrypt your previously-encrypted passwords again some day ... :)Sincerely,Ken Grome808-737-6499WebDNA Solutionsmailto:ken@webdna.nethttp://www.webdna.net
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
WebCatalog Technical Reference (1997)
Problems with AOHell (1999)
[group] ? (1997)
Possible Macv2.1b2 Merge Bug (1997)
Repeating Fields (1997)
Nested vs conditional (1997)
Applescript, WebDNA, and PDF (1997)
what's wrong with this picture (2006)
[click][/click] (1999)
Jimmy (1998)
Install Webcatalog under NT4.0 and Microsoft IIS 2.0 (1997)
How to Display text in empty fields (1997)
[WebDNA] Send URL Get without waiting for response (2014)
Help! WebCat2 bug (1997)
Emailer Error code 530? (2002)
European Convention (2004)
Subtotal Not Calculated on Invoice.html (1998)
WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997)
RE: [REPLACE] inside [FOUNDITEMS] (1998)
NY taxRates.db? (1997)