Slashdot Mirror

Search for it, authord.com is apprently dead or broken. Not affiliated with them, have used it for a couple years. Does NOT integrate with AD. Keeps a local list of users/categories/groups you can assign access levels and if they (or their group) are not assigned to the category or their access level is too low, they do not even see the entries. Windows only, written in VB, $129 for 10 users. I haven't found any viable open source alternatives.
We put the the executable and database on a network share (no registry keys!!), it stores the personal preferences (window size, position, etc) in My documents.
Individual logins, radius, MIIS sync are all superior alternatives, of course, but this is quick, affordably priced and reasonably secure.
Alternatives you might want to look at:

pGina http://www.pgina.org/?page_id=3 Master your passwords on a platform other than AD for your central identity store.

AcctSync, doen not appear to be actively developed, it has not had any news posted in about 18 months. https://sourceforge.net/projects/acctsync/

PSync http://www.psynch.com/, commercial, no pricing on their site (schmucks).

They could have avoided this bad password mess! http://www.psynch.com/

Come on guys, there are reasonable products out there to synchronize passwords
between systems. Surely one strong, remembered, frequently-changed passwords
is more secure than a dozen passwords on a post-it note, less costly than a
smart card or hardware token, and not as vulnerable to gummy bears as a consumer-grade
fingerprint scanner!

One such product is here: http://psynch.com/

I'm sure others work too.

... and for administrators who must set policy, are here:
http://psynch.com/docs/password-policy-guidelines. html

Even more general guidelines about authentication technologies, including passwords, expiration, intruder lockout, tokens, etc. are here:
http://psynch.com/docs/password-management-best-pr actices.html

It's a commercial site, but this content is pretty useful and not especially product focused.

... and for administrators who must set policy, are here:
http://psynch.com/docs/password-policy-guidelines. html

Even more general guidelines about authentication technologies, including passwords, expiration, intruder lockout, tokens, etc. are here:
http://psynch.com/docs/password-management-best-pr actices.html

It's a commercial site, but this content is pretty useful and not especially product focused.

... and for administrators who must set policy, are here:
http://psynch.com/docs/password-policy-guidelines. html

Even more general guidelines about authentication technologies, including passwords, expiration, intruder lockout, tokens, etc. are here:
http://psynch.com/docs/password-management-best-pr actices.html

It's a commercial site, but this content is pretty useful and not especially product focused.

The poster illustrates the problem with examples such as bookmarks and address books ( which is a different problem than what liberty et. al tries to solve I believe) . These kinds of information can already be kept in an LDAP server and most applications can store and retrieve these from those servers. Outlook does it, mozilla does, ximian does it.

LDAP address book support is relatively mature in most email readers. Check out OpenLDAP for more info.

Single sign-on can also be done via LDAP. Or Kerberos/LDAP if you're so inclined. Netscape NTSych product, the Psynch® product, etc. can be used to sych NT or win2k with an external database. Check out projects such as pgina. There's a free general purpose NT password sync dll available from AcctSync. This DLL is nice, you can catch user passwords and pass them to an arbituary script with the username. This could be a perl script that updates LDAP to a vbscript that updates the coresponding Oracle user, it doesn't matter.

Also, it's simple to store public certs in an ldap server, making it easier to deploy PKI on a budget ( you don't want to know how much netscape and novell charges for this per user, trust me :)

In short, a lot of your problems can be solved right now by running a LDAP server and configuring your applications to rely on it for their datastore. Good luck.

It's not that hard to enforce strong password rules at the time of password change .. and consequently our customers require always-new passwords, enforce dictionary checks, and can even apply regular expression rules.

(psynch.com if you're really curious).

M-Tech, a Calgary company makes P-Synch, a cross-platform password management system. P-Synch supports over 60 types of systems including: Unix servers, Windows NT, Windows 2000 active directory, OS390 / MVS mainframes, LDAP directories, email, groupware and popular ERP applications, such as SAP and PeopleSoft.

M-Tech showed P-Sync off to the Calgary Unix Users Group last year. When I saw your story, I immediately thought if them.

http://www.psynch.com/

looks to me like it isn't free .. but it should do what you want.

This works pretty good.

I am working on deployment of a product called "P-Synch" which synchronizes passwords between NT domains, Unix systems (NIS/YP included), Oracle, and anything else you can write a script for. It will be wonderful when users can go to a web page and reset all of their passwords, or the help desk can change a user's password on all machines at once.

IMHO, the best way to remember lots of passwords
is to synchronize them. First, you select a
hard to guess value. Select 2 or 3 if you
access some systems that you are afraid might
be compromised (e.g., local servers vs. public
WWW sites). Then, apply that password to every
account you have. voila - you don't have to
remember a million passwords.


with this in mind, we make / sell a commercial
package for synchronizing passwords:
http://www.psynch.com


-- Idan