--- - branch: MAIN date: Wed May 4 22:26:56 UTC 2011 files: - new: '1.5' old: '1.4' path: pkgsrc/sysutils/ir-account/Makefile pathrev: pkgsrc/sysutils/ir-account/Makefile@1.5 type: modified - new: '1.2' old: 1.1.1.1 path: pkgsrc/sysutils/ir-account/distinfo pathrev: pkgsrc/sysutils/ir-account/distinfo@1.2 type: modified id: 20110504T222656Z.abf6d82dea44412d27be8f4572e9665015fe5955 log: | Update to 0.2. (Changes are due to Richard Hansen of BBN.) New in Version 0.2 (released 2011-04-15): * Bug fixes: + extract-account: - account extraction left temp files if authorized_keys had the uchg flag set - if the user didn't actually exist, a bogus tarball would be created anyway + install-account: - the home directory was assumed to be /home/${USER}, which meant that root's files weren't installed properly - If the user already existed, the order of entries in the passwd database wasn't preserved. This caused problems with root accounts because getpwuid(0) started returning the passwd entry for the 'toor' user (breaking "are you root?" tests in various scripts). + sudo-add: - if sudo-add couldn't find the sudoers file or couldn't read it, it didn't remove existing entries when adding or removing a user (adding duplicate entries if adding a user that was already there, and silently failing when removing a user) - if sudo-add could find and read the sudoers file: * it would remove the wrong existing entry if the username of the user being added/removed started with the same characters as another user higher in the sudoers file (e.g., adding or removing foo would remove user foobar if foobar was higher in the sudoers file) * 'sudo-add -r' would only remove the first instance of a user from sudoers (a particular problem given the above bug) - sudo-add wasn't preserving order if the user was already in sudoers (order can be significant in sudoers) * Less verbose output. module: pkgsrc subject: 'CVS commit: pkgsrc/sysutils/ir-account' unixtime: '1304548016' user: gdt