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.

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

Future content: Server: Medium-Risk Configuration #7

Closed
akkornel opened this issue Apr 6, 2018 · 2 comments
Closed

Future content: Server: Medium-Risk Configuration #7

akkornel opened this issue Apr 6, 2018 · 2 comments
Labels
content Web site content enhancement New feature or request

Comments

@akkornel
Copy link
Member

akkornel commented Apr 6, 2018

Assuming we get approval for Medium Risk, I expect some changes would be needed in endpoint configuration. Just off-hand, I can think of the following:

  • Require at least TLS 1.1 (in grid-security configuration)
  • Log all transfers (in GridFTP configuration)
  • Disable the RSA ciphers (in grid-security configuration), for forward-secrecy. For example, consider the cipher string DHE:ECDHE:!LOW:!MEDIUM. This cannot be done until GridFTP and MyProxy are updated to enable DH/DHE ciphers. See Globus Support request #309315.
@akkornel akkornel added enhancement New feature or request content Web site content labels Apr 6, 2018
@rmarinshaw
Copy link

rmarinshaw commented Apr 8, 2018 via email

@akkornel
Copy link
Member Author

akkornel commented Oct 7, 2018

I've reviewed all of the pages, and I think all of the Medium Risk requirements are addressed, except for backup & restore. That one is covered by #8, so I think this is OK to close!

@akkornel akkornel closed this as completed Oct 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Web site content enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants