All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: Steve French <smfrench@gmail.com>, John Sanpe <sanpeqf@gmail.com>,
	stfrench@microsoft.com, linkinjeon@kernel.org, pc@manguebit.com,
	sprasad@microsoft.com, linux-cifs@vger.kernel.org,
	llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	samba-technical <samba-technical@lists.samba.org>,
	Jeremy Allison <jra@samba.org>
Subject: Re: [PATCH] fs/smb: using crypto lib instead cifs_arc4
Date: Sun, 5 Nov 2023 11:33:03 -0800	[thread overview]
Message-ID: <20231105193303.GA91123@sol.localdomain> (raw)
In-Reply-To: <CAN05THRzP6uFyza90kBy5Ku8yGKMi2K5VYX1TJsjbvQrLfAEiw@mail.gmail.com>

On Mon, Oct 23, 2023 at 05:42:11AM +1000, ronnie sahlberg wrote:
> You are right. The reason that arc4 and friend were moved into cifs
> was because the crypto guys told us "we will delete these algorithms
> from the crypto library"

This was suggested for md4 but not for arc4.  arc4 still has multiple users in
the kernel, so having it as a library makes sense.

- Eric

  reply	other threads:[~2023-11-05 19:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22 18:39 [PATCH] fs/smb: using crypto lib instead cifs_arc4 John Sanpe
2023-10-22 19:38 ` Steve French
2023-10-22 19:40   ` Steve French
2023-10-22 19:42     ` ronnie sahlberg
2023-11-05 19:33       ` Eric Biggers [this message]
2023-11-05 17:28 ` smb cifs: Linux 6.7 pre rc-1 kernel dump in smb2_get_aead_req Damian Tometzki
     [not found]   ` <CAH2r5msde65PMtn-96VZDAQkT_rq+e-2G4O+zbPUR8zSWGxMsg@mail.gmail.com>
2023-11-05 19:36     ` Eric Biggers
2023-11-05 19:40       ` Damian Tometzki
2023-11-05 20:15         ` Eric Biggers
2023-11-06  7:36           ` Damian Tometzki
2023-11-06 10:01             ` David Howells
2023-11-06 14:40             ` [PATCH] cifs: Fix encryption of cleared, but unset rq_iter data buffers David Howells
2023-11-06 15:41               ` Paulo Alcantara
2023-11-07  5:18               ` Damian Tometzki
2023-11-07 18:51                 ` Steve French

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=20231105193303.GA91123@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=jra@samba.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pc@manguebit.com \
    --cc=ronniesahlberg@gmail.com \
    --cc=samba-technical@lists.samba.org \
    --cc=sanpeqf@gmail.com \
    --cc=smfrench@gmail.com \
    --cc=sprasad@microsoft.com \
    --cc=stfrench@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.