Skip to content

SECURITY: The HTTP Unix daemon now uses a much more secure set of ciphers as default. #97

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

Merged
merged 1 commit into from
Jun 29, 2017

Conversation

triska
Copy link
Member

@triska triska commented Jun 28, 2017

The goal is to make setting up secure HTTPS servers easy for
users. With the new default, you obtain grade A at ssllabs.com for
your servers, whereas you previously obtained only F.

Future SWI-Prolog versions will likewise enable default ciphers that
are deemed secure at the time of the respective release, and at the
same time ensure compatibility with all but the most exotic or
outdated devices.

Note that obsolete ciphers must be disabled to reliably prevent
protocol downgrade attacks.

…hers as default.

The goal is to make setting up secure HTTPS servers easy for
users. With the new default, you obtain grade A at ssllabs.com for
your servers, whereas you previously obtained only F.

Future SWI-Prolog versions will likewise enable default ciphers that
are deemed secure at the time of the respective release, and at the
same time ensure compatibility with all but the most exotic or
outdated devices.

Note that obsolete ciphers *must* be disabled to reliably prevent
protocol downgrade attacks.
@JanWielemaker JanWielemaker merged commit b976969 into SWI-Prolog:master Jun 29, 2017
@JanWielemaker
Copy link
Member

Thanks. I've moved things around a little such that it is also used by more low-level APIs and the cipher predicate is public so it can be inspected and documented. Rebuilding the US server ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants