Contributed by Dengue on from the I-got-this-card-see. dept.
Thanks,
-dan"
(Comments are closed)
OpenBSD Journal
Contributed by Dengue on from the I-got-this-card-see. dept.
Thanks,
-dan"
(Comments are closed)
Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]
By Hans Insulander () hin@openbsd.org on mailto:hin@openbsd.org
Jim Rees is also working on smartcard support that will ship in 3.0, and you'd a driver for your specific cardreader and card.
By David Jorm () davidj@unixpac.com.au on http://www.unixpac.com.au/
By markus () markus@openbsd.org on mailto:markus@openbsd.org
# cryptoinit markus_friedl
and try:
# /usr/libexec/auth/login_crypto -d markus_friedl
openssh, also supports CRYPTOcard authentication
(enable ChallengeResponse, see ssh(1), sshd(8))
By Kevin Kadow () openbsd@msg.net on http://www.msg.net/utility/FWTK/#randomnumber
I've tried just about all of the authentication tokens, and have deployed SNK, SafeWord, and SecurID. I've managed to integrate most of these into SSH and PAM without massive effort.
I've found that in most cases the end-user is annoyed by Challenge-Respose systems and usually insist on Time Synchronous (SecurID) or Event Synchronois (various vendors, including Cryptocard).