summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorchristopherm <christopherm@4979c152-3d1c-0410-bac9-87ea11338e46>2006-11-15 23:23:24 +0000
committerchristopherm <christopherm@4979c152-3d1c-0410-bac9-87ea11338e46>2006-11-15 23:23:24 +0000
commit3c605838802da0f18ae2974debb17754f20047d7 (patch)
tree2e9d536bcf86f6611c0ca17af0d4a267501660f0
parent454c1ff918114c4db94ed4740e32268f8d117b50 (diff)
The admin password will now only be md5() in the database
git-svn-id: https://ledger-smb.svn.sourceforge.net/svnroot/ledger-smb/trunk@623 4979c152-3d1c-0410-bac9-87ea11338e46
-rwxr-xr-xsql/Pg-central.sql3
1 files changed, 0 insertions, 3 deletions
diff --git a/sql/Pg-central.sql b/sql/Pg-central.sql
index 4bab66ed..50904801 100755
--- a/sql/Pg-central.sql
+++ b/sql/Pg-central.sql
@@ -44,9 +44,6 @@ COMMENT ON TABLE users_conf IS 'This is a completely dumb table that is a place
COMMENT ON COLUMN users_conf.id IS 'Yes primary key with a FOREIGN KEY to users(id) is correct';
COMMENT ON COLUMN users_conf.password IS 'This means we have to get rid of the current password stuff and move to presumably md5()';
--- Per conversation with ChrisM, if the admin user has a null password a couple of things happen.
--- 1. It is implicit that this is an initial install
--- 2. If the admin password does not match the ledger-smb.conf admin password, we throw a hijack alert
-- The two below statements must be run from a single session
INSERT INTO users(username) VALUES ('admin');
INSERT INTO users_conf(id,password) VALUES (currval('users_id_seq'),NULL);