>>oh, like putting it in the gecos field? that'd be kinda cool. I like that idea.. But what are you doing if you want to transfer your crypted dir to another machine? Will be definitely harder to squeeze the bits out of the gecos. And you probably get a high probability of funny terminal behaving.
> Yes, that is the train of thought here.. > Markus, by using master.passwd db everything would at > least appear centralized:) Consider how many people will use this. Do you really believe that someone will change pwd.h for this reason? > Then add a special class which if the user belongs to gets > te special treatment? (maybe not too complicated..) That's exactly what I wanted to do. > Since master.passwd has 10 fields and that is intentional here is a > thought. Maybe using a special pointer like '+' is used for yp in > master.passwd. Funny idea. But YP is sth. completely different in this setting. It's where you get your password from not the other way round. The only thing you could do this way is marking it. But you have to use a dedicated login-facility anyway, while YP auth is integrated with all of the standard login-facilities. So this won't be of much use. > Another thought, add another ':' separated field into master.passwd. > This with the cur key on a per $USER $HOME basis. If it is unpopulated > of does not exist then ignore it for that $USER? well, pwd.h, you know...
