Todo #9868: Add clientAuth EKU to Server type certificates - pfSense - pfSense bugtracker

Actions

Copy link

Todo #9868

closed

Add clientAuth EKU to Server type certificates

Added by Jim Pingle about 5 years ago. Updated almost 5 years ago.

Status:

Resolved

Priority:

Low

Assignee:

Jim Pingle

Category:

Certificates

Target version:

2.4.5

Start date:

10/31/2019

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Description

Some cases may require a server certificate to be used to authenticate a server (to client) and authenticate as a client (to another server). Currently, server certificates only include the serverAuth EKU, but both may be present.

Additionally, the ISRG-CPS-v2.6 standard followed by Let's Encrypt contains both for end entity certificates.

Looking at some other standards like RFC 5280 (EKU), RFC 5216/RFC 5281 (EAP-[T]TLS) they all mention things in a permissive way, meaning that the presence of specific values enables uses. I don't see anything that would exclude or fail based on the presence of an EKU.

Actions

Copy link

Updated by Jim Pingle about 5 years ago

Status changed from New to Feedback
% Done changed from 0 to 100

Applied in changeset 46869dd2b5ebf32e8297d65f98444fb38d314336.

Actions

Copy link

Updated by Viktor Gurov about 5 years ago

Jim Pingle wrote:

Applied in changeset 46869dd2b5ebf32e8297d65f98444fb38d314336.

Tested on 2.5.0.a.20191109.1723

Resolved -

Serial: 11
Signature Digest: RSA-SHA256
SAN: DNS:servertest, IP Address:192.168.1.1
KU: Digital Signature, Key Encipherment
EKU: TLS Web Server Authentication, TLS Web Client Authentication, IP Security IKE Intermediate
Key Type: RSA
Key Size: 2048
DN: /CN=servertest
...