Doodles for Authentication: Recognition and User Study Results


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Doodles for Authentication: Recognition and User Study Results
# 1  
Old 05-06-2008
Doodles for Authentication: Recognition and User Study Results

HPL-2008-36 Doodles for Authentication: Recognition and User Study Results - Govindarajulu, Naveen Sundar; Madhvanath, Sriganesh
Keyword(s): Doodles, Authentication, Comparative user study, Dynamic Time Warping, L7 Features
Abstract: Traditional means of computer based authentication based on username and password combinations become unwieldy as the number of password accounts one manages increases. The average computer user needs to remember a large number of text username and password combinations for different applications, w ...
Full Report

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Red Hat

I want to centralize user authentication

Right now it is just a simple environment consisting of a small number of CentOS boxes, but I would like to set up central user authentication to make things easier, especially as we expand (I've already budgeted to triple our local infrastructure and we will be also expanding geographically to... (1 Reply)
Discussion started by: xdawg
1 Replies

2. Shell Programming and Scripting

Perl LWP user authentication

Hello all.. i am new to perl scripting.. i wanted to parse a text file, encode the parsed text and attach in url.. please point me to right resources if you know any..This is my major problem. Now i try to get a url running and save it in a text file using LWP module in perl, I used following... (0 Replies)
Discussion started by: empyrean
0 Replies

3. Programming

Questions about user authentication in my application

Hi, all, I am a newbie to linux authentication part. Questions below really puzzle me: How to authenticate users from local storage(passwd shadow) and nis server? (Without PAM) getpwnam_r() will return a '*' in the pw_passwd field of "struct passwd". I can parse /etc/shadow. But how... (1 Reply)
Discussion started by: mythmgn
1 Replies

4. AIX

LDAP user authentication issue

Hello everyone, hoping you can provide some incite with a little problem I'm having.. I have the LDAP client configured and running on my AIX 5.3 server, which is authenticating against an eDirectory LDAP server. I can login via LDAP no problems on the AIX server with newly created users,... (4 Replies)
Discussion started by: j_aix
4 Replies

5. Forum Support Area for Unregistered Users & Account Problems

authentication of new user

I recently registered, but never received the email with the instructions for authenticating my account. I confirmed my email in in the profile looks correct. I found and clicked the link to resend the authentication email. I clicked that link two days ago and I still don't have the email. It... (1 Reply)
Discussion started by: dwallace
1 Replies

6. UNIX for Dummies Questions & Answers

ps results - to show user's ps only

hi! how do i make ps results to only shows what's owned by users current job/background process only currently when users issuing ps: I just wanted the result when the user is issuing ps aux is same as when they're doing ps x like this: (which shows result on user's current background... (13 Replies)
Discussion started by: rdns
13 Replies

7. Shell Programming and Scripting

SFTP- Non-interactive user authentication

Hi All, sftp -b script.txt <hostname> user-authentication through non-interactive way is desired. But, its failing to do so. Could anyone kindly advise. Thanks for any/all help at the earliest. Regards, Dheeraj. (1 Reply)
Discussion started by: dheeruchakri
1 Replies

8. Solaris

User Authentication

Ok i need a little help... I have 20 Solaris 8 machines and I would like to have these machines do user authentication through one machine acting as server instead of having to maintain a user list on every machine. What can I do to achieve this? Thanks (3 Replies)
Discussion started by: meyersp
3 Replies
Login or Register to Ask a Question
pam_chauthtok(3)					     Library Functions Manual						  pam_chauthtok(3)

NAME
pam_chauthtok - perform password related functions within the PAM framework SYNOPSIS
[ flag ... ] file ... [ library ... ] DESCRIPTION
is called to change the authentication token associated with a particular user referenced by the authentication handle, pamh. The following flag may be passed in to The password service should not generate any messages. The password service should only update those passwords that have aged. If this flag is not passed, all password services should update their passwords. Upon successful completion of the call, the authentication token of the user will be changed in accordance with the password service con- figured in the system through pam.conf(4). Notes The flag is typically used by a application which has determined that the user's password has aged or expired. Before allowing the user to login, the application may invoke with this flag to allow the user to update the password. Typically applications such as passwd(1) should not use this flag. performs a preliminary check before attempting to update passwords. This check is performed for each password module in the stack as listed in pam.conf(4). The check may include pinging remote name services to determine if they are available. If returns then the check has failed, and passwords are not updated. APPLICATION USAGE
Refer to pam(3) for information on thread-safety of PAM interfaces. RETURN VALUE
Upon successful completion, is returned. In addition to the error return values described in pam(3), the following values may be returned: No permission. Authentication token manipulation error. Authentication information cannot be recovered. Authentication token lock busy. Authentication token aging disabled. User unknown to password service. Preliminary check by password service failed. SEE ALSO
pam(3), pam_start(3), pam_authenticate(3). pam_chauthtok(3)