public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Calum Mackay <calum.mackay@oracle.com>
To: Olga Kornievskaia <aglo@umich.edu>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	Chuck Lever <chuck.lever@oracle.com>
Subject: ktls-utils: question about certificate verification
Date: Thu, 20 Jun 2024 22:44:32 +0100	[thread overview]
Message-ID: <d489e2d7-d4ed-424b-8994-6abf36a01e06@oracle.com> (raw)

hi Olga,

A few weeks ago you and Chuck were discussing duplication requirements 
of the hostname in the CN field versus SAN extension in the certificate:

	https://lore.kernel.org/linux-nfs/CAN-5tyENK71L1C=6NwdB4mkxxf1qYZ2-4e-p8FQM=SmA3tMT_g@mail.gmail.com/


For what it's worth, my own testing showed that the SAN DNS: element 
doesn't need to duplicate the CN.

This is especially relevant in the case where the full DNS name is > 64 
chars, which is not strictly allowed as a CN (and openssl for example 
enforces that limit).

In that case, it works to put the short hostname in the CN, and the full 
DNS name in a SAN DNS: extension. There is no need to duplicate the CN 
entry in the SAN extension.

I also noted that using a wildcard CN (e.g. "*.acme.com") does not work.


I've yet to test mounting by IP, but will do so soon.


best wishes,
calum.


             reply	other threads:[~2024-06-20 21:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 21:44 Calum Mackay [this message]
2024-06-21 15:33 ` ktls-utils: question about certificate verification Olga Kornievskaia
2024-06-21 17:39   ` Calum Mackay
2024-06-25 17:31     ` Olga Kornievskaia
2024-06-25 19:48       ` Calum Mackay
2024-06-26  1:04         ` Rick Macklem
2024-06-26 13:29           ` Calum Mackay
2024-06-26 17:33             ` Olga Kornievskaia
  -- strict thread matches above, loose matches on Subject: below --
2024-05-31 17:23 Olga Kornievskaia
2024-05-31 17:27 ` Chuck Lever III
2024-05-31 17:40   ` Olga Kornievskaia
2024-05-31 18:01     ` Chuck Lever III

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=d489e2d7-d4ed-424b-8994-6abf36a01e06@oracle.com \
    --to=calum.mackay@oracle.com \
    --cc=aglo@umich.edu \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    /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