nbk [Sun, 12 Aug 2007 18:00:34 +0000 (18:00 +0000)]
Add a Makefile to dialup_admin to make the installation easier.
Now you can type "make install DIALUP_PREFIX=/path/of/your/choice"
and your local copy will work without editing a decade of files.
Based on the Makefile in the source package of the Debian archive,
with edits to not try to copy CVS directories. (so it works on CVS
snapshots, too)
In lib/sql/attrmap.php3, only register variables once. Go through $show_attrs and set default attribute
mappings for any attribute that a mapping does not exist.
pnixon [Thu, 24 Mar 2005 11:09:13 +0000 (11:09 +0000)]
Insert a uniqueid into AcctSessionId field also, as both Postgresql and Oracle have this field set to NUT NULL. (How did this code ever work with PG??)
pnixon [Tue, 22 Mar 2005 06:07:55 +0000 (06:07 +0000)]
Force set NLS_TIMESTAMP_TZ_FORMAT='YYYY-MM-DD HH24:MI:SS.FF TZH:TZM' on every Oracle connect. (If anyone can think of a better way to do this I am all ears)
kkalev [Wed, 16 Mar 2005 09:39:26 +0000 (09:39 +0000)]
Revert back to using postgresql specific functions. dbx functions should be changed
to also use a dabatase subtype and perform any database specific functions themselves.
kkalev [Tue, 15 Mar 2005 13:24:51 +0000 (13:24 +0000)]
Remove snmp_clearsession. It is replaced by clearsession which supports both snmp and telnet
methods of removing a user from an access server. Add corresponding configuration directives
general_sessionclear_method and nasXX_sessionclear_method
kkalev [Mon, 14 Mar 2005 11:51:32 +0000 (11:51 +0000)]
* Show the correct nas type in nas_admin. Bug noted by Nick Bright
* Correctly calculate the nas ip in lib/sql/nas_list.php3. Add a check_ip() function in lib/functions.php3
Bug noted by Nick Bright
kkalev [Wed, 9 Mar 2005 21:53:48 +0000 (21:53 +0000)]
* Make nasXX_finger_type actually work since the place where nas information was stored was changed a
long time ago. Bug noted by Nick Bright
* In user_finger only set LD_LIBRARY_PATH once, not each time we call snmpfinger
kkalev [Sat, 19 Feb 2005 12:02:34 +0000 (12:02 +0000)]
In clear_opensessions depending on sql type use either IS NULL or = 0 in the DELETE statement.
We need to find a cleaner solution to this. This closes bug#175
kkalev [Sat, 19 Feb 2005 01:08:44 +0000 (01:08 +0000)]
* Add more documentation for per user counter limit attributes (daily/weekly/monthly limits)
* Make all counter limits default to none so that people don't get confused
kkalev [Tue, 4 Jan 2005 15:17:28 +0000 (15:17 +0000)]
* Add an sqlrelay functions file. The user_admin page does not currently work. Looking into it.
* Add sqlrelay support in the scripts. Add a sqlrelay_query script to run sqlrelay commands
kkalev [Mon, 20 Dec 2004 16:58:16 +0000 (16:58 +0000)]
* In bin/snmpfinger also accept @,. in the username
* If we are stripping realms, then if needed strip them from the data returned by snmpfinger in
user_finger.php3
kkalev [Mon, 25 Oct 2004 13:55:04 +0000 (13:55 +0000)]
* Add lib/sql/group_change.php3 to add and delete a user from groups
* Add a new directive sql_show_all_groups. If set to true then in user edit page we show all available
groups with the ones the user is a member of highlighted. The administrator can then directly
change user group membership by changing membership in this group list.
kkalev [Mon, 9 Aug 2004 15:37:46 +0000 (15:37 +0000)]
In user_state also take into account any open sessions when calculating daily/weekly usage.
Add two more lines in the output stating the number of current open sessions and the time used.
* Add a drop down menu with existing groups in group_new.php3
* Check for sql in show_groups.php3
* In lib/sql/group_info.php3 if $login is not set, find available groups and place them in
$existing_groups along with a count of users per group. Use the functionality in group_new.php3
and show_groups.php3
* Update TODO
* A LOT of security related fixes. Now dialupadmin should hopefully be secure enough to
be accessed by normal users (not administrators).
* Move a few elements in the CSS file from the body tag. Suggestion by Gary McKinney
* Update FAQ about using php with no sql support.
* Allow the user to select between viewing FAQ,HOWTO or README in the help page.
* Use $_SERVER instead of $HTTP_SERVER_VARS
Add a missing.php3 file with functions that may be missing from the PHP version used. Include it
if a function is missing. Currently only array_change_key_case() is included
kkalev [Tue, 29 Jun 2004 10:09:26 +0000 (10:09 +0000)]
* Escape special characters in the sql password. This closes bug #96
* Do an xlat for general_accounting_attrs_file and general_user_edit_attrs_file. That way we can
have different mappings for each administrator.
kkalev [Fri, 18 Jun 2004 13:01:56 +0000 (13:01 +0000)]
* Move the xlat function to a separate file in lib/xlat.php3
* Add a lib/sql/nas_list.php3 to also get the nas list from sql (naslist.conf still works)
* add realms nasdb and nasadmin in username.mappings. nasadmin is used to signify if the
user is allowed to use the nas_admin page. nasdb is used to shorten the nas list to only
a few specific entries. That way administrator responsible for a few access servers will
only be able to administer those access servers and not see the rest of the nas list.
* Add username searching in the find page as suggested by joram agten
* Don't use nas_list in nas_admin
* Add a check_user_passwd() and a get_user_dn() functions in lib/ldap/functions.php3
* Add general_restrict_badusers_access directive. If set to yes we only allow each administrator
access to their own entries in the badusers table
* Add a username.mappings table. We are able to map each administrator username to additional queries
on the accounting and user settings tables.
* Add an sql_accounting_extra_query directive. If set this query is included in all
queries to the accounting tables.
Combined with admin username mappings we are able to easily restrict access on specific accounting data
to each administrator.
* Escape bad characters in the $login variable
* Add a da_sql_escape_string function. We use that for every element we pass to sql queries in order to
protect ourselves from sql injection.
* Use the ldap_userdn directive where applicable in the functions.php3 file
* Add an sql_xlat function
TODO: Check out the sql queries in lin/sql for sql injection.