Re: openssl(1) passwd chunck canary corrupted

2018-08-09 Thread Theo Buehler
On Thu, Aug 09, 2018 at 08:45:03AM +0200, Theo Buehler wrote: > On Wed, Aug 08, 2018 at 05:53:56PM +0200, Theo Buehler wrote: > > On Wed, Aug 08, 2018 at 02:45:29PM +0100, Ricardo Mestre wrote: > > > Hi, > > > > > > When openssl(1) passwd is invoked without passing in the `password' as > > >

Re: openssl(1) passwd chunck canary corrupted

2018-08-09 Thread Theo Buehler
On Wed, Aug 08, 2018 at 05:53:56PM +0200, Theo Buehler wrote: > On Wed, Aug 08, 2018 at 02:45:29PM +0100, Ricardo Mestre wrote: > > Hi, > > > > When openssl(1) passwd is invoked without passing in the `password' as > > argument > > , meaning interactively, and if the password is 10 or more

Re: openssl(1) passwd chunck canary corrupted

2018-08-08 Thread Theo Buehler
On Wed, Aug 08, 2018 at 02:45:29PM +0100, Ricardo Mestre wrote: > Hi, > > When openssl(1) passwd is invoked without passing in the `password' as > argument > , meaning interactively, and if the password is 10 or more characters it will > show the following memory corruption error, and using

openssl(1) passwd chunck canary corrupted

2018-08-08 Thread Ricardo Mestre
Hi, When openssl(1) passwd is invoked without passing in the `password' as argument , meaning interactively, and if the password is 10 or more characters it will show the following memory corruption error, and using -crypt which is the default: openssl(43025) in free(): chunck canary corrupted