Skip to content

tls: Add support for matching against OtherName SAN type#34471

Merged
ggreenway merged 24 commits intoenvoyproxy:mainfrom
arulthileeban:other_name_san
Jun 27, 2024
Merged

tls: Add support for matching against OtherName SAN type#34471
ggreenway merged 24 commits intoenvoyproxy:mainfrom
arulthileeban:other_name_san

Conversation

@arulthileeban
Copy link
Copy Markdown
Contributor

Commit Message: tls: Add support for matching against OtherName SAN type

In the current SAN matcher, only DNS, URI, IP, EMAIL types are supported. This change adds support to match against OtherName. A new config field oid is added which helps define the type of OtherName SAN envoy needs to match against.

Risk Level: Low
Testing: Unit Testing
Docs Changes: Added
Release Notes: Added
Fixes #34358

arulthileeban and others added 5 commits June 1, 2024 13:41
Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
@repokitteh-read-only
Copy link
Copy Markdown

Hi @arulthileeban, welcome and thank you for your contribution.

We will try to review your Pull Request as quickly as possible.

In the meantime, please take a look at the contribution guidelines if you have not done so already.

🐱

Caused by: #34471 was opened by arulthileeban.

see: more, trace.

@repokitteh-read-only
Copy link
Copy Markdown

CC @envoyproxy/api-shepherds: Your approval is needed for changes made to (api/envoy/|docs/root/api-docs/).
envoyproxy/api-shepherds assignee is @mattklein123
CC @envoyproxy/api-watchers: FYI only for changes made to (api/envoy/|docs/root/api-docs/).

🐱

Caused by: #34471 was opened by arulthileeban.

see: more, trace.

@arulthileeban
Copy link
Copy Markdown
Contributor Author

/retest

Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
Copy link
Copy Markdown
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

High level question to get started, thanks.

/wait

@ggreenway ggreenway self-assigned this Jun 3, 2024
Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
@mattklein123
Copy link
Copy Markdown
Member

/lgtm api

@repokitteh-read-only repokitteh-read-only bot removed the api label Jun 6, 2024
@mattklein123 mattklein123 removed their assignment Jun 6, 2024
Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
@repokitteh-read-only repokitteh-read-only bot added api and removed waiting labels Jun 6, 2024
ggreenway
ggreenway previously approved these changes Jun 27, 2024
Copy link
Copy Markdown
Member

@ggreenway ggreenway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this looks good.

I was thinking about the question of validating the type specifically or not, and I think it is probably ok not to because you are validating against a specific OID, and I think that is sufficient.

There's a merge conflict with the changelog; please merge main and fix the conflict.

/wait

Signed-off-by: Arul Thileeban Sagayam <arulthileeban@vt.edu>
@arulthileeban
Copy link
Copy Markdown
Contributor Author

Thanks for the review @ggreenway. Fixed the conflict and updated the branch

@ggreenway
Copy link
Copy Markdown
Member

You have spelling failures in the format check; you can put backticks around words in comments to exclude them from spellcheck

Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
@arulthileeban
Copy link
Copy Markdown
Contributor Author

You have spelling failures in the format check; you can put backticks around words in comments to exclude them from spellcheck

Thanks. Updated it

Copy link
Copy Markdown
Member

@ggreenway ggreenway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, one more fix: can you add test coverage for V_ASN1_BMPSTRING? I was looking at the coverage report (https://storage.googleapis.com/envoy-pr/868779a/coverage/source/common/tls/utility.cc.gcov.html) and that case is missed.

/wait

Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
@arulthileeban
Copy link
Copy Markdown
Contributor Author

Sorry, one more fix: can you add test coverage for V_ASN1_BMPSTRING? I was looking at the coverage report (https://storage.googleapis.com/envoy-pr/868779a/coverage/source/common/tls/utility.cc.gcov.html) and that case is missed.

/wait

My bad. I missed that one. Added the change required

ggreenway
ggreenway previously approved these changes Jun 27, 2024
Copy link
Copy Markdown
Member

@ggreenway ggreenway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@ggreenway ggreenway enabled auto-merge (squash) June 27, 2024 21:39
Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
auto-merge was automatically disabled June 27, 2024 21:52

Head branch was pushed to by a user without write access

@ggreenway ggreenway enabled auto-merge (squash) June 27, 2024 22:54
@ggreenway ggreenway merged commit aef38c4 into envoyproxy:main Jun 27, 2024
cainelli pushed a commit to cainelli/envoy that referenced this pull request Jul 5, 2024
…34471)

In the current SAN matcher, only DNS, URI, IP, EMAIL types are supported. This change adds support to match against OtherName. A new config field oid is added which helps define the type of OtherName SAN envoy needs to match against.

Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
Signed-off-by: Fernando Cainelli <fernando.cainelli-external@getyourguide.com>
cainelli pushed a commit to cainelli/envoy that referenced this pull request Jul 5, 2024
…34471)

In the current SAN matcher, only DNS, URI, IP, EMAIL types are supported. This change adds support to match against OtherName. A new config field oid is added which helps define the type of OtherName SAN envoy needs to match against.

Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
Signed-off-by: Fernando Cainelli <fernando.cainelli-external@getyourguide.com>
cainelli pushed a commit to cainelli/envoy that referenced this pull request Jul 5, 2024
…34471)

In the current SAN matcher, only DNS, URI, IP, EMAIL types are supported. This change adds support to match against OtherName. A new config field oid is added which helps define the type of OtherName SAN envoy needs to match against.

Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
Signed-off-by: Fernando Cainelli <fernando.cainelli-external@getyourguide.com>
cainelli pushed a commit to cainelli/envoy that referenced this pull request Jul 5, 2024
…34471)

In the current SAN matcher, only DNS, URI, IP, EMAIL types are supported. This change adds support to match against OtherName. A new config field oid is added which helps define the type of OtherName SAN envoy needs to match against.

Signed-off-by: Arul Thileeban Sagayam <arul.thilee@gmail.com>
Signed-off-by: Fernando Cainelli <fernando.cainelli-external@getyourguide.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow OtherName type in SAN matching

5 participants