/var/lib/gnumed/server/sql/gmTestAccounts.sql is in gnumed-server 19.6-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 | -- GNUmed database test accounts
-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-- !! NEVER EVER use those accounts/passwords in a !!
-- !! production database. As they are in CVS know- !!
-- !! ledge about them is PUBLIC and thus extremely !!
-- !! insecure. DO NOT USE FOR PRODUCTION. !!
-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-- $Source: /home/ncq/Projekte/cvs2git/vcs-mirror/gnumed/gnumed/server/sql/gmTestAccounts.sql,v $
-- $Id: gmTestAccounts.sql,v 1.11 2004-07-17 20:57:53 ncq Exp $
-- GPL v2 or later
-- author: Karsten.Hilbert@gmx.net
-- ===================================================================
-- must ignore errors so we don't fail on
-- accounts that exist already
\unset ON_ERROR_STOP
-- Anyone know a way of telling VALID UNTIL that the
-- value is CURRENT_DATE + interval '4 months' ?
-- not possible according to Tom Lane, either do in client
-- or wrap in pl/pgsql function with execute()
-- ===================================================
drop user "test-doc";
CREATE USER "test-doc"
WITH PASSWORD 'test-doc'
IN GROUP "gm-doctors", "gm-public"
VALID UNTIL '2004-12-31'
;
-- ===================================================
drop user "test-nurse";
CREATE USER "test-nurse"
WITH PASSWORD 'test-nurse'
IN GROUP "gm-staff_medical", "gm-public"
VALID UNTIL '2004-12-31'
;
-- ===================================================
drop user "test-secretary";
CREATE USER "test-secretary"
WITH PASSWORD 'test-secretary'
IN GROUP "gm-staff_office", "gm-public"
VALID UNTIL '2004-12-31'
;
-- ===================================================
\set ON_ERROR_STOP 1
-- ===================================================
-- $Log: gmTestAccounts.sql,v $
-- Revision 1.11 2004-07-17 20:57:53 ncq
-- - don't use user/_user workaround anymore as we dropped supporting
-- it (but we did NOT drop supporting readonly connections on > 7.3)
--
-- Revision 1.10 2004/01/10 02:02:03 ncq
-- - revalidate test accounts until end of 2004
--
-- Revision 1.9 2003/10/07 11:14:25 ncq
-- - try to make Debian happy
--
-- Revision 1.8 2003/06/14 11:42:45 ncq
-- - note on VALID UNTIL
-- - bump up VALID UNTIL to 2003-12-31
--
-- Revision 1.7 2003/06/11 12:51:07 ncq
-- - Andreas is right, we *cannot* do revision tracking here ...
--
-- Revision 1.6 2003/06/10 08:56:59 ncq
-- - schema_revision -> gm_schema_revision
--
-- Revision 1.5 2003/02/07 14:33:21 ncq
-- - can't use schema tracking since at server level we aren't guarantueed to have that
--
-- Revision 1.4 2003/02/04 12:22:53 ncq
-- - valid until in create user cannot do a sub-query :-(
-- - columns "owner" should really be of type "name" if defaulting to "CURRENT_USER"
-- - new functions set_curr_lang(*)
--
-- Revision 1.3 2003/01/30 09:02:13 ncq
-- - don't fail on failure to insert into schema revision table
--
-- Revision 1.2 2003/01/20 12:11:46 ncq
-- - typo
--
-- Revision 1.1 2003/01/19 15:30:32 ncq
-- - a few test users
--
|