Updated libpam-radius-auth package for user level auth in radius (mirror of https://github.com/vyos/libpam-radius-auth.git) https://git.amelek.net/vyos/libpam-radius-auth.git/atom?h=sagitta 2017-06-21T01:29:11+00:00 2017-06-21T01:29:11+00:00 Dave Olson olson@cumulusnetworks.com 2017-06-19T21:08:00+00:00 urn:sha1:61257dc81beebcf324027edb712305c376dd2052 Add changes allow admins to set up RADIUS clients with no local knowledge of the RADIUS accounts (no adduser required, nor LDAP, etc.) This is done by using the nss-mapuser package. The only real change to this package is to set up the SUDO prompt, so it's the RADIUS login name, in the pam_sm_acct_mgmt entry point. Bumped the version to 1.4.1 Change the PACKAGE info in configure to reflect Cumulus, and also a few related fields. Changed maintiner to dev-support Also incorporated changes to make debuging builds easier under debian. Added comment and description of src_ip to the config file (author of the src_ip changes hadn't yet done that), and removed the location of config file from comments, since debian installs to a different location. Quieted config complaints; can't move to current because current is GPLv3, and this doesn't use autoconf. Tried to capture the 5 years of changes between 1.3.17 and 1.4.0 Added lintian overrides. Fixed up debian/copyright file to be standard format, and match (approximately) the source files. overrides don't quite work, because source vs binary confusion, but documents them Added debian install files Added man page for the plugin, and for the RADIUS client config file 2014-11-26T17:06:53+00:00 Jens Kuehnel ilovelogging-git-commit@jens.kuehnel.org 2014-11-26T17:06:53+00:00 urn:sha1:c1986a03dc27c670e32973c2fabd8fb504585670 2014-08-29T17:04:36+00:00 Alan T. DeKok aland@freeradius.org 2014-08-29T17:04:36+00:00 urn:sha1:50146dc06372256cb899fbcf68bbc886d5641160 2014-08-29T10:06:46+00:00 Walter de Jong walter.dejong@surfsara.nl 2014-08-29T10:06:46+00:00 urn:sha1:fabeb81842796838035b64734e53a28463df50f6 Force authentication failure when a certain amount of challenges has been reached. This is a workaround for buggy servers that keep issueing challenges, when they should really send Access-Reject. The limit is configurable through parameter "max_challenge". The default is 0, which means the workaround is disabled. An invalid or negative value also disables this workaround. 2014-06-17T21:00:11+00:00 Bennett Samowich bennett@foolean.org 2014-06-16T01:23:34+00:00 urn:sha1:9a1ee796634504a6f26a08fb8731c1d032dba9f2 2013-02-24T01:20:01+00:00 Diego Elio Pettenò flameeyes@flameeyes.eu 2013-02-24T01:20:01+00:00 urn:sha1:0089fa4ee9c6de7e7684a88e1227d56beaaf0f85 The path depends on the bitness of the software, so it can't be used this way. 2012-10-24T07:18:01+00:00 Arran Cudbard-Bell a.cudbardb@freeradius.org 2012-10-24T07:18:01+00:00 urn:sha1:c2c2b9c4b0571f4e6050de78ae8fd813d1be7431