Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Alan Dekok: TLS Server Name Indication #50 #2

Open
haussli opened this issue May 25, 2022 · 2 comments
Open

Alan Dekok: TLS Server Name Indication #50 #2

haussli opened this issue May 25, 2022 · 2 comments
Assignees
@haussli

Comments

@haussli
Copy link
Owner

haussli commented May 25, 2022

Importing from haussli/draft-dahm-opsawg-tacacs-security#50

[dcmgashcisco] commented [on Apr 14]

It would be good to mention that TLS Server Name Indication (SNI) SHOULD be supported (https://datatracker.ietf.org/doc/html/rfc6066#section-3). That way one server can act as the TACACS+ host for multiple domains, and switch between them using SNI.
@haussli
Copy link
Owner Author

haussli commented May 25, 2022

Issue haussli/draft-dahm-opsawg-tacacs-security#34 addressed this. We closed it w/o addressing, thinking that there might not be desire for this.

Should we re-open 34? Do so if there is more demand? Wait for adoption?

@haussli haussli mentioned this issue May 25, 2022
Closed
@haussli haussli self-assigned this Jul 12, 2022
@haussli
Copy link
Owner Author

haussli commented Mar 13, 2023

Addressed in 15b0f4d, if everyone agrees.

haussli added a commit that referenced this issue Mar 13, 2023
@haussli
Add a SHOULD support for TLS Server Name Indicator (SNI) in Sections TLS
379c0f0 
Identification and Security Considerations.

This addresses PR #2.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@haussli haussli

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@haussli