Re: [Chicken-hackers] user-information update for OpenBSD

Peter Bex scripsit: > Yeah, but what if you're writing, say, a login manager or ssh replacement > in Scheme? Then you need to be able to crypt & compare the password and > preferably use a portable API to get the crypted password. Then make such a portable API and don't try to use getpasswd()

Re: [Chicken-hackers] user-information update for OpenBSD

On Tue, Jul 19, 2016 at 12:13:28PM -0400, John Cowan wrote: > Christian Kellermann scripsit: > > > Maybe it makes sense to split out the sensitive information from the > > user-information for all Operating systems and thinking of another set > > of procedures that will produce the credentials.

Re: [Chicken-hackers] user-information update for OpenBSD

Christian Kellermann scripsit: > Maybe it makes sense to split out the sensitive information from the > user-information for all Operating systems and thinking of another set > of procedures that will produce the credentials. These can then use OS > specific functions to get at the information.

Re: [Chicken-hackers] user-information update for OpenBSD

* Timo Myyrä [160719 12:30]: > I think that would be more sensible approach. user-information would return > info > from /etc/passwd and then another procedure to get the encrypted password. > > That would probably happen for 5.0? Yes, 5.0 is the ultimate excuse to

Re: [Chicken-hackers] user-information update for OpenBSD

Christian Kellermann writes: > * Timo Myyrä [160719 09:20]: > >> Hi, >> >> OpenBSD-current was changed so that shadow database isn't opened by default >> anymore: >> http://article.gmane.org/gmane.os.openbsd.cvs/155646 >> >> This affects calls to