Hi!
Am 22.07.2022 um 21:10 schrieb Mikhail Koliada:
What do you think?
I like the idea and would like to see that change.
Conrad
On Sat, Jul 23, 2022 at 08:55:14PM -0400, Mike Gilbert wrote:
> On Fri, Jul 22, 2022 at 3:10 PM Mikhail Koliada wrote:
> >
> > Hello!
> >
> > This idea has been fluctuating in my head for quite a while given that the
> > migration had happened
> > a while ago [0] and some other major
On 7/25/2022 16:29, John Helmert III wrote:
> On Mon, Jul 25, 2022 at 03:59:59PM -0400, Joshua Kinard wrote:
>> On 7/25/2022 15:30, Joshua Kinard wrote:
>> [snip]
>>
>>>
>>> Some really quick looking around, I'm not finding any substantive
>>> discussions on why yescrypt is better than argon2. It
On Mon, Jul 25, 2022 at 03:59:59PM -0400, Joshua Kinard wrote:
> On 7/25/2022 15:30, Joshua Kinard wrote:
> [snip]
>
> >
> > Some really quick looking around, I'm not finding any substantive
> > discussions on why yescrypt is better than argon2. It so far seems that it
> > just got implemented
On 7/25/2022 15:30, Joshua Kinard wrote:
[snip]
>
> Some really quick looking around, I'm not finding any substantive
> discussions on why yescrypt is better than argon2. It so far seems that it
> just got implemented in libxcrypt sooner than argon2 did, so that's why
> there is this sudden
On 7/25/2022 15:34, John Helmert III wrote:
> On Mon, Jul 25, 2022 at 03:30:08PM -0400, Joshua Kinard wrote:
[snip]
>>
>> "yescrypt" is an odd name for a hashing algorithm. I looked it up on
>> Wikipedia, and it just redirects to the 2013 Password Hashing Competition
>> (PHC)[1], in which
On Mon, Jul 25, 2022 at 03:30:08PM -0400, Joshua Kinard wrote:
> On 7/25/2022 14:44, Sam James wrote:
> >
> >
> >> On 22 Jul 2022, at 20:10, Mikhail Koliada wrote:
> >>
> >> Hello!
> >>
> >> This idea has been fluctuating in my head for quite a while given that the
> >> migration had happened
On 7/25/2022 14:44, Sam James wrote:
>
>
>> On 22 Jul 2022, at 20:10, Mikhail Koliada wrote:
>>
>> Hello!
>>
>> This idea has been fluctuating in my head for quite a while given that the
>> migration had happened
>> a while ago [0] and some other major distributions have already adopted
>>
> On 22 Jul 2022, at 20:10, Mikhail Koliada wrote:
>
> Hello!
>
> This idea has been fluctuating in my head for quite a while given that the
> migration had happened
> a while ago [0] and some other major distributions have already adopted
> yescrypt as their default algo
> by now [1]. For
> On 25 Jul 2022, at 15:35, Peter Stuge wrote:
>
> Mikhail Koliada wrote:
>> This idea has been fluctuating in my head for quite a while given
>> that the migration had happened a while ago [0] and some other
>> major distributions have already adopted yescrypt as their default algo
>> by now
On Mon, Jul 25, 2022 at 11:11 AM Marek Szuba wrote:
>
> On 2022-07-25 15:35, Peter Stuge wrote:
>
> > Please only do that based on proven merit and nothing else.
>
> https://pthree.org/2018/05/23/do-not-use-sha256crypt-sha512crypt-theyre-dangerous/
> , https://www.password-hashing.net/ , the fact
On 2022-07-25 15:35, Peter Stuge wrote:
Mikhail Koliada wrote:
This idea has been fluctuating in my head for quite a while given
that the migration had happened a while ago [0] and some other
major distributions have already adopted yescrypt as their default algo
by now [1].
Please only do
Mikhail Koliada wrote:
> This idea has been fluctuating in my head for quite a while given
> that the migration had happened a while ago [0] and some other
> major distributions have already adopted yescrypt as their default algo
> by now [1].
Please only do that based on proven merit and nothing
On Fri, Jul 22, 2022 at 3:10 PM Mikhail Koliada wrote:
>
> Hello!
>
>
>
> This idea has been fluctuating in my head for quite a while given that the
> migration had happened
>
> a while ago [0] and some other major distributions have already adopted
> yescrypt as their default algo
>
> by now
14 matches
Mail list logo
