diff options
author | Juan J. Martinez <jjm@usebox.net> | 2024-04-20 13:43:19 +0100 |
---|---|---|
committer | Juan J. Martinez <jjm@usebox.net> | 2024-04-20 13:43:19 +0100 |
commit | 4fcdc4a237a217262c29e9b1a1804dda410ba0a0 (patch) | |
tree | 792dce23d9bd3c307c1b8d300034d8e4f409e6a8 /README.md | |
parent | 9a60fc8286960bf4efd69ebe152741306db59887 (diff) | |
download | spacebeans-4fcdc4a237a217262c29e9b1a1804dda410ba0a0.tar.gz spacebeans-4fcdc4a237a217262c29e9b1a1804dda410ba0a0.zip |
Removed auto-generated cert functionality
It wasn't a great idea to start with (I never used it), so I decided it
was best if it was removed.
Generating self signed certificates is easy enough.
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 12 |
1 files changed, 0 insertions, 12 deletions
@@ -15,7 +15,6 @@ Some of the **SpaceBeans** features: - Virtual hosting, with SNI support - User directories support - Classic CGI scripts - - User provided certificates or auto-generated in memory (for development) - Configurable SSL engine (e.g. TLSv1.2 and/or TLSv1.3), with configurable ciphers Check [CHANGES](CHANGES.md) to see what's new in the latest release. @@ -47,17 +46,6 @@ You should evaluate your security requirements when running **SpaceBeans**. In this section *TOFU* refers to "Trust On First Use". -### Auto-generated self-signed certificate - -This is the easiest option, no need to store securely the certificate. The -downside is that you get a new certificate every time you start the service, -and that's bad for TOFU validation. - -This is recommended **only for development** and not for a service facing the -Internet. - -Comment out the `key-store` section on your virtual host and you are done. - ### Self-signed certificate You can generate a self signed certificate using Java's `keytool`: |