From: Bhaskar Chowdhury <bhaskarlinux73@gmail.com>
To: Daniel Mentz <danielmentz@google.com>
Cc: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
masahiroy@kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel:gen_kheaders:Replace md5sum to sha256sum
Date: Sat, 24 Sep 2022 03:02:32 +0530 [thread overview]
Message-ID: <Yy4l8AVyoEJtV+Vm@Gentoo> (raw)
In-Reply-To: <CAE2F3rDymUUDyXrxFyhSGe4k1jrsZih2DbXViA23wAND=XJuyg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
On 11:12 Fri 23 Sep 2022, Daniel Mentz wrote:
>On Fri, Sep 23, 2022 at 4:06 AM Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote:
>> Thought to apply a better encryption mechanism.
>
>MD5 and SHA256 are secure (or, in the case of MD5, not so secure) hash
>algorithms, not encryption mechanisms.
>
>> Replace all occurance of md5sum to sha256sum .
>
>Looking at this script, I'm not convinced that it relies on MD5 being
>a cryptophically secure hash function. It appears to me as if this
>script uses MD5 to simply detect innocent changes to a set of files as
>opposed to guarding against malicious attacks. I also found that
>sha256sum takes almost three times longer than md5sum. So, in the
>absence of security requirements, md5sum might actually be the better
>choice because it's faster.
Al righto! Then...no issues, give it a pass.
--
Thanks,
Bhaskar
"Here's looking at you kid"-- Casablanca
https://about.me/unixbhaskar
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-09-23 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 11:03 Bhaskar Chowdhury
2022-09-23 18:12 ` Daniel Mentz
2022-09-23 21:32 ` Bhaskar Chowdhury [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yy4l8AVyoEJtV+Vm@Gentoo \
--to=bhaskarlinux73@gmail.com \
--cc=danielmentz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=unixbhaskar@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®