NAME¶

opieserv - Example OPIE-based OTP server

SYNOPSIS¶

opieserv

[ principal ]

DESCRIPTION¶

opieserv takes an OTP principal (e.g., a user name) from either the command line or standard input and returns a current OTP challenge for that principal. It then reads an OTP response to that challenge from standard input and displays a message and returns a value to indicate either success (exit value = 0) or failure (exit value = 1). It is intended as an example for programmers of how a simple OTP server can be built.

EXAMPLE¶

wintermute$ opieserv kebe

otp-md5 495 wi01309

Response:

User verified.

wintermute$

SEE ALSO¶

opiegen(1), opiekey(1), opie(4), opiepasswd(1), opieinfo(1), opiesu(1), opielogin(1), opieftpd(8), opiekeys(5), opieaccess(5)

AUTHOR¶

The opieserv1) program was created by Craig Metz for OPIE 2.2.

Bellcore's S/Key was written by Phil Karn, Neil M. Haller, and John S. Walden of Bellcore. OPIE was created at NRL by Randall Atkinson, Dan McDonald, and Craig Metz.

S/Key is a trademark of Bell Communications Research (Bellcore).

CONTACT¶

OPIE is discussed on the Bellcore "S/Key Users" mailing list. To join, send an email request to:

skey-users-request@thumper.bellcore.com