Hardware authentication for Linux using ordinary USB Flash Drives.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

196 lines
8.3 KiB

17 years ago
17 years ago
17 years ago
18 years ago
  1. * 0.4.2
  2. - Added the pad_expiration option which tells pam_usb how often pads
  3. should be updated in order to reduce device writing.
  4. - Support for time options in the configuration parser (5s, 2h, 10m, etc)
  5. - Added the --verbose option to pamusb-conf
  6. - Fixed the ElementTree import statement of pamusb-agent to work with
  7. Python 2.5. Thanks to Donald Hayward <liquidsunshine@gmail.com> for
  8. the patch.
  9. - Various minor bugfix
  10. * 0.4.1
  11. - Fixed a security issue related to OpenSSH authentication
  12. - Fixed the quiet option (now it is really quiet)
  13. - Support for devices without vendor/model information
  14. * 0.4.0
  15. - Both pam_usb and its tools (adm, hotplug) have been redesigned from the
  16. ground up and rewritten from scratch.
  17. - Hardware recognition is now done through HAL which provides a stable
  18. interface over kernel changes.
  19. - Certificates have been replaced by one time pads. That will prevent
  20. copies of the USB device to be used for authentication.
  21. - Device's manufacturer properties verification. pam_usb now verifies
  22. device informations (vendor, product, serial number, UUID) in the
  23. authentication process.
  24. - Configuration is now handled in a central place, the pamusb.conf
  25. configuration file. This XML file contains configuration entries for
  26. users, devices and services.
  27. - pamusb-agent (formely usbhotplug) make use of DBUS signals (sent by HAL)
  28. instead of kernel hotplugging. Also, its configuration has been merged
  29. into the pamusb.conf configuration file.
  30. - A new tool named pamusb-check has been added. It can perform authentication
  31. the way the PAM module does. It can be useful for testing and scripting
  32. purposes.
  33. * 0.3.3
  34. - The option keypath is now splitted into local_keypath and device_keypath.
  35. - Fixed a bug that occurred when the TTY entry was empty.
  36. - pam_usb doesn't get anymore the tty name from PAM_TTY as it used to be
  37. empty on some systems.
  38. - Better defaults. The default options have been set to fit most needs,
  39. you are no longer required to use !check_device on 2.6.
  40. - Verbose mode. By default, pam_usb now prints some informations during
  41. the login process (access granted, the reason why access was refused, etc).
  42. This can be turned off using the brand new 'quiet' option.
  43. - Other small fixes.
  44. * 0.3.2
  45. - Now pam_usb will also try to autodetect /dev/sdN devices (not just
  46. /dev/sdNX).
  47. - Fixed a bug that happened when the application using PAM didn't set
  48. PAM_TTY correctly.
  49. - Added the use_first_pass and try_first_pass options.
  50. Now if you enter your password on another PAM module (such as pam_mount
  51. or pam_ssh), pam_usb will use that password to decrypt the private key.
  52. * 0.3.1
  53. - Lot of misc fixes (memory management, Makefiles, sanity checks, etc).
  54. I'd like to thank the PaX Team <pageexec@freemail.hu> who did almost
  55. the whole job.
  56. - Added the hostname option which allows to select what hostname should
  57. be used for authentication (useful for shared public keys over lan).
  58. Thanks to Nicolas Chauvat <chauvat@nerim.net> who reported the issue,
  59. the idea and the patch for this feature.
  60. * 0.3.0
  61. - Not much changes in this version beside a gcc fix, but the 0.2 branch
  62. reached too many new features so i wanted to name this release 0.3.0
  63. as i should have done with 0.2.3
  64. - Fixed a gcc 3.3 compile issue, and all related warning.
  65. I would like to thank the following guys for having reported this bug so fast:
  66. Lalande Fabrice <fabrice.lalande@orange.fr>
  67. Marco <gaedol@softhome.net>
  68. Neil Dunbar <neil.dunbar@hp.com>
  69. * 0.2.3
  70. - Added the usbhotplug tool.
  71. usbhotplug is a hotplug agent that will automagically start a lock handler
  72. when the usb device is removed and an unlock handler when the usb device
  73. is plugged back in and authenticated through pam_usb.
  74. The default handlers will start xlock when the usb device is removed,
  75. and will kill it when the usb device is plugged back in and authenticated.
  76. I'd like to thank Wout Mertens <wmertens@cisco.com> as we had a couple
  77. of discussions about hotplug which helped me implementing this tool.
  78. - The parser can now understand "option" and "!option" instead of
  79. option=1 and option=-1 (e.g. debug !check_device).
  80. Thanks to Jean-Christophe JASKULA <jean.christophe.jasku-la@wanadoo.fr> who
  81. suggested me that and provided an initial patch.
  82. - Fixed a loop bug on serial number checking. Thanks to Zs <horzsol@freemail.hu>
  83. for reporting the bug and a patch to fix it.
  84. - Added the direct_open option which allows to open the private key
  85. using O_DIRECT to avoid disk caching (works only on devices that
  86. supports it). Thanks to myles <myles@tenhand.com> who suggested me that.
  87. - Added some sanity checks here and there because it seems that the PAM
  88. API can return weird stuff from time to time.
  89. - Handling the mount point creation/remotion in a better way which seems
  90. to fix a couple of mntpoint problems.
  91. * 0.2.2
  92. - Added the keep_mounted option, which allows to not umount the mount point
  93. once logged (useful if the gpg/ssh key is stored on there)
  94. - Fixed the mntpoint option: do not delete the directory if it's not a
  95. temporary one.
  96. - Added the support to pass multiple filesystems name with the fs=
  97. option (comma separated list). Changed the default fs to "ext2,vfat"
  98. - Added the log_file option. Takes a filename as a argument.
  99. Combined with debug=1 it can log debug messages to a file.
  100. - Not mounting the device as read-only anymore. Instead, the mount_opts
  101. option has been created. It accepts a comma separated list of mount
  102. options (accepted options are: ro,bind,sync,remount,nosuid,noexec,nodev).
  103. - Fixed an issue which made the allow_remote feature not working correctly
  104. with gdm/kdm.
  105. - Introduced the local_hosts and local_consoles options. They contain a
  106. comma separated lists of hosts and consoles allowed to log in while using
  107. allow_remote=-1
  108. * 0.2.1
  109. - Changed the naming method from x.y to x.y.z
  110. - pam_usb is now able to distinguish local users from remote (as in
  111. logged via ssh), and denies the authentication of non-local users.
  112. Setting allow_remote to 1 disable this feature.
  113. - Mounting is now done in read-only.
  114. - Added the missing mandatory PAM functions.
  115. * 0.2_rc2
  116. - Workaround to make pam_usb not use /proc so it can run on Linux 2.6
  117. By setting check_device to -1, pam_usb will neither check the device's
  118. serial number, nor if it's attached. It's not a real problem if you
  119. don't need serial number checking, but don't combine it with
  120. check_if_mounted.
  121. - Added the force_device capability. Now you can specify a device that
  122. will be mounted without going in guessing mode. If the device cannot
  123. be mounted, it'll switch back to the default guess mode.
  124. Useful if guess mode fails, if you don't want it to try several
  125. devices before getting the right one (so you can login faster), or if
  126. you want to login using a floppy disk, a cdrom or whatever you want.
  127. - Modified the serial number authentication method so now if no serial
  128. numbers are avaible on a device, it will try to use the GUID.
  129. Thanks to Damien Braillard <damien.b@freesurf.ch> who reported the
  130. issue, suggested a way to fix it, and provided a first patch for it.
  131. * 0.2_rc1
  132. - Radically changed the way pam_usb authenticates the user on the
  133. system. Now it works with a pair of DSA keys.
  134. Thanks to Wout Mertens <wmertens@cisco.com> who told me that i could
  135. use a couple of SSH keys to fix the authentication issue.
  136. That gave me the idea to use a set of private/public keys.
  137. Thanks to Ilkka Mattila <ilkka@lyseo.edu.ouka.fi> who helped me to
  138. find out a better way to implement the key challenge: extracting the
  139. public key was inadequate.
  140. Also thanks to those who brought up weird scenarios and/or tested
  141. pre-releases of pam_usb, in alphabetical order:
  142. Ilkka Mattila <ilkka@lyseo.edu.ouka.fi>
  143. Joonas Kortesalmi
  144. Thomas Stewart <thomas@stewarts.org.uk>
  145. Tuure Laurinolli <tuure@laurinolli.net>
  146. * 0.1:
  147. - Now pam_usb doesn't require a mount point. Instead, it creates
  148. a temporary directory under /tmp.
  149. Thanks to Loic Jaquemet <jaquemet@fiifo.u-psud.fr> who gave me the idea.
  150. - Compiles with gcc 2.95 thanks to Tobias Bayer <tobi.bayer@gmx.de> bug
  151. report.
  152. * 0.1-beta2:
  153. - procfile and device entries autodetection have been fixed thanks to
  154. Thomas Stewart <thomas@stewarts.org.uk> bug reports.
  155. - devfs support added. Thanks to Loic Jaquemet <jaquemet@fiifo.u-psud.fr>
  156. for the bug report.
  157. * 0.1-beta1:
  158. - Initial release