Date: Fri, 24 Aug 2018 09:25:11 +0700 From: Olivier <Olivier.Nicole@cs.ait.ac.th> To: freebsd-questions@freebsd.org Subject: Re: What hash to use Message-ID: <wu7lg8wwlfc.fsf@banyan.cs.ait.ac.th> In-Reply-To: <74a041fe-b00a-673e-c43f-b72aa04e5297@razorfever.net> (482254ac@razorfever.net)
next in thread | previous in thread | raw e-mail | index | archive | help
"Derek (freebsd lists)" <482254ac@razorfever.net> writes: > On 2018-08-23 05:16 AM, Olivier wrote: >> I am using a tools that hashes the passwords in the form of >> $2b$10$OQBll77HJqnOR.zqK2jx8ukE6m68Azc7nrsgRdcT6bVfERRmzFV4. >> >> What magic tool can I use in freeBSD to do the same hashing? >> > > Try this (cdemo.c): > > > > Then: > > cc -lcrypt -o cdemo cdemo.c > ./cdemo > > This is okay for a one-off. > > You might wire stdin to read the salt, or for bonus points make > your own salt generator. > > Additionally, it's likely not a good idea to read the password > from the command-line (argv+argc). A file descriptor (e.g. > stdin) of some kind would be better, as it will show up in shell > history and the process table. > > Some languages, e.g. python, php, etc will have a library to do > this for you as well. Thank you Derek, I will give it a try. I started looking in Perl, but could not find anything. I am trying to automatically generate 100 accounts for a software, I don't want to create them with the web interface, so having the password on the history is not a problem (and I am asked to have the password=username, so the quality of password is not a worry :) Best regards, Olivier
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?wu7lg8wwlfc.fsf>