-
Notifications
You must be signed in to change notification settings - Fork 352
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.
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
T5796:backport-add/fixed OCSERV HTTP security headers #2572
Conversation
All those options look like they can be good idea, but I feel really uneasy about changing the hardcoded default setup without giving people a way to disable any of those options. I believe we can only make such changes if we are absolutely certain that they cannot have any adverse effects. I think we should get back to this after 1.3.5 is out. |
I'll leave a context here : those headers were tested by the community / reported as well , basically they are old http vulnerabilities and also are recommend in default template from ocserv : https://gitlab.com/openconnect/ocserv/-/blob/master/doc/sample.config?ref_type=heads but I agree with applied after 1.3.5 , at least we've introduced in 1.4/1.5 |
Let's make it configurable with
For all versions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's make it configurable but not by default
@sever-sever @dmbaturin was added the command to enable http headers : test 1.3.X configuration :
|
Change Summary
http security headers (cherry picked from commit db51546)
Types of changes
Related Task(s)
Related PR(s)
Component(s) name
openconnect
Proposed changes
How to test
00:12:14 dco1 ocserv-worker[7112]: main: CN=oc-srv,O=VyOS,L=Mycity,ST=Delaware,C=US certificate key usage prevents key encipherment; unable to support the RSA ciphersuites; if that is not intent>
Dec 02 00:12:14 dco1 ocserv[7112]: note: setting 'file' as supplemental config option
Dec 02 00:12:18 dco1 ocserv[5989]: sec-mod: sec-mod instance 0 issue cookie
Dec 02 00:12:18 dco1 ocserv[5989]: sec-mod: using 'plain' authentication to authenticate user (session: sBJX91)
Dec 02 00:12:21 dco1 ocserv[5989]: sec-mod: initiating session for user 'tst' (session: sBJX91)
Dec 02 11:49:37 dco1 ocserv[7581]: Parsing plain auth method subconfig using legacy format
Dec 02 11:49:37 dco1 ocserv[7581]: note: vhost:default: setting 'plain' as primary authentication method
Dec 02 11:49:37 dco1 ocserv[7581]: note: setting 'file' as supplemental config option
Dec 02 11:49:37 dco1 ocserv-worker[7581]: main: CN=oc-srv,O=VyOS,L=Mycity,ST=Delaware,C=US certificate key usage prevents key encipherment; unable to support the RSA ciphersuites; if that is not intent>
Dec 02 11:49:40 dco1 ocserv[5989]: sec-mod: sec-mod instance 0 issue cookie
Dec 02 11:49:40 dco1 ocserv[5989]: sec-mod: using 'plain' authentication to authenticate user (session: v61ylj)
Dec 02 11:50:11 dco1 ocserv[5989]: sec-mod: initiating session for user 'tst' (session: v61ylj)
Smoketest result
Checklist: