cosmopolitan/third_party/mbedtls/test/test_suite_ssl.datax

10635 lines
330 KiB
Text
Raw Normal View History

Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
Test calback buffer sanity
0
Callback buffer test: Exercise simple write/read
1:int:50:int:25:int:25:int:25:int:25:int:0:int:0:int:0:int:0
Callback buffer test: Filling up the buffer
1:int:50:int:50:int:50:int:50:int:50:int:0:int:0:int:0:int:0
Callback buffer test: Filling up the buffer in two steps
1:int:50:int:20:int:20:int:0:int:0:int:30:int:30:int:50:int:50
Callback buffer test: Reading out the buffer in two steps
1:int:50:int:50:int:50:int:30:int:30:int:0:int:0:int:20:int:20
Callback buffer test: Data wraps in buffer
1:int:50:int:45:int:45:int:10:int:10:int:10:int:10:int:45:int:45
Callback buffer test: Data starts at the end
1:int:50:int:50:int:50:int:49:int:49:int:10:int:10:int:11:int:11
Callback buffer test: Can write less than requested
1:int:50:int:75:int:50:int:30:int:30:int:25:int:25:int:45:int:45
Callback buffer test: Can read less than requested
1:int:50:int:25:int:25:int:30:int:25:int:5:int:5:int:5:int:5
Callback buffer test: Writing to full buffer
1:int:50:int:50:int:50:int:0:int:0:int:10:int:0:int:60:int:50
Callback buffer test: Reading from empty buffer
1:int:50:int:0:int:0:int:10:int:0:int:0:int:0:int:0:int:0
Test mock socket sanity
2
Test mock blocking TCP connection
3:int:1
Test mock non-blocking TCP connection
3:int:0
Test mock blocking TCP connection (interleaving)
4:int:1
Test mock non-blocking TCP connection (interleaving)
4:int:0
Message queue - sanity
5
Message queue - basic test
6
Message queue - overflow/underflow
7
Message queue - interleaved
8
Message queue - insufficient buffer
9
Message transport mock - uninitialized structures
10
Message transport mock - basic test
11
Message transport mock - queue overflow/underflow
12
Message transport mock - socket overflow
13
Message transport mock - truncated message
14
Message transport mock - socket read error
15
Message transport mock - one-way interleaved sends/reads
16
Message transport mock - two-way interleaved sends/reads
17
Test mbedtls_endpoint sanity for the client
33:exp:0
Test mbedtls_endpoint sanity for the server
33:exp:1
Test moving clients handshake to state: HELLO_REQUEST
34:exp:0:exp:2:int:1
Test moving clients handshake to state: CLIENT_HELLO
34:exp:0:exp:3:int:1
Test moving clients handshake to state: SERVER_HELLO
34:exp:0:exp:4:int:1
Test moving clients handshake to state: SERVER_CERTIFICATE
34:exp:0:exp:5:int:1
Test moving clients handshake to state: SERVER_KEY_EXCHANGE
34:exp:0:exp:6:int:1
Test moving clients handshake to state: CERTIFICATE_REQUEST
34:exp:0:exp:7:int:1
Test moving clients handshake to state: SERVER_HELLO_DONE
34:exp:0:exp:8:int:1
Test moving clients handshake to state: CLIENT_CERTIFICATE
34:exp:0:exp:9:int:1
Test moving clients handshake to state: CLIENT_KEY_EXCHANGE
34:exp:0:exp:10:int:1
Test moving clients handshake to state: CERTIFICATE_VERIFY
34:exp:0:exp:11:int:1
Test moving clients handshake to state: CLIENT_CHANGE_CIPHER_SPEC
34:exp:0:exp:12:int:1
Test moving clients handshake to state: CLIENT_FINISHED
34:exp:0:exp:13:int:1
Test moving clients handshake to state: SERVER_CHANGE_CIPHER_SPEC
34:exp:0:exp:14:int:1
Test moving clients handshake to state: SERVER_FINISHED
34:exp:0:exp:15:int:1
Test moving clients handshake to state: FLUSH_BUFFERS
34:exp:0:exp:16:int:1
Test moving clients handshake to state: HANDSHAKE_WRAPUP
34:exp:0:exp:17:int:1
Test moving clients handshake to state: HANDSHAKE_OVER
34:exp:0:exp:18:int:1
Test moving servers handshake to state: HELLO_REQUEST
34:exp:1:exp:2:int:1
Test moving servers handshake to state: CLIENT_HELLO
34:exp:1:exp:3:int:1
Test moving servers handshake to state: SERVER_HELLO
34:exp:1:exp:4:int:1
Test moving servers handshake to state: SERVER_CERTIFICATE
34:exp:1:exp:5:int:1
Test moving servers handshake to state: SERVER_KEY_EXCHANGE
34:exp:1:exp:6:int:1
Test moving servers handshake to state: CERTIFICATE_REQUEST
34:exp:1:exp:7:int:1
Test moving servers handshake to state: SERVER_HELLO_DONE
34:exp:1:exp:8:int:1
Test moving servers handshake to state: CLIENT_CERTIFICATE
34:exp:1:exp:9:int:1
Test moving servers handshake to state: CLIENT_KEY_EXCHANGE
34:exp:1:exp:10:int:1
Test moving servers handshake to state: CERTIFICATE_VERIFY
34:exp:1:exp:11:int:1
Test moving servers handshake to state: CLIENT_CHANGE_CIPHER_SPEC
34:exp:1:exp:12:int:1
Test moving servers handshake to state: CLIENT_FINISHED
34:exp:1:exp:13:int:1
Test moving servers handshake to state: SERVER_CHANGE_CIPHER_SPEC
34:exp:1:exp:14:int:1
Test moving servers handshake to state: SERVER_FINISHED
34:exp:1:exp:15:int:1
Test moving servers handshake to state: FLUSH_BUFFERS
34:exp:1:exp:16:int:1
Test moving servers handshake to state: HANDSHAKE_WRAPUP
34:exp:1:exp:17:int:1
Test moving servers handshake to state: HANDSHAKE_OVER
34:exp:1:exp:18:int:1
Negative test moving clients ssl to state: VERIFY_REQUEST_SENT
34:exp:0:exp:19:int:0
Negative test moving servers ssl to state: NEW_SESSION_TICKET
34:exp:1:exp:20:int:0
Handshake, SSL3
depends_on:0:1:2
35:int:0:exp:21:exp:21:exp:21:exp:21:exp:21
Handshake, tls1
depends_on:3:4
35:int:0:exp:22:exp:22:exp:22:exp:22:exp:22
Handshake, tls1_1
depends_on:5:4
35:int:0:exp:23:exp:23:exp:23:exp:23:exp:23
Handshake, tls1_2
depends_on:6
35:int:0:exp:24:exp:24:exp:24:exp:24:exp:24
Handshake, ECDHE-RSA-AES256-GCM-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:9:10:1:2:11
37:char*:"ECDHE-RSA-AES256-GCM-SHA384":exp:25:int:0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
Handshake, RSA-AES128-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:12:9:1:2
37:char*:"RSA-AES128-CCM":exp:25:int:0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
Handshake, DHE-RSA-AES256-CBC-SHA256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:13:1:2:40
37:char*:"DHE-RSA-AES256-CBC-SHA256":exp:25:int:0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
Handshake, ECDHE-ECDSA-AES256-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:12:14:15:2
37:char*:"ECDHE-ECDSA-AES256-CCM":exp:26:int:0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
Handshake, ECDH-ECDSA-CAMELLIA-256-CBC-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:4:14:15:2:16
37:char*:"ECDH-ECDSA-CAMELLIA-256-CBC-SHA384":exp:26:int:0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
Handshake, PSK-AES128-CBC-SHA
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:4:1:2:41
36:char*:"PSK-AES128-CBC-SHA":exp:25:hex:"abc123":int:0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS Handshake, tls1_1
depends_on:5:4:17
35:int:1:exp:23:exp:23:exp:23:exp:23:exp:23
DTLS Handshake, tls1_2
depends_on:6:17
35:int:1:exp:24:exp:24:exp:24:exp:24:exp:24
DTLS Handshake, ECDHE-RSA-AES256-GCM-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:9:10:1:2:11:17
37:char*:"ECDHE-RSA-AES256-GCM-SHA384":exp:25:int:1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS Handshake, RSA-AES128-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:12:9:1:2:17
37:char*:"RSA-AES128-CCM":exp:25:int:1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS Handshake, DHE-RSA-AES256-CBC-SHA256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:13:1:2:17:40
37:char*:"DHE-RSA-AES256-CBC-SHA256":exp:25:int:1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS Handshake, ECDHE-ECDSA-AES256-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:12:14:15:2:17
37:char*:"ECDHE-ECDSA-AES256-CCM":exp:26:int:1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS Handshake, ECDH-ECDSA-CAMELLIA-256-CBC-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:4:14:15:2:16:17
37:char*:"ECDH-ECDSA-CAMELLIA-256-CBC-SHA384":exp:26:int:1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS Handshake, PSK-AES128-CBC-SHA
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:4:1:2:17:41
36:char*:"PSK-AES128-CBC-SHA":exp:25:hex:"abc123":int:1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS Handshake with serialization, tls1_2
depends_on:1:2:17
41
DTLS Handshake fragmentation, MFL=512
depends_on:1:2:17
42:exp:27:int:1:int:1
DTLS Handshake fragmentation, MFL=1024
depends_on:1:2:17
42:exp:28:int:0:int:1
Handshake min/max version check, all -> 1.2
depends_on:6
35:int:0:exp:29:exp:29:exp:29:exp:29:exp:24
Handshake min/max version check, cli max 1.1 -> 1.1
depends_on:5:4
35:int:0:exp:29:exp:22:exp:29:exp:29:exp:22
Handshake min/max version check, srv max 1.1 -> 1.1
depends_on:5:4
35:int:0:exp:29:exp:29:exp:29:exp:22:exp:22
Handshake min/max version check, cli+srv max 1.1 -> 1.1
depends_on:5:4
35:int:0:exp:29:exp:22:exp:29:exp:22:exp:22
Handshake min/max version check, cli max 1.1, srv min 1.1 -> 1.1
depends_on:5:4
35:int:0:exp:29:exp:22:exp:22:exp:29:exp:22
Handshake min/max version check, cli min 1.1, srv max 1.1 -> 1.1
depends_on:5:4
35:int:0:exp:22:exp:29:exp:29:exp:22:exp:22
Handshake min/max version check, cli min 1.2, srv max 1.1 -> fail
depends_on:5:4:6
35:int:0:exp:23:exp:29:exp:29:exp:22:exp:29
Handshake min/max version check, srv min 1.2, cli max 1.1 -> fail
depends_on:5:4:6
35:int:0:exp:29:exp:22:exp:23:exp:29:exp:29
Sending app data via TLS, MFL=512 without fragmentation
depends_on:18
39:exp:27:int:400:int:512:int:1:int:1
Sending app data via TLS, MFL=512 with fragmentation
depends_on:18
39:exp:27:int:513:int:1536:int:2:int:3
Sending app data via TLS, MFL=1024 without fragmentation
depends_on:18
39:exp:28:int:1000:int:1024:int:1:int:1
Sending app data via TLS, MFL=1024 with fragmentation
depends_on:18
39:exp:28:int:1025:int:5120:int:2:int:5
Sending app data via TLS, MFL=2048 without fragmentation
depends_on:18
39:exp:30:int:2000:int:2048:int:1:int:1
Sending app data via TLS, MFL=2048 with fragmentation
depends_on:18
39:exp:30:int:2049:int:8192:int:2:int:4
Sending app data via TLS, MFL=4096 without fragmentation
depends_on:18
39:exp:31:int:4000:int:4096:int:1:int:1
Sending app data via TLS, MFL=4096 with fragmentation
depends_on:18
39:exp:31:int:4097:int:12288:int:2:int:3
Sending app data via TLS without MFL and without fragmentation
39:exp:32:int:16001:int:16384:int:1:int:1
Sending app data via TLS without MFL and with fragmentation
39:exp:32:int:16385:int:100000:int:2:int:7
Sending app data via DTLS, MFL=512 without fragmentation
depends_on:18
40:exp:27:int:400:int:512:int:1:int:1
Sending app data via DTLS, MFL=512 with fragmentation
depends_on:18
40:exp:27:int:513:int:1536:int:0:int:0
Sending app data via DTLS, MFL=1024 without fragmentation
depends_on:18
40:exp:28:int:1000:int:1024:int:1:int:1
Sending app data via DTLS, MFL=1024 with fragmentation
depends_on:18
40:exp:28:int:1025:int:5120:int:0:int:0
Sending app data via DTLS, MFL=2048 without fragmentation
depends_on:18
40:exp:30:int:2000:int:2048:int:1:int:1
Sending app data via DTLS, MFL=2048 with fragmentation
depends_on:18
40:exp:30:int:2049:int:8192:int:0:int:0
Sending app data via DTLS, MFL=4096 without fragmentation
depends_on:18
40:exp:31:int:4000:int:4096:int:1:int:1
Sending app data via DTLS, MFL=4096 with fragmentation
depends_on:18
40:exp:31:int:4097:int:12288:int:0:int:0
Sending app data via DTLS, without MFL and without fragmentation
40:exp:32:int:16001:int:16384:int:1:int:1
Sending app data via DTLS, without MFL and with fragmentation
40:exp:32:int:16385:int:100000:int:0:int:0
DTLS renegotiation: no legacy renegotiation
43:exp:33
DTLS renegotiation: legacy renegotiation
43:exp:34
DTLS renegotiation: legacy break handshake
43:exp:35
DTLS serialization with MFL=512
45:exp:27
DTLS serialization with MFL=1024
45:exp:28
DTLS serialization with MFL=2048
45:exp:30
DTLS serialization with MFL=4096
45:exp:31
DTLS no legacy renegotiation with MFL=512
46:exp:27:exp:33:char*:""
DTLS no legacy renegotiation with MFL=1024
46:exp:28:exp:33:char*:""
DTLS no legacy renegotiation with MFL=2048
46:exp:30:exp:33:char*:""
DTLS no legacy renegotiation with MFL=4096
46:exp:31:exp:33:char*:""
DTLS legacy allow renegotiation with MFL=512
46:exp:27:exp:34:char*:""
DTLS legacy allow renegotiation with MFL=1024
46:exp:28:exp:34:char*:""
DTLS legacy allow renegotiation with MFL=2048
46:exp:30:exp:34:char*:""
DTLS legacy allow renegotiation with MFL=4096
46:exp:31:exp:34:char*:""
DTLS legacy break handshake renegotiation with MFL=512
46:exp:27:exp:35:char*:""
DTLS legacy break handshake renegotiation with MFL=1024
46:exp:28:exp:35:char*:""
DTLS legacy break handshake renegotiation with MFL=2048
46:exp:30:exp:35:char*:""
DTLS legacy break handshake renegotiation with MFL=4096
46:exp:31:exp:35:char*:""
DTLS no legacy renegotiation with MFL=512, ECDHE-RSA-AES256-GCM-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:9:10:11
46:exp:27:exp:33:char*:"ECDHE-RSA-AES256-GCM-SHA384"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS no legacy renegotiation with MFL=1024, ECDHE-RSA-AES256-GCM-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:9:10:11
46:exp:28:exp:33:char*:"ECDHE-RSA-AES256-GCM-SHA384"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS no legacy renegotiation with MFL=2048, ECDHE-RSA-AES256-GCM-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:9:10:11
46:exp:30:exp:33:char*:"ECDHE-RSA-AES256-GCM-SHA384"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS no legacy renegotiation with MFL=4096, ECDHE-RSA-AES256-GCM-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:9:10:11
46:exp:31:exp:33:char*:"ECDHE-RSA-AES256-GCM-SHA384"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy allow renegotiation with MFL=512, ECDHE-RSA-AES256-GCM-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:9:10:11
46:exp:27:exp:34:char*:"ECDHE-RSA-AES256-GCM-SHA384"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy allow renegotiation with MFL=1024, ECDHE-RSA-AES256-GCM-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:9:10:11
46:exp:28:exp:34:char*:"ECDHE-RSA-AES256-GCM-SHA384"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy allow renegotiation with MFL=2048, ECDHE-RSA-AES256-GCM-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:9:10:11
46:exp:30:exp:34:char*:"ECDHE-RSA-AES256-GCM-SHA384"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy allow renegotiation with MFL=4096, ECDHE-RSA-AES256-GCM-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:9:10:11
46:exp:31:exp:34:char*:"ECDHE-RSA-AES256-GCM-SHA384"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy break handshake renegotiation with MFL=512, ECDHE-RSA-AES256-GCM-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:9:10:11
46:exp:27:exp:35:char*:"ECDHE-RSA-AES256-GCM-SHA384"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy break handshake renegotiation with MFL=1024, ECDHE-RSA-AES256-GCM-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:9:10:11
46:exp:28:exp:35:char*:"ECDHE-RSA-AES256-GCM-SHA384"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy break handshake renegotiation with MFL=2048, ECDHE-RSA-AES256-GCM-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:9:10:11
46:exp:30:exp:35:char*:"ECDHE-RSA-AES256-GCM-SHA384"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy break handshake renegotiation with MFL=4096, ECDHE-RSA-AES256-GCM-SHA384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:7:8:9:10:11
46:exp:31:exp:35:char*:"ECDHE-RSA-AES256-GCM-SHA384"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS no legacy renegotiation with MFL=512, RSA-AES128-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:12:9
46:exp:27:exp:33:char*:"RSA-AES128-CCM"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS no legacy renegotiation with MFL=1024, RSA-AES128-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:12:9
46:exp:28:exp:33:char*:"RSA-AES128-CCM"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS no legacy renegotiation with MFL=2048, RSA-AES128-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:12:9
46:exp:30:exp:33:char*:"RSA-AES128-CCM"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS no legacy renegotiation with MFL=4096, RSA-AES128-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:12:9
46:exp:31:exp:33:char*:"RSA-AES128-CCM"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy allow renegotiation with MFL=512, RSA-AES128-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:12:9
46:exp:27:exp:34:char*:"RSA-AES128-CCM"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy allow renegotiation with MFL=1024, RSA-AES128-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:12:9
46:exp:28:exp:34:char*:"RSA-AES128-CCM"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy allow renegotiation with MFL=2048, RSA-AES128-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:12:9
46:exp:30:exp:34:char*:"RSA-AES128-CCM"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy allow renegotiation with MFL=4096, RSA-AES128-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:12:9
46:exp:31:exp:34:char*:"RSA-AES128-CCM"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy break handshake renegotiation with MFL=512, RSA-AES128-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:12:9
46:exp:27:exp:35:char*:"RSA-AES128-CCM"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy break handshake renegotiation with MFL=1024, RSA-AES128-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:12:9
46:exp:28:exp:35:char*:"RSA-AES128-CCM"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy break handshake renegotiation with MFL=2048, RSA-AES128-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:12:9
46:exp:30:exp:35:char*:"RSA-AES128-CCM"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy break handshake renegotiation with MFL=4096, RSA-AES128-CCM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:12:9
46:exp:31:exp:35:char*:"RSA-AES128-CCM"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS no legacy renegotiation with MFL=512, DHE-RSA-AES256-CBC-SHA256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:13
46:exp:27:exp:33:char*:"DHE-RSA-AES256-CBC-SHA256"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS no legacy renegotiation with MFL=1024, DHE-RSA-AES256-CBC-SHA256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:13
46:exp:28:exp:33:char*:"DHE-RSA-AES256-CBC-SHA256"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS no legacy renegotiation with MFL=2048, DHE-RSA-AES256-CBC-SHA256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:13
46:exp:30:exp:33:char*:"DHE-RSA-AES256-CBC-SHA256"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS no legacy renegotiation with MFL=4096, DHE-RSA-AES256-CBC-SHA256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:13
46:exp:31:exp:33:char*:"DHE-RSA-AES256-CBC-SHA256"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy allow renegotiation with MFL=512, DHE-RSA-AES256-CBC-SHA256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:13
46:exp:27:exp:34:char*:"DHE-RSA-AES256-CBC-SHA256"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy allow renegotiation with MFL=1024, DHE-RSA-AES256-CBC-SHA256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:13
46:exp:28:exp:34:char*:"DHE-RSA-AES256-CBC-SHA256"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy allow renegotiation with MFL=2048, DHE-RSA-AES256-CBC-SHA256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:13
46:exp:30:exp:34:char*:"DHE-RSA-AES256-CBC-SHA256"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy allow renegotiation with MFL=4096, DHE-RSA-AES256-CBC-SHA256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:13
46:exp:31:exp:34:char*:"DHE-RSA-AES256-CBC-SHA256"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy break handshake renegotiation with MFL=512, DHE-RSA-AES256-CBC-SHA256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:13
46:exp:27:exp:35:char*:"DHE-RSA-AES256-CBC-SHA256"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy break handshake renegotiation with MFL=1024, DHE-RSA-AES256-CBC-SHA256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:13
46:exp:28:exp:35:char*:"DHE-RSA-AES256-CBC-SHA256"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy break handshake renegotiation with MFL=2048, DHE-RSA-AES256-CBC-SHA256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:13
46:exp:30:exp:35:char*:"DHE-RSA-AES256-CBC-SHA256"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
DTLS legacy break handshake renegotiation with MFL=4096, DHE-RSA-AES256-CBC-SHA256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:13
46:exp:31:exp:35:char*:"DHE-RSA-AES256-CBC-SHA256"
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
SSL DTLS replay: initial state, seqnum 0
18:hex:"":hex:"000000000000":int:0
SSL DTLS replay: 0 seen, 1 arriving
18:hex:"000000000000":hex:"000000000001":int:0
SSL DTLS replay: 0 seen, 0 replayed
18:hex:"000000000000":hex:"000000000000":exp:36
SSL DTLS replay: 0-1 seen, 2 arriving
18:hex:"000000000000000000000001":hex:"000000000002":int:0
SSL DTLS replay: 0-1 seen, 1 replayed
18:hex:"000000000000000000000001":hex:"000000000001":exp:36
SSL DTLS replay: 0-1 seen, 0 replayed
18:hex:"000000000000000000000001":hex:"000000000000":exp:36
SSL DTLS replay: new
18:hex:"abcd12340000abcd12340001abcd12340003":hex:"abcd12340004":int:0
SSL DTLS replay: way new
18:hex:"abcd12340000abcd12340001abcd12340003":hex:"abcd12350000":int:0
SSL DTLS replay: delayed
18:hex:"abcd12340000abcd12340001abcd12340003":hex:"abcd12340002":int:0
SSL DTLS replay: lastest replayed
18:hex:"abcd12340000abcd12340001abcd12340003":hex:"abcd12340003":exp:36
SSL DTLS replay: older replayed
18:hex:"abcd12340000abcd12340001abcd12340003":hex:"abcd12340001":exp:36
SSL DTLS replay: most recent in window, replayed
18:hex:"abcd12340000abcd12340002abcd12340003":hex:"abcd12340002":exp:36
SSL DTLS replay: oldest in window, replayed
18:hex:"abcd12340000abcd12340001abcd1234003f":hex:"abcd12340000":exp:36
SSL DTLS replay: oldest in window, not replayed
18:hex:"abcd12340001abcd12340002abcd1234003f":hex:"abcd12340000":int:0
SSL DTLS replay: just out of the window
18:hex:"abcd12340001abcd12340002abcd1234003f":hex:"abcd1233ffff":exp:36
SSL DTLS replay: way out of the window
18:hex:"abcd12340001abcd12340002abcd1234003f":hex:"abcd12330000":exp:36
SSL DTLS replay: big jump then replay
18:hex:"abcd12340000abcd12340100":hex:"abcd12340100":exp:36
SSL DTLS replay: big jump then new
18:hex:"abcd12340000abcd12340100":hex:"abcd12340101":int:0
SSL DTLS replay: big jump then just delayed
18:hex:"abcd12340000abcd12340100":hex:"abcd123400ff":int:0
SSL SET_HOSTNAME memory leak: call ssl_set_hostname twice
19:char*:"server0":char*:"server1"
SSL session serialization: Wrong major version
32:int:1:int:0:int:0:int:0
SSL session serialization: Wrong minor version
32:int:0:int:1:int:0:int:0
SSL session serialization: Wrong patch version
32:int:0:int:0:int:1:int:0
SSL session serialization: Wrong config
32:int:0:int:0:int:0:int:1
Record crypt, AES128-CBC, 1.2, SHA-384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8
20:exp:37:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, SHA-384, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
20:exp:37:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, SHA-384, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
20:exp:37:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.2, SHA-384, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8:20
20:exp:37:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, SHA-384, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
20:exp:37:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, SHA-384, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
20:exp:37:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.2, SHA-384, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8
20:exp:37:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, SHA-384, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
20:exp:37:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, SHA-384, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
20:exp:37:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.2, SHA-384, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8:20
20:exp:37:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
20:exp:37:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
20:exp:37:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.2, SHA-256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13
20:exp:37:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, SHA-256, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
20:exp:37:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, SHA-256, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
20:exp:37:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.2, SHA-256, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13:20
20:exp:37:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, SHA-256, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
20:exp:37:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, SHA-256, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
20:exp:37:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.2, SHA-256, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13
20:exp:37:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, SHA-256, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
20:exp:37:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, SHA-256, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
20:exp:37:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.2, SHA-256, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13:20
20:exp:37:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
20:exp:37:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
20:exp:37:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.2, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21
20:exp:37:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, SHA-1, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
20:exp:37:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, SHA-1, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
20:exp:37:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.2, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21:20
20:exp:37:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, SHA-1, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
20:exp:37:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, SHA-1, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
20:exp:37:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.2, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21
20:exp:37:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, SHA-1, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
20:exp:37:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, SHA-1, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
20:exp:37:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.2, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21:20
20:exp:37:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
20:exp:37:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
20:exp:37:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.2, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22
20:exp:37:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, MD5, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
20:exp:37:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, MD5, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
20:exp:37:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.2, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22:20
20:exp:37:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, MD5, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
20:exp:37:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, MD5, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
20:exp:37:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.2, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22
20:exp:37:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, MD5, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
20:exp:37:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, MD5, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
20:exp:37:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.2, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22:20
20:exp:37:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, AES128-CBC, 1.2, MD5, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
20:exp:37:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, AES128-CBC, 1.2, MD5, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
20:exp:37:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, AES128-CBC, 1.1, SHA-384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8
20:exp:37:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.1, SHA-384, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8:20
20:exp:37:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.1, SHA-384, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8
20:exp:37:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.1, SHA-384, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8:20
20:exp:37:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.1, SHA-256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13
20:exp:37:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.1, SHA-256, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13:20
20:exp:37:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.1, SHA-256, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13
20:exp:37:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.1, SHA-256, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13:20
20:exp:37:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.1, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21
20:exp:37:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.1, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21:20
20:exp:37:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.1, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21
20:exp:37:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.1, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21:20
20:exp:37:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.1, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22
20:exp:37:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.1, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22:20
20:exp:37:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.1, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22
20:exp:37:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.1, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22:20
20:exp:37:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, AES128-CBC, 1.0, SHA-384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8
20:exp:37:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, AES128-CBC, 1.0, SHA-384, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8:20
20:exp:37:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, AES128-CBC, 1.0, SHA-384, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8
20:exp:37:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, AES128-CBC, 1.0, SHA-384, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8:20
20:exp:37:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, AES128-CBC, 1.0, SHA-256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13
20:exp:37:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, AES128-CBC, 1.0, SHA-256, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13:20
20:exp:37:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, AES128-CBC, 1.0, SHA-256, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13
20:exp:37:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, AES128-CBC, 1.0, SHA-256, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13:20
20:exp:37:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, AES128-CBC, 1.0, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21
20:exp:37:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, AES128-CBC, 1.0, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21:20
20:exp:37:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, AES128-CBC, 1.0, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21
20:exp:37:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, AES128-CBC, 1.0, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21:20
20:exp:37:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, AES128-CBC, 1.0, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22
20:exp:37:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, AES128-CBC, 1.0, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22:20
20:exp:37:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, AES128-CBC, 1.0, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22
20:exp:37:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, AES128-CBC, 1.0, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22:20
20:exp:37:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, AES128-CBC, SSL3, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21
20:exp:37:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, AES128-CBC, SSL3, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21:20
20:exp:37:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, AES128-CBC, SSL3, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21
20:exp:37:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, AES128-CBC, SSL3, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21:20
20:exp:37:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, AES128-CBC, SSL3, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22
20:exp:37:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, AES128-CBC, SSL3, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22:20
20:exp:37:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, AES128-CBC, SSL3, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22
20:exp:37:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, AES128-CBC, SSL3, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22:20
20:exp:37:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, AES-192-CBC, 1.2, SHA-384
depends_on:4:9:6:7:8
20:exp:42:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:9:6:7:8
20:exp:42:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:9:6:7:8
20:exp:42:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.2, SHA-384, EtM
depends_on:4:9:6:7:8:20
20:exp:42:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:9:6:7:8:20
20:exp:42:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:9:6:7:8:20
20:exp:42:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.2, SHA-384, short tag
depends_on:4:9:6:7:8
20:exp:42:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:9:6:7:8
20:exp:42:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:9:6:7:8
20:exp:42:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:9:6:7:8:20
20:exp:42:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:9:6:7:8:20
20:exp:42:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:9:6:7:8:20
20:exp:42:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.2, SHA-256
depends_on:4:9:6:13
20:exp:42:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:9:6:13
20:exp:42:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:9:6:13
20:exp:42:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.2, SHA-256, EtM
depends_on:4:9:6:13:20
20:exp:42:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:9:6:13:20
20:exp:42:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:9:6:13:20
20:exp:42:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.2, SHA-256, short tag
depends_on:4:9:6:13
20:exp:42:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:9:6:13
20:exp:42:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:9:6:13
20:exp:42:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:9:6:13:20
20:exp:42:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:9:6:13:20
20:exp:42:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:9:6:13:20
20:exp:42:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.2, SHA-1
depends_on:4:9:6:21
20:exp:42:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:9:6:21
20:exp:42:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:9:6:21
20:exp:42:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.2, SHA-1, EtM
depends_on:4:9:6:21:20
20:exp:42:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:9:6:21:20
20:exp:42:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:9:6:21:20
20:exp:42:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.2, SHA-1, short tag
depends_on:4:9:6:21
20:exp:42:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:9:6:21
20:exp:42:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:9:6:21
20:exp:42:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:9:6:21:20
20:exp:42:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:9:6:21:20
20:exp:42:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:9:6:21:20
20:exp:42:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.2, MD5
depends_on:4:9:6:22
20:exp:42:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:9:6:22
20:exp:42:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:9:6:22
20:exp:42:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.2, MD5, EtM
depends_on:4:9:6:22:20
20:exp:42:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:9:6:22:20
20:exp:42:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:9:6:22:20
20:exp:42:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.2, MD5, short tag
depends_on:4:9:6:22
20:exp:42:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:9:6:22
20:exp:42:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:9:6:22
20:exp:42:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.2, MD5, short tag, EtM
depends_on:4:9:6:22:20
20:exp:42:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, AES-192-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:9:6:22:20
20:exp:42:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, AES-192-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:9:6:22:20
20:exp:42:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, AES-192-CBC, 1.1, SHA-384
depends_on:4:9:5:7:8
20:exp:42:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.1, SHA-384, EtM
depends_on:4:9:5:7:8:20
20:exp:42:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.1, SHA-384, short tag
depends_on:4:9:5:7:8
20:exp:42:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:9:5:7:8:20
20:exp:42:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.1, SHA-256
depends_on:4:9:5:13
20:exp:42:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.1, SHA-256, EtM
depends_on:4:9:5:13:20
20:exp:42:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.1, SHA-256, short tag
depends_on:4:9:5:13
20:exp:42:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:9:5:13:20
20:exp:42:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.1, SHA-1
depends_on:4:9:5:21
20:exp:42:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.1, SHA-1, EtM
depends_on:4:9:5:21:20
20:exp:42:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.1, SHA-1, short tag
depends_on:4:9:5:21
20:exp:42:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:9:5:21:20
20:exp:42:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.1, MD5
depends_on:4:9:5:22
20:exp:42:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.1, MD5, EtM
depends_on:4:9:5:22:20
20:exp:42:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.1, MD5, short tag
depends_on:4:9:5:22
20:exp:42:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.1, MD5, short tag, EtM
depends_on:4:9:5:22:20
20:exp:42:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, AES-192-CBC, 1.0, SHA-384
depends_on:4:9:3:7:8
20:exp:42:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, AES-192-CBC, 1.0, SHA-384, EtM
depends_on:4:9:3:7:8:20
20:exp:42:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, AES-192-CBC, 1.0, SHA-384, short tag
depends_on:4:9:3:7:8
20:exp:42:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, AES-192-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:9:3:7:8:20
20:exp:42:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, AES-192-CBC, 1.0, SHA-256
depends_on:4:9:3:13
20:exp:42:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, AES-192-CBC, 1.0, SHA-256, EtM
depends_on:4:9:3:13:20
20:exp:42:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, AES-192-CBC, 1.0, SHA-256, short tag
depends_on:4:9:3:13
20:exp:42:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, AES-192-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:9:3:13:20
20:exp:42:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, AES-192-CBC, 1.0, SHA-1
depends_on:4:9:3:21
20:exp:42:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, AES-192-CBC, 1.0, SHA-1, EtM
depends_on:4:9:3:21:20
20:exp:42:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, AES-192-CBC, 1.0, SHA-1, short tag
depends_on:4:9:3:21
20:exp:42:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, AES-192-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:9:3:21:20
20:exp:42:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, AES-192-CBC, 1.0, MD5
depends_on:4:9:3:22
20:exp:42:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, AES-192-CBC, 1.0, MD5, EtM
depends_on:4:9:3:22:20
20:exp:42:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, AES-192-CBC, 1.0, MD5, short tag
depends_on:4:9:3:22
20:exp:42:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, AES-192-CBC, 1.0, MD5, short tag, EtM
depends_on:4:9:3:22:20
20:exp:42:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, AES-192-CBC, SSL3, SHA-1
depends_on:4:9:0:21
20:exp:42:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, AES-192-CBC, SSL3, SHA-1, EtM
depends_on:4:9:0:21:20
20:exp:42:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, AES-192-CBC, SSL3, SHA-1, short tag
depends_on:4:9:0:21
20:exp:42:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, AES-192-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:9:0:21:20
20:exp:42:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, AES-192-CBC, SSL3, MD5
depends_on:4:9:0:22
20:exp:42:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, AES-192-CBC, SSL3, MD5, EtM
depends_on:4:9:0:22:20
20:exp:42:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, AES-192-CBC, SSL3, MD5, short tag
depends_on:4:9:0:22
20:exp:42:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, AES-192-CBC, SSL3, MD5, short tag, EtM
depends_on:4:9:0:22:20
20:exp:42:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, AES256-CBC, 1.2, SHA-384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8
20:exp:43:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, SHA-384, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
20:exp:43:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, SHA-384, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
20:exp:43:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.2, SHA-384, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8:20
20:exp:43:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, SHA-384, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
20:exp:43:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, SHA-384, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
20:exp:43:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.2, SHA-384, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8
20:exp:43:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, SHA-384, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
20:exp:43:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, SHA-384, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
20:exp:43:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.2, SHA-384, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8:20
20:exp:43:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
20:exp:43:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
20:exp:43:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.2, SHA-256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13
20:exp:43:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, SHA-256, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
20:exp:43:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, SHA-256, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
20:exp:43:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.2, SHA-256, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13:20
20:exp:43:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, SHA-256, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
20:exp:43:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, SHA-256, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
20:exp:43:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.2, SHA-256, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13
20:exp:43:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, SHA-256, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
20:exp:43:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, SHA-256, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
20:exp:43:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.2, SHA-256, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13:20
20:exp:43:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
20:exp:43:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
20:exp:43:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.2, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21
20:exp:43:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, SHA-1, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
20:exp:43:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, SHA-1, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
20:exp:43:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.2, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21:20
20:exp:43:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, SHA-1, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
20:exp:43:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, SHA-1, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
20:exp:43:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.2, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21
20:exp:43:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, SHA-1, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
20:exp:43:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, SHA-1, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
20:exp:43:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.2, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21:20
20:exp:43:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
20:exp:43:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
20:exp:43:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.2, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22
20:exp:43:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, MD5, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
20:exp:43:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, MD5, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
20:exp:43:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.2, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22:20
20:exp:43:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, MD5, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
20:exp:43:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, MD5, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
20:exp:43:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.2, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22
20:exp:43:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, MD5, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
20:exp:43:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, MD5, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
20:exp:43:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.2, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22:20
20:exp:43:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, AES256-CBC, 1.2, MD5, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
20:exp:43:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, AES256-CBC, 1.2, MD5, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
20:exp:43:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, AES256-CBC, 1.1, SHA-384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8
20:exp:43:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.1, SHA-384, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8:20
20:exp:43:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.1, SHA-384, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8
20:exp:43:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.1, SHA-384, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8:20
20:exp:43:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.1, SHA-256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13
20:exp:43:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.1, SHA-256, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13:20
20:exp:43:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.1, SHA-256, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13
20:exp:43:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.1, SHA-256, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13:20
20:exp:43:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.1, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21
20:exp:43:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.1, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21:20
20:exp:43:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.1, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21
20:exp:43:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.1, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21:20
20:exp:43:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.1, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22
20:exp:43:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.1, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22:20
20:exp:43:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.1, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22
20:exp:43:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.1, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22:20
20:exp:43:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, AES256-CBC, 1.0, SHA-384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8
20:exp:43:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, AES256-CBC, 1.0, SHA-384, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8:20
20:exp:43:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, AES256-CBC, 1.0, SHA-384, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8
20:exp:43:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, AES256-CBC, 1.0, SHA-384, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8:20
20:exp:43:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, AES256-CBC, 1.0, SHA-256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13
20:exp:43:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, AES256-CBC, 1.0, SHA-256, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13:20
20:exp:43:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, AES256-CBC, 1.0, SHA-256, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13
20:exp:43:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, AES256-CBC, 1.0, SHA-256, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13:20
20:exp:43:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, AES256-CBC, 1.0, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21
20:exp:43:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, AES256-CBC, 1.0, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21:20
20:exp:43:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, AES256-CBC, 1.0, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21
20:exp:43:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, AES256-CBC, 1.0, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21:20
20:exp:43:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, AES256-CBC, 1.0, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22
20:exp:43:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, AES256-CBC, 1.0, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22:20
20:exp:43:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, AES256-CBC, 1.0, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22
20:exp:43:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, AES256-CBC, 1.0, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22:20
20:exp:43:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, AES256-CBC, SSL3, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21
20:exp:43:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, AES256-CBC, SSL3, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21:20
20:exp:43:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, AES256-CBC, SSL3, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21
20:exp:43:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, AES256-CBC, SSL3, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21:20
20:exp:43:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, AES256-CBC, SSL3, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22
20:exp:43:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, AES256-CBC, SSL3, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22:20
20:exp:43:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, AES256-CBC, SSL3, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22
20:exp:43:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, AES256-CBC, SSL3, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22:20
20:exp:43:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-384
depends_on:4:23:6:7:8
20:exp:44:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:23:6:7:8
20:exp:44:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:23:6:7:8
20:exp:44:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-384, EtM
depends_on:4:23:6:7:8:20
20:exp:44:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:23:6:7:8:20
20:exp:44:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:23:6:7:8:20
20:exp:44:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-384, short tag
depends_on:4:23:6:7:8
20:exp:44:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:23:6:7:8
20:exp:44:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:23:6:7:8
20:exp:44:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:23:6:7:8:20
20:exp:44:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:23:6:7:8:20
20:exp:44:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:23:6:7:8:20
20:exp:44:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-256
depends_on:4:23:6:13
20:exp:44:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:23:6:13
20:exp:44:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:23:6:13
20:exp:44:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-256, EtM
depends_on:4:23:6:13:20
20:exp:44:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:23:6:13:20
20:exp:44:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:23:6:13:20
20:exp:44:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-256, short tag
depends_on:4:23:6:13
20:exp:44:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:23:6:13
20:exp:44:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:23:6:13
20:exp:44:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:23:6:13:20
20:exp:44:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:23:6:13:20
20:exp:44:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:23:6:13:20
20:exp:44:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-1
depends_on:4:23:6:21
20:exp:44:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:23:6:21
20:exp:44:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:23:6:21
20:exp:44:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-1, EtM
depends_on:4:23:6:21:20
20:exp:44:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:23:6:21:20
20:exp:44:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:23:6:21:20
20:exp:44:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-1, short tag
depends_on:4:23:6:21
20:exp:44:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:23:6:21
20:exp:44:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:23:6:21
20:exp:44:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:23:6:21:20
20:exp:44:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:23:6:21:20
20:exp:44:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:23:6:21:20
20:exp:44:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.2, MD5
depends_on:4:23:6:22
20:exp:44:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:23:6:22
20:exp:44:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:23:6:22
20:exp:44:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.2, MD5, EtM
depends_on:4:23:6:22:20
20:exp:44:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:23:6:22:20
20:exp:44:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:23:6:22:20
20:exp:44:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.2, MD5, short tag
depends_on:4:23:6:22
20:exp:44:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:23:6:22
20:exp:44:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:23:6:22
20:exp:44:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.2, MD5, short tag, EtM
depends_on:4:23:6:22:20
20:exp:44:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARIA-128-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:23:6:22:20
20:exp:44:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARIA-128-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:23:6:22:20
20:exp:44:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARIA-128-CBC, 1.1, SHA-384
depends_on:4:23:5:7:8
20:exp:44:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.1, SHA-384, EtM
depends_on:4:23:5:7:8:20
20:exp:44:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.1, SHA-384, short tag
depends_on:4:23:5:7:8
20:exp:44:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:23:5:7:8:20
20:exp:44:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.1, SHA-256
depends_on:4:23:5:13
20:exp:44:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.1, SHA-256, EtM
depends_on:4:23:5:13:20
20:exp:44:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.1, SHA-256, short tag
depends_on:4:23:5:13
20:exp:44:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:23:5:13:20
20:exp:44:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.1, SHA-1
depends_on:4:23:5:21
20:exp:44:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.1, SHA-1, EtM
depends_on:4:23:5:21:20
20:exp:44:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.1, SHA-1, short tag
depends_on:4:23:5:21
20:exp:44:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:23:5:21:20
20:exp:44:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.1, MD5
depends_on:4:23:5:22
20:exp:44:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.1, MD5, EtM
depends_on:4:23:5:22:20
20:exp:44:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.1, MD5, short tag
depends_on:4:23:5:22
20:exp:44:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.1, MD5, short tag, EtM
depends_on:4:23:5:22:20
20:exp:44:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, SHA-384
depends_on:4:23:3:7:8
20:exp:44:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, SHA-384, EtM
depends_on:4:23:3:7:8:20
20:exp:44:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, SHA-384, short tag
depends_on:4:23:3:7:8
20:exp:44:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:23:3:7:8:20
20:exp:44:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, SHA-256
depends_on:4:23:3:13
20:exp:44:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, SHA-256, EtM
depends_on:4:23:3:13:20
20:exp:44:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, SHA-256, short tag
depends_on:4:23:3:13
20:exp:44:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:23:3:13:20
20:exp:44:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, SHA-1
depends_on:4:23:3:21
20:exp:44:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, SHA-1, EtM
depends_on:4:23:3:21:20
20:exp:44:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, SHA-1, short tag
depends_on:4:23:3:21
20:exp:44:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:23:3:21:20
20:exp:44:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, MD5
depends_on:4:23:3:22
20:exp:44:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, MD5, EtM
depends_on:4:23:3:22:20
20:exp:44:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, MD5, short tag
depends_on:4:23:3:22
20:exp:44:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, 1.0, MD5, short tag, EtM
depends_on:4:23:3:22:20
20:exp:44:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARIA-128-CBC, SSL3, SHA-1
depends_on:4:23:0:21
20:exp:44:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, ARIA-128-CBC, SSL3, SHA-1, EtM
depends_on:4:23:0:21:20
20:exp:44:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, ARIA-128-CBC, SSL3, SHA-1, short tag
depends_on:4:23:0:21
20:exp:44:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, ARIA-128-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:23:0:21:20
20:exp:44:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, ARIA-128-CBC, SSL3, MD5
depends_on:4:23:0:22
20:exp:44:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, ARIA-128-CBC, SSL3, MD5, EtM
depends_on:4:23:0:22:20
20:exp:44:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, ARIA-128-CBC, SSL3, MD5, short tag
depends_on:4:23:0:22
20:exp:44:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, ARIA-128-CBC, SSL3, MD5, short tag, EtM
depends_on:4:23:0:22:20
20:exp:44:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-384
depends_on:4:23:6:7:8
20:exp:45:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:23:6:7:8
20:exp:45:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:23:6:7:8
20:exp:45:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-384, EtM
depends_on:4:23:6:7:8:20
20:exp:45:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:23:6:7:8:20
20:exp:45:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:23:6:7:8:20
20:exp:45:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-384, short tag
depends_on:4:23:6:7:8
20:exp:45:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:23:6:7:8
20:exp:45:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:23:6:7:8
20:exp:45:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:23:6:7:8:20
20:exp:45:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:23:6:7:8:20
20:exp:45:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:23:6:7:8:20
20:exp:45:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-256
depends_on:4:23:6:13
20:exp:45:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:23:6:13
20:exp:45:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:23:6:13
20:exp:45:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-256, EtM
depends_on:4:23:6:13:20
20:exp:45:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:23:6:13:20
20:exp:45:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:23:6:13:20
20:exp:45:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-256, short tag
depends_on:4:23:6:13
20:exp:45:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:23:6:13
20:exp:45:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:23:6:13
20:exp:45:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:23:6:13:20
20:exp:45:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:23:6:13:20
20:exp:45:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:23:6:13:20
20:exp:45:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-1
depends_on:4:23:6:21
20:exp:45:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:23:6:21
20:exp:45:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:23:6:21
20:exp:45:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-1, EtM
depends_on:4:23:6:21:20
20:exp:45:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:23:6:21:20
20:exp:45:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:23:6:21:20
20:exp:45:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-1, short tag
depends_on:4:23:6:21
20:exp:45:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:23:6:21
20:exp:45:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:23:6:21
20:exp:45:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:23:6:21:20
20:exp:45:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:23:6:21:20
20:exp:45:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:23:6:21:20
20:exp:45:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.2, MD5
depends_on:4:23:6:22
20:exp:45:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:23:6:22
20:exp:45:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:23:6:22
20:exp:45:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.2, MD5, EtM
depends_on:4:23:6:22:20
20:exp:45:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:23:6:22:20
20:exp:45:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:23:6:22:20
20:exp:45:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.2, MD5, short tag
depends_on:4:23:6:22
20:exp:45:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:23:6:22
20:exp:45:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:23:6:22
20:exp:45:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.2, MD5, short tag, EtM
depends_on:4:23:6:22:20
20:exp:45:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARIA-192-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:23:6:22:20
20:exp:45:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARIA-192-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:23:6:22:20
20:exp:45:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARIA-192-CBC, 1.1, SHA-384
depends_on:4:23:5:7:8
20:exp:45:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.1, SHA-384, EtM
depends_on:4:23:5:7:8:20
20:exp:45:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.1, SHA-384, short tag
depends_on:4:23:5:7:8
20:exp:45:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:23:5:7:8:20
20:exp:45:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.1, SHA-256
depends_on:4:23:5:13
20:exp:45:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.1, SHA-256, EtM
depends_on:4:23:5:13:20
20:exp:45:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.1, SHA-256, short tag
depends_on:4:23:5:13
20:exp:45:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:23:5:13:20
20:exp:45:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.1, SHA-1
depends_on:4:23:5:21
20:exp:45:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.1, SHA-1, EtM
depends_on:4:23:5:21:20
20:exp:45:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.1, SHA-1, short tag
depends_on:4:23:5:21
20:exp:45:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:23:5:21:20
20:exp:45:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.1, MD5
depends_on:4:23:5:22
20:exp:45:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.1, MD5, EtM
depends_on:4:23:5:22:20
20:exp:45:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.1, MD5, short tag
depends_on:4:23:5:22
20:exp:45:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.1, MD5, short tag, EtM
depends_on:4:23:5:22:20
20:exp:45:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, SHA-384
depends_on:4:23:3:7:8
20:exp:45:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, SHA-384, EtM
depends_on:4:23:3:7:8:20
20:exp:45:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, SHA-384, short tag
depends_on:4:23:3:7:8
20:exp:45:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:23:3:7:8:20
20:exp:45:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, SHA-256
depends_on:4:23:3:13
20:exp:45:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, SHA-256, EtM
depends_on:4:23:3:13:20
20:exp:45:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, SHA-256, short tag
depends_on:4:23:3:13
20:exp:45:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:23:3:13:20
20:exp:45:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, SHA-1
depends_on:4:23:3:21
20:exp:45:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, SHA-1, EtM
depends_on:4:23:3:21:20
20:exp:45:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, SHA-1, short tag
depends_on:4:23:3:21
20:exp:45:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:23:3:21:20
20:exp:45:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, MD5
depends_on:4:23:3:22
20:exp:45:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, MD5, EtM
depends_on:4:23:3:22:20
20:exp:45:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, MD5, short tag
depends_on:4:23:3:22
20:exp:45:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, 1.0, MD5, short tag, EtM
depends_on:4:23:3:22:20
20:exp:45:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARIA-192-CBC, SSL3, SHA-1
depends_on:4:23:0:21
20:exp:45:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, ARIA-192-CBC, SSL3, SHA-1, EtM
depends_on:4:23:0:21:20
20:exp:45:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, ARIA-192-CBC, SSL3, SHA-1, short tag
depends_on:4:23:0:21
20:exp:45:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, ARIA-192-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:23:0:21:20
20:exp:45:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, ARIA-192-CBC, SSL3, MD5
depends_on:4:23:0:22
20:exp:45:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, ARIA-192-CBC, SSL3, MD5, EtM
depends_on:4:23:0:22:20
20:exp:45:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, ARIA-192-CBC, SSL3, MD5, short tag
depends_on:4:23:0:22
20:exp:45:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, ARIA-192-CBC, SSL3, MD5, short tag, EtM
depends_on:4:23:0:22:20
20:exp:45:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-384
depends_on:4:23:6:7:8
20:exp:46:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:23:6:7:8
20:exp:46:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:23:6:7:8
20:exp:46:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-384, EtM
depends_on:4:23:6:7:8:20
20:exp:46:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:23:6:7:8:20
20:exp:46:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:23:6:7:8:20
20:exp:46:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-384, short tag
depends_on:4:23:6:7:8
20:exp:46:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:23:6:7:8
20:exp:46:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:23:6:7:8
20:exp:46:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:23:6:7:8:20
20:exp:46:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:23:6:7:8:20
20:exp:46:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:23:6:7:8:20
20:exp:46:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-256
depends_on:4:23:6:13
20:exp:46:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:23:6:13
20:exp:46:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:23:6:13
20:exp:46:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-256, EtM
depends_on:4:23:6:13:20
20:exp:46:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:23:6:13:20
20:exp:46:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:23:6:13:20
20:exp:46:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-256, short tag
depends_on:4:23:6:13
20:exp:46:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:23:6:13
20:exp:46:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:23:6:13
20:exp:46:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:23:6:13:20
20:exp:46:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:23:6:13:20
20:exp:46:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:23:6:13:20
20:exp:46:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-1
depends_on:4:23:6:21
20:exp:46:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:23:6:21
20:exp:46:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:23:6:21
20:exp:46:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-1, EtM
depends_on:4:23:6:21:20
20:exp:46:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:23:6:21:20
20:exp:46:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:23:6:21:20
20:exp:46:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-1, short tag
depends_on:4:23:6:21
20:exp:46:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:23:6:21
20:exp:46:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:23:6:21
20:exp:46:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:23:6:21:20
20:exp:46:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:23:6:21:20
20:exp:46:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:23:6:21:20
20:exp:46:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.2, MD5
depends_on:4:23:6:22
20:exp:46:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:23:6:22
20:exp:46:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:23:6:22
20:exp:46:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.2, MD5, EtM
depends_on:4:23:6:22:20
20:exp:46:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:23:6:22:20
20:exp:46:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:23:6:22:20
20:exp:46:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.2, MD5, short tag
depends_on:4:23:6:22
20:exp:46:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:23:6:22
20:exp:46:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:23:6:22
20:exp:46:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.2, MD5, short tag, EtM
depends_on:4:23:6:22:20
20:exp:46:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARIA-256-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:23:6:22:20
20:exp:46:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARIA-256-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:23:6:22:20
20:exp:46:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARIA-256-CBC, 1.1, SHA-384
depends_on:4:23:5:7:8
20:exp:46:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.1, SHA-384, EtM
depends_on:4:23:5:7:8:20
20:exp:46:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.1, SHA-384, short tag
depends_on:4:23:5:7:8
20:exp:46:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:23:5:7:8:20
20:exp:46:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.1, SHA-256
depends_on:4:23:5:13
20:exp:46:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.1, SHA-256, EtM
depends_on:4:23:5:13:20
20:exp:46:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.1, SHA-256, short tag
depends_on:4:23:5:13
20:exp:46:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:23:5:13:20
20:exp:46:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.1, SHA-1
depends_on:4:23:5:21
20:exp:46:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.1, SHA-1, EtM
depends_on:4:23:5:21:20
20:exp:46:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.1, SHA-1, short tag
depends_on:4:23:5:21
20:exp:46:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:23:5:21:20
20:exp:46:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.1, MD5
depends_on:4:23:5:22
20:exp:46:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.1, MD5, EtM
depends_on:4:23:5:22:20
20:exp:46:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.1, MD5, short tag
depends_on:4:23:5:22
20:exp:46:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.1, MD5, short tag, EtM
depends_on:4:23:5:22:20
20:exp:46:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, SHA-384
depends_on:4:23:3:7:8
20:exp:46:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, SHA-384, EtM
depends_on:4:23:3:7:8:20
20:exp:46:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, SHA-384, short tag
depends_on:4:23:3:7:8
20:exp:46:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:23:3:7:8:20
20:exp:46:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, SHA-256
depends_on:4:23:3:13
20:exp:46:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, SHA-256, EtM
depends_on:4:23:3:13:20
20:exp:46:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, SHA-256, short tag
depends_on:4:23:3:13
20:exp:46:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:23:3:13:20
20:exp:46:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, SHA-1
depends_on:4:23:3:21
20:exp:46:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, SHA-1, EtM
depends_on:4:23:3:21:20
20:exp:46:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, SHA-1, short tag
depends_on:4:23:3:21
20:exp:46:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:23:3:21:20
20:exp:46:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, MD5
depends_on:4:23:3:22
20:exp:46:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, MD5, EtM
depends_on:4:23:3:22:20
20:exp:46:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, MD5, short tag
depends_on:4:23:3:22
20:exp:46:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, 1.0, MD5, short tag, EtM
depends_on:4:23:3:22:20
20:exp:46:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARIA-256-CBC, SSL3, SHA-1
depends_on:4:23:0:21
20:exp:46:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, ARIA-256-CBC, SSL3, SHA-1, EtM
depends_on:4:23:0:21:20
20:exp:46:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, ARIA-256-CBC, SSL3, SHA-1, short tag
depends_on:4:23:0:21
20:exp:46:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, ARIA-256-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:23:0:21:20
20:exp:46:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, ARIA-256-CBC, SSL3, MD5
depends_on:4:23:0:22
20:exp:46:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, ARIA-256-CBC, SSL3, MD5, EtM
depends_on:4:23:0:22:20
20:exp:46:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, ARIA-256-CBC, SSL3, MD5, short tag
depends_on:4:23:0:22
20:exp:46:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, ARIA-256-CBC, SSL3, MD5, short tag, EtM
depends_on:4:23:0:22:20
20:exp:46:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-384
depends_on:4:16:6:7:8
20:exp:47:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:16:6:7:8
20:exp:47:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:16:6:7:8
20:exp:47:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-384, EtM
depends_on:4:16:6:7:8:20
20:exp:47:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:16:6:7:8:20
20:exp:47:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:16:6:7:8:20
20:exp:47:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-384, short tag
depends_on:4:16:6:7:8
20:exp:47:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:16:6:7:8
20:exp:47:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:16:6:7:8
20:exp:47:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:16:6:7:8:20
20:exp:47:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:16:6:7:8:20
20:exp:47:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:16:6:7:8:20
20:exp:47:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-256
depends_on:4:16:6:13
20:exp:47:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:16:6:13
20:exp:47:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:16:6:13
20:exp:47:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-256, EtM
depends_on:4:16:6:13:20
20:exp:47:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:16:6:13:20
20:exp:47:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:16:6:13:20
20:exp:47:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-256, short tag
depends_on:4:16:6:13
20:exp:47:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:16:6:13
20:exp:47:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:16:6:13
20:exp:47:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:16:6:13:20
20:exp:47:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:16:6:13:20
20:exp:47:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:16:6:13:20
20:exp:47:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-1
depends_on:4:16:6:21
20:exp:47:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:16:6:21
20:exp:47:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:16:6:21
20:exp:47:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-1, EtM
depends_on:4:16:6:21:20
20:exp:47:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:16:6:21:20
20:exp:47:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:16:6:21:20
20:exp:47:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-1, short tag
depends_on:4:16:6:21
20:exp:47:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:16:6:21
20:exp:47:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:16:6:21
20:exp:47:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:16:6:21:20
20:exp:47:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:16:6:21:20
20:exp:47:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:16:6:21:20
20:exp:47:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, MD5
depends_on:4:16:6:22
20:exp:47:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:16:6:22
20:exp:47:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:16:6:22
20:exp:47:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, MD5, EtM
depends_on:4:16:6:22:20
20:exp:47:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:16:6:22:20
20:exp:47:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:16:6:22:20
20:exp:47:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, MD5, short tag
depends_on:4:16:6:22
20:exp:47:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:16:6:22
20:exp:47:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:16:6:22
20:exp:47:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, MD5, short tag, EtM
depends_on:4:16:6:22:20
20:exp:47:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:16:6:22:20
20:exp:47:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:16:6:22:20
20:exp:47:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, SHA-384
depends_on:4:16:5:7:8
20:exp:47:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, SHA-384, EtM
depends_on:4:16:5:7:8:20
20:exp:47:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, SHA-384, short tag
depends_on:4:16:5:7:8
20:exp:47:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:16:5:7:8:20
20:exp:47:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, SHA-256
depends_on:4:16:5:13
20:exp:47:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, SHA-256, EtM
depends_on:4:16:5:13:20
20:exp:47:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, SHA-256, short tag
depends_on:4:16:5:13
20:exp:47:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:16:5:13:20
20:exp:47:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, SHA-1
depends_on:4:16:5:21
20:exp:47:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, SHA-1, EtM
depends_on:4:16:5:21:20
20:exp:47:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, SHA-1, short tag
depends_on:4:16:5:21
20:exp:47:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:16:5:21:20
20:exp:47:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, MD5
depends_on:4:16:5:22
20:exp:47:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, MD5, EtM
depends_on:4:16:5:22:20
20:exp:47:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, MD5, short tag
depends_on:4:16:5:22
20:exp:47:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.1, MD5, short tag, EtM
depends_on:4:16:5:22:20
20:exp:47:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, SHA-384
depends_on:4:16:3:7:8
20:exp:47:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, SHA-384, EtM
depends_on:4:16:3:7:8:20
20:exp:47:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, SHA-384, short tag
depends_on:4:16:3:7:8
20:exp:47:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:16:3:7:8:20
20:exp:47:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, SHA-256
depends_on:4:16:3:13
20:exp:47:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, SHA-256, EtM
depends_on:4:16:3:13:20
20:exp:47:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, SHA-256, short tag
depends_on:4:16:3:13
20:exp:47:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:16:3:13:20
20:exp:47:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, SHA-1
depends_on:4:16:3:21
20:exp:47:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, SHA-1, EtM
depends_on:4:16:3:21:20
20:exp:47:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, SHA-1, short tag
depends_on:4:16:3:21
20:exp:47:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:16:3:21:20
20:exp:47:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, MD5
depends_on:4:16:3:22
20:exp:47:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, MD5, EtM
depends_on:4:16:3:22:20
20:exp:47:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, MD5, short tag
depends_on:4:16:3:22
20:exp:47:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, 1.0, MD5, short tag, EtM
depends_on:4:16:3:22:20
20:exp:47:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-128-CBC, SSL3, SHA-1
depends_on:4:16:0:21
20:exp:47:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, CAMELLIA-128-CBC, SSL3, SHA-1, EtM
depends_on:4:16:0:21:20
20:exp:47:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, CAMELLIA-128-CBC, SSL3, SHA-1, short tag
depends_on:4:16:0:21
20:exp:47:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, CAMELLIA-128-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:16:0:21:20
20:exp:47:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, CAMELLIA-128-CBC, SSL3, MD5
depends_on:4:16:0:22
20:exp:47:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, CAMELLIA-128-CBC, SSL3, MD5, EtM
depends_on:4:16:0:22:20
20:exp:47:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, CAMELLIA-128-CBC, SSL3, MD5, short tag
depends_on:4:16:0:22
20:exp:47:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, CAMELLIA-128-CBC, SSL3, MD5, short tag, EtM
depends_on:4:16:0:22:20
20:exp:47:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-384
depends_on:4:16:6:7:8
20:exp:48:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:16:6:7:8
20:exp:48:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:16:6:7:8
20:exp:48:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-384, EtM
depends_on:4:16:6:7:8:20
20:exp:48:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:16:6:7:8:20
20:exp:48:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:16:6:7:8:20
20:exp:48:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-384, short tag
depends_on:4:16:6:7:8
20:exp:48:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:16:6:7:8
20:exp:48:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:16:6:7:8
20:exp:48:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:16:6:7:8:20
20:exp:48:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:16:6:7:8:20
20:exp:48:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:16:6:7:8:20
20:exp:48:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-256
depends_on:4:16:6:13
20:exp:48:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:16:6:13
20:exp:48:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:16:6:13
20:exp:48:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-256, EtM
depends_on:4:16:6:13:20
20:exp:48:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:16:6:13:20
20:exp:48:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:16:6:13:20
20:exp:48:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-256, short tag
depends_on:4:16:6:13
20:exp:48:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:16:6:13
20:exp:48:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:16:6:13
20:exp:48:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:16:6:13:20
20:exp:48:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:16:6:13:20
20:exp:48:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:16:6:13:20
20:exp:48:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-1
depends_on:4:16:6:21
20:exp:48:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:16:6:21
20:exp:48:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:16:6:21
20:exp:48:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-1, EtM
depends_on:4:16:6:21:20
20:exp:48:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:16:6:21:20
20:exp:48:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:16:6:21:20
20:exp:48:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-1, short tag
depends_on:4:16:6:21
20:exp:48:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:16:6:21
20:exp:48:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:16:6:21
20:exp:48:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:16:6:21:20
20:exp:48:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:16:6:21:20
20:exp:48:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:16:6:21:20
20:exp:48:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, MD5
depends_on:4:16:6:22
20:exp:48:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:16:6:22
20:exp:48:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:16:6:22
20:exp:48:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, MD5, EtM
depends_on:4:16:6:22:20
20:exp:48:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:16:6:22:20
20:exp:48:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:16:6:22:20
20:exp:48:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, MD5, short tag
depends_on:4:16:6:22
20:exp:48:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:16:6:22
20:exp:48:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:16:6:22
20:exp:48:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, MD5, short tag, EtM
depends_on:4:16:6:22:20
20:exp:48:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:16:6:22:20
20:exp:48:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:16:6:22:20
20:exp:48:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, SHA-384
depends_on:4:16:5:7:8
20:exp:48:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, SHA-384, EtM
depends_on:4:16:5:7:8:20
20:exp:48:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, SHA-384, short tag
depends_on:4:16:5:7:8
20:exp:48:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:16:5:7:8:20
20:exp:48:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, SHA-256
depends_on:4:16:5:13
20:exp:48:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, SHA-256, EtM
depends_on:4:16:5:13:20
20:exp:48:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, SHA-256, short tag
depends_on:4:16:5:13
20:exp:48:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:16:5:13:20
20:exp:48:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, SHA-1
depends_on:4:16:5:21
20:exp:48:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, SHA-1, EtM
depends_on:4:16:5:21:20
20:exp:48:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, SHA-1, short tag
depends_on:4:16:5:21
20:exp:48:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:16:5:21:20
20:exp:48:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, MD5
depends_on:4:16:5:22
20:exp:48:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, MD5, EtM
depends_on:4:16:5:22:20
20:exp:48:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, MD5, short tag
depends_on:4:16:5:22
20:exp:48:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.1, MD5, short tag, EtM
depends_on:4:16:5:22:20
20:exp:48:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, SHA-384
depends_on:4:16:3:7:8
20:exp:48:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, SHA-384, EtM
depends_on:4:16:3:7:8:20
20:exp:48:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, SHA-384, short tag
depends_on:4:16:3:7:8
20:exp:48:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:16:3:7:8:20
20:exp:48:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, SHA-256
depends_on:4:16:3:13
20:exp:48:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, SHA-256, EtM
depends_on:4:16:3:13:20
20:exp:48:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, SHA-256, short tag
depends_on:4:16:3:13
20:exp:48:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:16:3:13:20
20:exp:48:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, SHA-1
depends_on:4:16:3:21
20:exp:48:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, SHA-1, EtM
depends_on:4:16:3:21:20
20:exp:48:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, SHA-1, short tag
depends_on:4:16:3:21
20:exp:48:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:16:3:21:20
20:exp:48:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, MD5
depends_on:4:16:3:22
20:exp:48:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, MD5, EtM
depends_on:4:16:3:22:20
20:exp:48:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, MD5, short tag
depends_on:4:16:3:22
20:exp:48:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, 1.0, MD5, short tag, EtM
depends_on:4:16:3:22:20
20:exp:48:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-192-CBC, SSL3, SHA-1
depends_on:4:16:0:21
20:exp:48:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, CAMELLIA-192-CBC, SSL3, SHA-1, EtM
depends_on:4:16:0:21:20
20:exp:48:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, CAMELLIA-192-CBC, SSL3, SHA-1, short tag
depends_on:4:16:0:21
20:exp:48:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, CAMELLIA-192-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:16:0:21:20
20:exp:48:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, CAMELLIA-192-CBC, SSL3, MD5
depends_on:4:16:0:22
20:exp:48:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, CAMELLIA-192-CBC, SSL3, MD5, EtM
depends_on:4:16:0:22:20
20:exp:48:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, CAMELLIA-192-CBC, SSL3, MD5, short tag
depends_on:4:16:0:22
20:exp:48:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, CAMELLIA-192-CBC, SSL3, MD5, short tag, EtM
depends_on:4:16:0:22:20
20:exp:48:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-384
depends_on:4:16:6:7:8
20:exp:49:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:16:6:7:8
20:exp:49:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:16:6:7:8
20:exp:49:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-384, EtM
depends_on:4:16:6:7:8:20
20:exp:49:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:16:6:7:8:20
20:exp:49:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:16:6:7:8:20
20:exp:49:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-384, short tag
depends_on:4:16:6:7:8
20:exp:49:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:16:6:7:8
20:exp:49:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:16:6:7:8
20:exp:49:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:16:6:7:8:20
20:exp:49:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:16:6:7:8:20
20:exp:49:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:16:6:7:8:20
20:exp:49:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-256
depends_on:4:16:6:13
20:exp:49:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:16:6:13
20:exp:49:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:16:6:13
20:exp:49:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-256, EtM
depends_on:4:16:6:13:20
20:exp:49:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:16:6:13:20
20:exp:49:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:16:6:13:20
20:exp:49:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-256, short tag
depends_on:4:16:6:13
20:exp:49:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:16:6:13
20:exp:49:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:16:6:13
20:exp:49:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:16:6:13:20
20:exp:49:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:16:6:13:20
20:exp:49:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:16:6:13:20
20:exp:49:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-1
depends_on:4:16:6:21
20:exp:49:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:16:6:21
20:exp:49:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:16:6:21
20:exp:49:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-1, EtM
depends_on:4:16:6:21:20
20:exp:49:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:16:6:21:20
20:exp:49:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:16:6:21:20
20:exp:49:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-1, short tag
depends_on:4:16:6:21
20:exp:49:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:16:6:21
20:exp:49:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:16:6:21
20:exp:49:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:16:6:21:20
20:exp:49:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:16:6:21:20
20:exp:49:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:16:6:21:20
20:exp:49:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, MD5
depends_on:4:16:6:22
20:exp:49:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:16:6:22
20:exp:49:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:16:6:22
20:exp:49:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, MD5, EtM
depends_on:4:16:6:22:20
20:exp:49:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:16:6:22:20
20:exp:49:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:16:6:22:20
20:exp:49:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, MD5, short tag
depends_on:4:16:6:22
20:exp:49:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:16:6:22
20:exp:49:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:16:6:22
20:exp:49:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, MD5, short tag, EtM
depends_on:4:16:6:22:20
20:exp:49:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:16:6:22:20
20:exp:49:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:16:6:22:20
20:exp:49:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, SHA-384
depends_on:4:16:5:7:8
20:exp:49:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, SHA-384, EtM
depends_on:4:16:5:7:8:20
20:exp:49:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, SHA-384, short tag
depends_on:4:16:5:7:8
20:exp:49:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:16:5:7:8:20
20:exp:49:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, SHA-256
depends_on:4:16:5:13
20:exp:49:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, SHA-256, EtM
depends_on:4:16:5:13:20
20:exp:49:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, SHA-256, short tag
depends_on:4:16:5:13
20:exp:49:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:16:5:13:20
20:exp:49:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, SHA-1
depends_on:4:16:5:21
20:exp:49:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, SHA-1, EtM
depends_on:4:16:5:21:20
20:exp:49:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, SHA-1, short tag
depends_on:4:16:5:21
20:exp:49:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:16:5:21:20
20:exp:49:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, MD5
depends_on:4:16:5:22
20:exp:49:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, MD5, EtM
depends_on:4:16:5:22:20
20:exp:49:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, MD5, short tag
depends_on:4:16:5:22
20:exp:49:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.1, MD5, short tag, EtM
depends_on:4:16:5:22:20
20:exp:49:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, SHA-384
depends_on:4:16:3:7:8
20:exp:49:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, SHA-384, EtM
depends_on:4:16:3:7:8:20
20:exp:49:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, SHA-384, short tag
depends_on:4:16:3:7:8
20:exp:49:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:16:3:7:8:20
20:exp:49:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, SHA-256
depends_on:4:16:3:13
20:exp:49:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, SHA-256, EtM
depends_on:4:16:3:13:20
20:exp:49:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, SHA-256, short tag
depends_on:4:16:3:13
20:exp:49:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:16:3:13:20
20:exp:49:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, SHA-1
depends_on:4:16:3:21
20:exp:49:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, SHA-1, EtM
depends_on:4:16:3:21:20
20:exp:49:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, SHA-1, short tag
depends_on:4:16:3:21
20:exp:49:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:16:3:21:20
20:exp:49:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, MD5
depends_on:4:16:3:22
20:exp:49:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, MD5, EtM
depends_on:4:16:3:22:20
20:exp:49:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, MD5, short tag
depends_on:4:16:3:22
20:exp:49:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, 1.0, MD5, short tag, EtM
depends_on:4:16:3:22:20
20:exp:49:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, CAMELLIA-256-CBC, SSL3, SHA-1
depends_on:4:16:0:21
20:exp:49:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, CAMELLIA-256-CBC, SSL3, SHA-1, EtM
depends_on:4:16:0:21:20
20:exp:49:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, CAMELLIA-256-CBC, SSL3, SHA-1, short tag
depends_on:4:16:0:21
20:exp:49:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, CAMELLIA-256-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:16:0:21:20
20:exp:49:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, CAMELLIA-256-CBC, SSL3, MD5
depends_on:4:16:0:22
20:exp:49:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, CAMELLIA-256-CBC, SSL3, MD5, EtM
depends_on:4:16:0:22:20
20:exp:49:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, CAMELLIA-256-CBC, SSL3, MD5, short tag
depends_on:4:16:0:22
20:exp:49:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, CAMELLIA-256-CBC, SSL3, MD5, short tag, EtM
depends_on:4:16:0:22:20
20:exp:49:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-384
depends_on:4:24:6:7:8
20:exp:50:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:24:6:7:8
20:exp:50:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:24:6:7:8
20:exp:50:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-384, EtM
depends_on:4:24:6:7:8:20
20:exp:50:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:24:6:7:8:20
20:exp:50:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:24:6:7:8:20
20:exp:50:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-384, short tag
depends_on:4:24:6:7:8
20:exp:50:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:24:6:7:8
20:exp:50:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:24:6:7:8
20:exp:50:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:24:6:7:8:20
20:exp:50:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:24:6:7:8:20
20:exp:50:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:24:6:7:8:20
20:exp:50:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-256
depends_on:4:24:6:13
20:exp:50:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:24:6:13
20:exp:50:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:24:6:13
20:exp:50:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-256, EtM
depends_on:4:24:6:13:20
20:exp:50:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:24:6:13:20
20:exp:50:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:24:6:13:20
20:exp:50:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-256, short tag
depends_on:4:24:6:13
20:exp:50:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:24:6:13
20:exp:50:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:24:6:13
20:exp:50:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:24:6:13:20
20:exp:50:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:24:6:13:20
20:exp:50:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:24:6:13:20
20:exp:50:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-1
depends_on:4:24:6:21
20:exp:50:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:24:6:21
20:exp:50:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:24:6:21
20:exp:50:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-1, EtM
depends_on:4:24:6:21:20
20:exp:50:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:24:6:21:20
20:exp:50:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:24:6:21:20
20:exp:50:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-1, short tag
depends_on:4:24:6:21
20:exp:50:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:24:6:21
20:exp:50:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:24:6:21
20:exp:50:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:24:6:21:20
20:exp:50:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:24:6:21:20
20:exp:50:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:24:6:21:20
20:exp:50:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.2, MD5
depends_on:4:24:6:22
20:exp:50:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:24:6:22
20:exp:50:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:24:6:22
20:exp:50:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.2, MD5, EtM
depends_on:4:24:6:22:20
20:exp:50:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:24:6:22:20
20:exp:50:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:24:6:22:20
20:exp:50:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.2, MD5, short tag
depends_on:4:24:6:22
20:exp:50:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:24:6:22
20:exp:50:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:24:6:22
20:exp:50:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.2, MD5, short tag, EtM
depends_on:4:24:6:22:20
20:exp:50:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:24:6:22:20
20:exp:50:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, BLOWFISH-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:24:6:22:20
20:exp:50:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, BLOWFISH-CBC, 1.1, SHA-384
depends_on:4:24:5:7:8
20:exp:50:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.1, SHA-384, EtM
depends_on:4:24:5:7:8:20
20:exp:50:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.1, SHA-384, short tag
depends_on:4:24:5:7:8
20:exp:50:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:24:5:7:8:20
20:exp:50:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.1, SHA-256
depends_on:4:24:5:13
20:exp:50:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.1, SHA-256, EtM
depends_on:4:24:5:13:20
20:exp:50:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.1, SHA-256, short tag
depends_on:4:24:5:13
20:exp:50:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:24:5:13:20
20:exp:50:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.1, SHA-1
depends_on:4:24:5:21
20:exp:50:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.1, SHA-1, EtM
depends_on:4:24:5:21:20
20:exp:50:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.1, SHA-1, short tag
depends_on:4:24:5:21
20:exp:50:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:24:5:21:20
20:exp:50:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.1, MD5
depends_on:4:24:5:22
20:exp:50:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.1, MD5, EtM
depends_on:4:24:5:22:20
20:exp:50:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.1, MD5, short tag
depends_on:4:24:5:22
20:exp:50:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.1, MD5, short tag, EtM
depends_on:4:24:5:22:20
20:exp:50:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, SHA-384
depends_on:4:24:3:7:8
20:exp:50:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, SHA-384, EtM
depends_on:4:24:3:7:8:20
20:exp:50:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, SHA-384, short tag
depends_on:4:24:3:7:8
20:exp:50:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:24:3:7:8:20
20:exp:50:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, SHA-256
depends_on:4:24:3:13
20:exp:50:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, SHA-256, EtM
depends_on:4:24:3:13:20
20:exp:50:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, SHA-256, short tag
depends_on:4:24:3:13
20:exp:50:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:24:3:13:20
20:exp:50:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, SHA-1
depends_on:4:24:3:21
20:exp:50:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, SHA-1, EtM
depends_on:4:24:3:21:20
20:exp:50:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, SHA-1, short tag
depends_on:4:24:3:21
20:exp:50:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:24:3:21:20
20:exp:50:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, MD5
depends_on:4:24:3:22
20:exp:50:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, MD5, EtM
depends_on:4:24:3:22:20
20:exp:50:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, MD5, short tag
depends_on:4:24:3:22
20:exp:50:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, 1.0, MD5, short tag, EtM
depends_on:4:24:3:22:20
20:exp:50:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, BLOWFISH-CBC, SSL3, SHA-1
depends_on:4:24:0:21
20:exp:50:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, BLOWFISH-CBC, SSL3, SHA-1, EtM
depends_on:4:24:0:21:20
20:exp:50:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, BLOWFISH-CBC, SSL3, SHA-1, short tag
depends_on:4:24:0:21
20:exp:50:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, BLOWFISH-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:24:0:21:20
20:exp:50:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, BLOWFISH-CBC, SSL3, MD5
depends_on:4:24:0:22
20:exp:50:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, BLOWFISH-CBC, SSL3, MD5, EtM
depends_on:4:24:0:22:20
20:exp:50:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, BLOWFISH-CBC, SSL3, MD5, short tag
depends_on:4:24:0:22
20:exp:50:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, BLOWFISH-CBC, SSL3, MD5, short tag, EtM
depends_on:4:24:0:22:20
20:exp:50:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, AES128-GCM, 1.2
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:10
20:exp:51:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES128-GCM, 1.3
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:25:10
20:exp:51:exp:41:int:0:int:0:exp:52:int:0:int:0
Record crypt, AES128-GCM, 1.2, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
20:exp:51:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES128-GCM, 1.2, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
20:exp:51:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES128-GCM, 1.2, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:10
20:exp:51:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES128-GCM, 1.2, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
20:exp:51:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES128-GCM, 1.2, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
20:exp:51:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES-192-GCM, 1.2
depends_on:9:6:10
20:exp:53:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES-192-GCM, 1.3
depends_on:9:25:10
20:exp:53:exp:41:int:0:int:0:exp:52:int:0:int:0
Record crypt, AES-192-GCM, 1.2, CID 4+4
depends_on:19:9:6:10
20:exp:53:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES-192-GCM, 1.2, CID 4+0
depends_on:19:9:6:10
20:exp:53:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES-192-GCM, 1.2, short tag
depends_on:9:6:10
20:exp:53:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES-192-GCM, 1.2, short tag, CID 4+4
depends_on:19:9:6:10
20:exp:53:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES-192-GCM, 1.2, short tag, CID 4+0
depends_on:19:9:6:10
20:exp:53:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES256-GCM, 1.2
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:10
20:exp:54:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES256-GCM, 1.3
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:25:10
20:exp:54:exp:41:int:0:int:0:exp:52:int:0:int:0
Record crypt, AES256-GCM, 1.2, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
20:exp:54:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES256-GCM, 1.2, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
20:exp:54:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES256-GCM, 1.2, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:10
20:exp:54:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES256-GCM, 1.2, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
20:exp:54:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES256-GCM, 1.2, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
20:exp:54:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-GCM, 1.2
depends_on:16:6:10
20:exp:55:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-GCM, 1.2, CID 4+4
depends_on:19:16:6:10
20:exp:55:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-GCM, 1.2, CID 4+0
depends_on:19:16:6:10
20:exp:55:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-GCM, 1.2, short tag
depends_on:16:6:10
20:exp:55:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-GCM, 1.2, short tag, CID 4+4
depends_on:19:16:6:10
20:exp:55:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-GCM, 1.2, short tag, CID 4+0
depends_on:19:16:6:10
20:exp:55:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-GCM, 1.2
depends_on:16:6:10
20:exp:56:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-GCM, 1.2, CID 4+4
depends_on:19:16:6:10
20:exp:56:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-GCM, 1.2, CID 4+0
depends_on:19:16:6:10
20:exp:56:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-GCM, 1.2, short tag
depends_on:16:6:10
20:exp:56:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-GCM, 1.2, short tag, CID 4+4
depends_on:19:16:6:10
20:exp:56:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-GCM, 1.2, short tag, CID 4+0
depends_on:19:16:6:10
20:exp:56:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-GCM, 1.2
depends_on:16:6:10
20:exp:57:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-GCM, 1.2, CID 4+4
depends_on:19:16:6:10
20:exp:57:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-GCM, 1.2, CID 4+0
depends_on:19:16:6:10
20:exp:57:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-GCM, 1.2, short tag
depends_on:16:6:10
20:exp:57:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-GCM, 1.2, short tag, CID 4+4
depends_on:19:16:6:10
20:exp:57:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-GCM, 1.2, short tag, CID 4+0
depends_on:19:16:6:10
20:exp:57:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES128-CCM, 1.2
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:12
20:exp:58:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES128-CCM, 1.3
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:25:12
20:exp:58:exp:41:int:0:int:0:exp:52:int:0:int:0
Record crypt, AES128-CCM, 1.2, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
20:exp:58:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES128-CCM, 1.2, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
20:exp:58:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES128-CCM, 1.2, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:12
20:exp:58:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES128-CCM, 1.2, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
20:exp:58:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES128-CCM, 1.2, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
20:exp:58:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES-192-CCM, 1.2
depends_on:9:6:12
20:exp:59:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES-192-CCM, 1.3
depends_on:9:25:12
20:exp:59:exp:41:int:0:int:0:exp:52:int:0:int:0
Record crypt, AES-192-CCM, 1.2, CID 4+4
depends_on:19:9:6:12
20:exp:59:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES-192-CCM, 1.2, CID 4+0
depends_on:19:9:6:12
20:exp:59:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES-192-CCM, 1.2, short tag
depends_on:9:6:12
20:exp:59:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES-192-CCM, 1.2, short tag, CID 4+4
depends_on:19:9:6:12
20:exp:59:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES-192-CCM, 1.2, short tag, CID 4+0
depends_on:19:9:6:12
20:exp:59:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, AES256-CCM, 1.2
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:12
20:exp:60:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, AES256-CCM, 1.3
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:25:12
20:exp:60:exp:41:int:0:int:0:exp:52:int:0:int:0
Record crypt, AES256-CCM, 1.2, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
20:exp:60:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, AES256-CCM, 1.2, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
20:exp:60:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, AES256-CCM, 1.2, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:12
20:exp:60:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, AES256-CCM, 1.2, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
20:exp:60:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, AES256-CCM, 1.2, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
20:exp:60:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CCM, 1.2
depends_on:16:6:12
20:exp:61:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CCM, 1.2, CID 4+4
depends_on:19:16:6:12
20:exp:61:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CCM, 1.2, CID 4+0
depends_on:19:16:6:12
20:exp:61:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-128-CCM, 1.2, short tag
depends_on:16:6:12
20:exp:61:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-128-CCM, 1.2, short tag, CID 4+4
depends_on:19:16:6:12
20:exp:61:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-128-CCM, 1.2, short tag, CID 4+0
depends_on:19:16:6:12
20:exp:61:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CCM, 1.2
depends_on:16:6:12
20:exp:62:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CCM, 1.2, CID 4+4
depends_on:19:16:6:12
20:exp:62:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CCM, 1.2, CID 4+0
depends_on:19:16:6:12
20:exp:62:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-192-CCM, 1.2, short tag
depends_on:16:6:12
20:exp:62:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-192-CCM, 1.2, short tag, CID 4+4
depends_on:19:16:6:12
20:exp:62:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-192-CCM, 1.2, short tag, CID 4+0
depends_on:19:16:6:12
20:exp:62:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CCM, 1.2
depends_on:16:6:12
20:exp:63:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CCM, 1.2, CID 4+4
depends_on:19:16:6:12
20:exp:63:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CCM, 1.2, CID 4+0
depends_on:19:16:6:12
20:exp:63:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, CAMELLIA-256-CCM, 1.2, short tag
depends_on:16:6:12
20:exp:63:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, CAMELLIA-256-CCM, 1.2, short tag, CID 4+4
depends_on:19:16:6:12
20:exp:63:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, CAMELLIA-256-CCM, 1.2, short tag, CID 4+0
depends_on:19:16:6:12
20:exp:63:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, SHA-384
depends_on:26:6:7:8
20:exp:64:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, SHA-384, CID 4+4
depends_on:19:26:6:7:8
20:exp:64:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, SHA-384, CID 4+0
depends_on:19:26:6:7:8
20:exp:64:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, SHA-384, EtM
depends_on:26:6:7:8:20
20:exp:64:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:26:6:7:8:20
20:exp:64:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:26:6:7:8:20
20:exp:64:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, SHA-384, short tag
depends_on:26:6:7:8
20:exp:64:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:26:6:7:8
20:exp:64:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:26:6:7:8
20:exp:64:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, SHA-384, short tag, EtM
depends_on:26:6:7:8:20
20:exp:64:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:26:6:7:8:20
20:exp:64:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:26:6:7:8:20
20:exp:64:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, SHA-256
depends_on:26:6:13
20:exp:64:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, SHA-256, CID 4+4
depends_on:19:26:6:13
20:exp:64:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, SHA-256, CID 4+0
depends_on:19:26:6:13
20:exp:64:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, SHA-256, EtM
depends_on:26:6:13:20
20:exp:64:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:26:6:13:20
20:exp:64:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:26:6:13:20
20:exp:64:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, SHA-256, short tag
depends_on:26:6:13
20:exp:64:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:26:6:13
20:exp:64:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:26:6:13
20:exp:64:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, SHA-256, short tag, EtM
depends_on:26:6:13:20
20:exp:64:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:26:6:13:20
20:exp:64:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:26:6:13:20
20:exp:64:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, SHA-1
depends_on:26:6:21
20:exp:64:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, SHA-1, CID 4+4
depends_on:19:26:6:21
20:exp:64:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, SHA-1, CID 4+0
depends_on:19:26:6:21
20:exp:64:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, SHA-1, EtM
depends_on:26:6:21:20
20:exp:64:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:26:6:21:20
20:exp:64:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:26:6:21:20
20:exp:64:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, SHA-1, short tag
depends_on:26:6:21
20:exp:64:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:26:6:21
20:exp:64:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:26:6:21
20:exp:64:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, SHA-1, short tag, EtM
depends_on:26:6:21:20
20:exp:64:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:26:6:21:20
20:exp:64:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:26:6:21:20
20:exp:64:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, MD5
depends_on:26:6:22
20:exp:64:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, MD5, CID 4+4
depends_on:19:26:6:22
20:exp:64:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, MD5, CID 4+0
depends_on:19:26:6:22
20:exp:64:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, MD5, EtM
depends_on:26:6:22:20
20:exp:64:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, MD5, EtM, CID 4+4
depends_on:19:26:6:22:20
20:exp:64:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, MD5, EtM, CID 4+0
depends_on:19:26:6:22:20
20:exp:64:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, MD5, short tag
depends_on:26:6:22
20:exp:64:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, MD5, short tag, CID 4+4
depends_on:19:26:6:22
20:exp:64:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, MD5, short tag, CID 4+0
depends_on:19:26:6:22
20:exp:64:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.2, MD5, short tag, EtM
depends_on:26:6:22:20
20:exp:64:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, ARC4-128, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:26:6:22:20
20:exp:64:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, ARC4-128, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:26:6:22:20
20:exp:64:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, ARC4-128, 1.1, SHA-384
depends_on:26:5:7:8
20:exp:64:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.1, SHA-384, EtM
depends_on:26:5:7:8:20
20:exp:64:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.1, SHA-384, short tag
depends_on:26:5:7:8
20:exp:64:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.1, SHA-384, short tag, EtM
depends_on:26:5:7:8:20
20:exp:64:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.1, SHA-256
depends_on:26:5:13
20:exp:64:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.1, SHA-256, EtM
depends_on:26:5:13:20
20:exp:64:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.1, SHA-256, short tag
depends_on:26:5:13
20:exp:64:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.1, SHA-256, short tag, EtM
depends_on:26:5:13:20
20:exp:64:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.1, SHA-1
depends_on:26:5:21
20:exp:64:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.1, SHA-1, EtM
depends_on:26:5:21:20
20:exp:64:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.1, SHA-1, short tag
depends_on:26:5:21
20:exp:64:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.1, SHA-1, short tag, EtM
depends_on:26:5:21:20
20:exp:64:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.1, MD5
depends_on:26:5:22
20:exp:64:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.1, MD5, EtM
depends_on:26:5:22:20
20:exp:64:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.1, MD5, short tag
depends_on:26:5:22
20:exp:64:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.1, MD5, short tag, EtM
depends_on:26:5:22:20
20:exp:64:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, ARC4-128, 1.0, SHA-384
depends_on:26:3:7:8
20:exp:64:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARC4-128, 1.0, SHA-384, EtM
depends_on:26:3:7:8:20
20:exp:64:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARC4-128, 1.0, SHA-384, short tag
depends_on:26:3:7:8
20:exp:64:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARC4-128, 1.0, SHA-384, short tag, EtM
depends_on:26:3:7:8:20
20:exp:64:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARC4-128, 1.0, SHA-256
depends_on:26:3:13
20:exp:64:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARC4-128, 1.0, SHA-256, EtM
depends_on:26:3:13:20
20:exp:64:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARC4-128, 1.0, SHA-256, short tag
depends_on:26:3:13
20:exp:64:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARC4-128, 1.0, SHA-256, short tag, EtM
depends_on:26:3:13:20
20:exp:64:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARC4-128, 1.0, SHA-1
depends_on:26:3:21
20:exp:64:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARC4-128, 1.0, SHA-1, EtM
depends_on:26:3:21:20
20:exp:64:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARC4-128, 1.0, SHA-1, short tag
depends_on:26:3:21
20:exp:64:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARC4-128, 1.0, SHA-1, short tag, EtM
depends_on:26:3:21:20
20:exp:64:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARC4-128, 1.0, MD5
depends_on:26:3:22
20:exp:64:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, ARC4-128, 1.0, MD5, EtM
depends_on:26:3:22:20
20:exp:64:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, ARC4-128, 1.0, MD5, short tag
depends_on:26:3:22
20:exp:64:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, ARC4-128, 1.0, MD5, short tag, EtM
depends_on:26:3:22:20
20:exp:64:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, ARC4-128, SSL3, SHA-1
depends_on:26:0:21
20:exp:64:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, ARC4-128, SSL3, SHA-1, EtM
depends_on:26:0:21:20
20:exp:64:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, ARC4-128, SSL3, SHA-1, short tag
depends_on:26:0:21
20:exp:64:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, ARC4-128, SSL3, SHA-1, short tag, EtM
depends_on:26:0:21:20
20:exp:64:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, ARC4-128, SSL3, MD5
depends_on:26:0:22
20:exp:64:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, ARC4-128, SSL3, MD5, EtM
depends_on:26:0:22:20
20:exp:64:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, ARC4-128, SSL3, MD5, short tag
depends_on:26:0:22
20:exp:64:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, ARC4-128, SSL3, MD5, short tag, EtM
depends_on:26:0:22:20
20:exp:64:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, NULL cipher, 1.2, SHA-384
depends_on:27:6:7:8
20:exp:65:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.2, SHA-384, EtM
depends_on:27:6:7:8:20
20:exp:65:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.2, SHA-384, short tag
depends_on:27:6:7:8
20:exp:65:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.2, SHA-384, short tag, EtM
depends_on:27:6:7:8:20
20:exp:65:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.2, SHA-256
depends_on:27:6:13
20:exp:65:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.2, SHA-256, EtM
depends_on:27:6:13:20
20:exp:65:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.2, SHA-256, short tag
depends_on:27:6:13
20:exp:65:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.2, SHA-256, short tag, EtM
depends_on:27:6:13:20
20:exp:65:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.2, SHA-1
depends_on:27:6:21
20:exp:65:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.2, SHA-1, EtM
depends_on:27:6:21:20
20:exp:65:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.2, SHA-1, short tag
depends_on:27:6:21
20:exp:65:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.2, SHA-1, short tag, EtM
depends_on:27:6:21:20
20:exp:65:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.2, MD5
depends_on:27:6:22
20:exp:65:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.2, MD5, EtM
depends_on:27:6:22:20
20:exp:65:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.2, MD5, short tag
depends_on:27:6:22
20:exp:65:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.2, MD5, short tag, EtM
depends_on:27:6:22:20
20:exp:65:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, NULL cipher, 1.1, SHA-384
depends_on:27:5:7:8
20:exp:65:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.1, SHA-384, EtM
depends_on:27:5:7:8:20
20:exp:65:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.1, SHA-384, short tag
depends_on:27:5:7:8
20:exp:65:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.1, SHA-384, short tag, EtM
depends_on:27:5:7:8:20
20:exp:65:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.1, SHA-256
depends_on:27:5:13
20:exp:65:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.1, SHA-256, EtM
depends_on:27:5:13:20
20:exp:65:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.1, SHA-256, short tag
depends_on:27:5:13
20:exp:65:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.1, SHA-256, short tag, EtM
depends_on:27:5:13:20
20:exp:65:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.1, SHA-1
depends_on:27:5:21
20:exp:65:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.1, SHA-1, EtM
depends_on:27:5:21:20
20:exp:65:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.1, SHA-1, short tag
depends_on:27:5:21
20:exp:65:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.1, SHA-1, short tag, EtM
depends_on:27:5:21:20
20:exp:65:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.1, MD5
depends_on:27:5:22
20:exp:65:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.1, MD5, EtM
depends_on:27:5:22:20
20:exp:65:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.1, MD5, short tag
depends_on:27:5:22
20:exp:65:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.1, MD5, short tag, EtM
depends_on:27:5:22:20
20:exp:65:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, NULL cipher, 1.0, SHA-384
depends_on:27:3:7:8
20:exp:65:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, NULL cipher, 1.0, SHA-384, EtM
depends_on:27:3:7:8:20
20:exp:65:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, NULL cipher, 1.0, SHA-384, short tag
depends_on:27:3:7:8
20:exp:65:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, NULL cipher, 1.0, SHA-384, short tag, EtM
depends_on:27:3:7:8:20
20:exp:65:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, NULL cipher, 1.0, SHA-256
depends_on:27:3:13
20:exp:65:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, NULL cipher, 1.0, SHA-256, EtM
depends_on:27:3:13:20
20:exp:65:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, NULL cipher, 1.0, SHA-256, short tag
depends_on:27:3:13
20:exp:65:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, NULL cipher, 1.0, SHA-256, short tag, EtM
depends_on:27:3:13:20
20:exp:65:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, NULL cipher, 1.0, SHA-1
depends_on:27:3:21
20:exp:65:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, NULL cipher, 1.0, SHA-1, EtM
depends_on:27:3:21:20
20:exp:65:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, NULL cipher, 1.0, SHA-1, short tag
depends_on:27:3:21
20:exp:65:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, NULL cipher, 1.0, SHA-1, short tag, EtM
depends_on:27:3:21:20
20:exp:65:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, NULL cipher, 1.0, MD5
depends_on:27:3:22
20:exp:65:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, NULL cipher, 1.0, MD5, EtM
depends_on:27:3:22:20
20:exp:65:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, NULL cipher, 1.0, MD5, short tag
depends_on:27:3:22
20:exp:65:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, NULL cipher, 1.0, MD5, short tag, EtM
depends_on:27:3:22:20
20:exp:65:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, NULL cipher, SSL3, SHA-1
depends_on:27:0:21
20:exp:65:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, NULL cipher, SSL3, SHA-1, EtM
depends_on:27:0:21:20
20:exp:65:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, NULL cipher, SSL3, SHA-1, short tag
depends_on:27:0:21
20:exp:65:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, NULL cipher, SSL3, SHA-1, short tag, EtM
depends_on:27:0:21:20
20:exp:65:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, NULL cipher, SSL3, MD5
depends_on:27:0:22
20:exp:65:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, NULL cipher, SSL3, MD5, EtM
depends_on:27:0:22:20
20:exp:65:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, NULL cipher, SSL3, MD5, short tag
depends_on:27:0:22
20:exp:65:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, NULL cipher, SSL3, MD5, short tag, EtM
depends_on:27:0:22:20
20:exp:65:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, ChachaPoly
depends_on:28:6
20:exp:66:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, ChachaPoly, 1.3
depends_on:28:25
20:exp:66:exp:41:int:0:int:0:exp:52:int:0:int:0
Record crypt, little space, ChachaPoly
depends_on:28:6
21:exp:66:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ChachaPoly, 1.3
depends_on:28:25
21:exp:66:exp:41:int:0:int:0:exp:52:int:0:int:0
Record crypt, little space, ChachaPoly, CID 4+4
depends_on:19:28:6
21:exp:66:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, ChachaPoly, CID 4+0
depends_on:19:28:6
21:exp:66:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8
21:exp:37:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-384, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
21:exp:37:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, SHA-384, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
21:exp:37:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-384, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8:20
21:exp:37:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-384, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
21:exp:37:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, SHA-384, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
21:exp:37:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-384, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8
21:exp:37:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-384, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
21:exp:37:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, SHA-384, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
21:exp:37:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-384, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8:20
21:exp:37:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
21:exp:37:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
21:exp:37:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13
21:exp:37:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-256, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
21:exp:37:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, SHA-256, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
21:exp:37:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-256, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13:20
21:exp:37:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-256, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
21:exp:37:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, SHA-256, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
21:exp:37:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-256, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13
21:exp:37:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-256, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
21:exp:37:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, SHA-256, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
21:exp:37:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-256, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13:20
21:exp:37:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
21:exp:37:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
21:exp:37:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21
21:exp:37:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-1, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
21:exp:37:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, SHA-1, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
21:exp:37:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21:20
21:exp:37:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-1, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
21:exp:37:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, SHA-1, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
21:exp:37:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21
21:exp:37:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-1, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
21:exp:37:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, SHA-1, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
21:exp:37:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21:20
21:exp:37:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
21:exp:37:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
21:exp:37:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22
21:exp:37:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, MD5, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
21:exp:37:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, MD5, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
21:exp:37:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22:20
21:exp:37:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, MD5, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
21:exp:37:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, MD5, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
21:exp:37:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22
21:exp:37:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, MD5, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
21:exp:37:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, MD5, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
21:exp:37:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.2, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22:20
21:exp:37:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, AES128-CBC, 1.2, MD5, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
21:exp:37:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, AES128-CBC, 1.2, MD5, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
21:exp:37:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, AES128-CBC, 1.1, SHA-384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8
21:exp:37:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.1, SHA-384, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8:20
21:exp:37:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.1, SHA-384, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8
21:exp:37:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.1, SHA-384, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8:20
21:exp:37:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.1, SHA-256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13
21:exp:37:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.1, SHA-256, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13:20
21:exp:37:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.1, SHA-256, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13
21:exp:37:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.1, SHA-256, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13:20
21:exp:37:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.1, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21
21:exp:37:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.1, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21:20
21:exp:37:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.1, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21
21:exp:37:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.1, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21:20
21:exp:37:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.1, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22
21:exp:37:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.1, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22:20
21:exp:37:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.1, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22
21:exp:37:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.1, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22:20
21:exp:37:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, SHA-384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8
21:exp:37:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, SHA-384, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8:20
21:exp:37:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, SHA-384, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8
21:exp:37:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, SHA-384, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8:20
21:exp:37:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, SHA-256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13
21:exp:37:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, SHA-256, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13:20
21:exp:37:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, SHA-256, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13
21:exp:37:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, SHA-256, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13:20
21:exp:37:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21
21:exp:37:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21:20
21:exp:37:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21
21:exp:37:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21:20
21:exp:37:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22
21:exp:37:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22:20
21:exp:37:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22
21:exp:37:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, 1.0, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22:20
21:exp:37:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, AES128-CBC, SSL3, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21
21:exp:37:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, AES128-CBC, SSL3, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21:20
21:exp:37:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, AES128-CBC, SSL3, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21
21:exp:37:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, AES128-CBC, SSL3, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21:20
21:exp:37:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, AES128-CBC, SSL3, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22
21:exp:37:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, AES128-CBC, SSL3, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22:20
21:exp:37:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, AES128-CBC, SSL3, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22
21:exp:37:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, AES128-CBC, SSL3, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22:20
21:exp:37:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-384
depends_on:4:9:6:7:8
21:exp:42:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:9:6:7:8
21:exp:42:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:9:6:7:8
21:exp:42:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-384, EtM
depends_on:4:9:6:7:8:20
21:exp:42:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:9:6:7:8:20
21:exp:42:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:9:6:7:8:20
21:exp:42:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-384, short tag
depends_on:4:9:6:7:8
21:exp:42:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:9:6:7:8
21:exp:42:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:9:6:7:8
21:exp:42:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:9:6:7:8:20
21:exp:42:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:9:6:7:8:20
21:exp:42:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:9:6:7:8:20
21:exp:42:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-256
depends_on:4:9:6:13
21:exp:42:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:9:6:13
21:exp:42:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:9:6:13
21:exp:42:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-256, EtM
depends_on:4:9:6:13:20
21:exp:42:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:9:6:13:20
21:exp:42:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:9:6:13:20
21:exp:42:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-256, short tag
depends_on:4:9:6:13
21:exp:42:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:9:6:13
21:exp:42:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:9:6:13
21:exp:42:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:9:6:13:20
21:exp:42:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:9:6:13:20
21:exp:42:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:9:6:13:20
21:exp:42:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-1
depends_on:4:9:6:21
21:exp:42:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:9:6:21
21:exp:42:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:9:6:21
21:exp:42:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-1, EtM
depends_on:4:9:6:21:20
21:exp:42:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:9:6:21:20
21:exp:42:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:9:6:21:20
21:exp:42:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-1, short tag
depends_on:4:9:6:21
21:exp:42:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:9:6:21
21:exp:42:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:9:6:21
21:exp:42:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:9:6:21:20
21:exp:42:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:9:6:21:20
21:exp:42:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:9:6:21:20
21:exp:42:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.2, MD5
depends_on:4:9:6:22
21:exp:42:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:9:6:22
21:exp:42:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:9:6:22
21:exp:42:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.2, MD5, EtM
depends_on:4:9:6:22:20
21:exp:42:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:9:6:22:20
21:exp:42:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:9:6:22:20
21:exp:42:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.2, MD5, short tag
depends_on:4:9:6:22
21:exp:42:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:9:6:22
21:exp:42:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:9:6:22
21:exp:42:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.2, MD5, short tag, EtM
depends_on:4:9:6:22:20
21:exp:42:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:9:6:22:20
21:exp:42:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, AES-192-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:9:6:22:20
21:exp:42:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, AES-192-CBC, 1.1, SHA-384
depends_on:4:9:5:7:8
21:exp:42:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.1, SHA-384, EtM
depends_on:4:9:5:7:8:20
21:exp:42:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.1, SHA-384, short tag
depends_on:4:9:5:7:8
21:exp:42:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:9:5:7:8:20
21:exp:42:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.1, SHA-256
depends_on:4:9:5:13
21:exp:42:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.1, SHA-256, EtM
depends_on:4:9:5:13:20
21:exp:42:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.1, SHA-256, short tag
depends_on:4:9:5:13
21:exp:42:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:9:5:13:20
21:exp:42:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.1, SHA-1
depends_on:4:9:5:21
21:exp:42:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.1, SHA-1, EtM
depends_on:4:9:5:21:20
21:exp:42:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.1, SHA-1, short tag
depends_on:4:9:5:21
21:exp:42:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:9:5:21:20
21:exp:42:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.1, MD5
depends_on:4:9:5:22
21:exp:42:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.1, MD5, EtM
depends_on:4:9:5:22:20
21:exp:42:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.1, MD5, short tag
depends_on:4:9:5:22
21:exp:42:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.1, MD5, short tag, EtM
depends_on:4:9:5:22:20
21:exp:42:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, SHA-384
depends_on:4:9:3:7:8
21:exp:42:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, SHA-384, EtM
depends_on:4:9:3:7:8:20
21:exp:42:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, SHA-384, short tag
depends_on:4:9:3:7:8
21:exp:42:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:9:3:7:8:20
21:exp:42:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, SHA-256
depends_on:4:9:3:13
21:exp:42:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, SHA-256, EtM
depends_on:4:9:3:13:20
21:exp:42:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, SHA-256, short tag
depends_on:4:9:3:13
21:exp:42:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:9:3:13:20
21:exp:42:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, SHA-1
depends_on:4:9:3:21
21:exp:42:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, SHA-1, EtM
depends_on:4:9:3:21:20
21:exp:42:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, SHA-1, short tag
depends_on:4:9:3:21
21:exp:42:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:9:3:21:20
21:exp:42:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, MD5
depends_on:4:9:3:22
21:exp:42:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, MD5, EtM
depends_on:4:9:3:22:20
21:exp:42:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, MD5, short tag
depends_on:4:9:3:22
21:exp:42:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, 1.0, MD5, short tag, EtM
depends_on:4:9:3:22:20
21:exp:42:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, AES-192-CBC, SSL3, SHA-1
depends_on:4:9:0:21
21:exp:42:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, AES-192-CBC, SSL3, SHA-1, EtM
depends_on:4:9:0:21:20
21:exp:42:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, AES-192-CBC, SSL3, SHA-1, short tag
depends_on:4:9:0:21
21:exp:42:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, AES-192-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:9:0:21:20
21:exp:42:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, AES-192-CBC, SSL3, MD5
depends_on:4:9:0:22
21:exp:42:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, AES-192-CBC, SSL3, MD5, EtM
depends_on:4:9:0:22:20
21:exp:42:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, AES-192-CBC, SSL3, MD5, short tag
depends_on:4:9:0:22
21:exp:42:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, AES-192-CBC, SSL3, MD5, short tag, EtM
depends_on:4:9:0:22:20
21:exp:42:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8
21:exp:43:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-384, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
21:exp:43:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, SHA-384, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
21:exp:43:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-384, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8:20
21:exp:43:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-384, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
21:exp:43:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, SHA-384, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
21:exp:43:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-384, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8
21:exp:43:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-384, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
21:exp:43:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, SHA-384, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8
21:exp:43:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-384, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:7:8:20
21:exp:43:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
21:exp:43:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:7:8:20
21:exp:43:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13
21:exp:43:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-256, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
21:exp:43:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, SHA-256, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
21:exp:43:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-256, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13:20
21:exp:43:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-256, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
21:exp:43:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, SHA-256, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
21:exp:43:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-256, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13
21:exp:43:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-256, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
21:exp:43:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, SHA-256, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13
21:exp:43:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-256, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:13:20
21:exp:43:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
21:exp:43:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:13:20
21:exp:43:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21
21:exp:43:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-1, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
21:exp:43:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, SHA-1, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
21:exp:43:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21:20
21:exp:43:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-1, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
21:exp:43:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, SHA-1, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
21:exp:43:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21
21:exp:43:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-1, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
21:exp:43:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, SHA-1, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21
21:exp:43:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:21:20
21:exp:43:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
21:exp:43:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:21:20
21:exp:43:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.2, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22
21:exp:43:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, MD5, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
21:exp:43:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, MD5, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
21:exp:43:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.2, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22:20
21:exp:43:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, MD5, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
21:exp:43:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, MD5, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
21:exp:43:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.2, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22
21:exp:43:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, MD5, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
21:exp:43:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, MD5, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22
21:exp:43:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.2, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:6:22:20
21:exp:43:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, AES256-CBC, 1.2, MD5, short tag, EtM, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
21:exp:43:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, AES256-CBC, 1.2, MD5, short tag, EtM, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:4:9:6:22:20
21:exp:43:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, AES256-CBC, 1.1, SHA-384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8
21:exp:43:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.1, SHA-384, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8:20
21:exp:43:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.1, SHA-384, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8
21:exp:43:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.1, SHA-384, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:7:8:20
21:exp:43:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.1, SHA-256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13
21:exp:43:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.1, SHA-256, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13:20
21:exp:43:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.1, SHA-256, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13
21:exp:43:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.1, SHA-256, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:13:20
21:exp:43:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.1, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21
21:exp:43:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.1, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21:20
21:exp:43:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.1, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21
21:exp:43:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.1, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:21:20
21:exp:43:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.1, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22
21:exp:43:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.1, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22:20
21:exp:43:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.1, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22
21:exp:43:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.1, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:5:22:20
21:exp:43:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, SHA-384
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8
21:exp:43:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, SHA-384, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8:20
21:exp:43:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, SHA-384, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8
21:exp:43:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, SHA-384, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:7:8:20
21:exp:43:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, SHA-256
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13
21:exp:43:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, SHA-256, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13:20
21:exp:43:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, SHA-256, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13
21:exp:43:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, SHA-256, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:13:20
21:exp:43:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21
21:exp:43:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21:20
21:exp:43:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21
21:exp:43:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:21:20
21:exp:43:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22
21:exp:43:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22:20
21:exp:43:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22
21:exp:43:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, 1.0, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:3:22:20
21:exp:43:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, AES256-CBC, SSL3, SHA-1
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21
21:exp:43:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, AES256-CBC, SSL3, SHA-1, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21:20
21:exp:43:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, AES256-CBC, SSL3, SHA-1, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21
21:exp:43:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, AES256-CBC, SSL3, SHA-1, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:21:20
21:exp:43:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, AES256-CBC, SSL3, MD5
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22
21:exp:43:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, AES256-CBC, SSL3, MD5, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22:20
21:exp:43:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, AES256-CBC, SSL3, MD5, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22
21:exp:43:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, AES256-CBC, SSL3, MD5, short tag, EtM
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:4:9:0:22:20
21:exp:43:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-384
depends_on:4:23:6:7:8
21:exp:44:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:23:6:7:8
21:exp:44:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:23:6:7:8
21:exp:44:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-384, EtM
depends_on:4:23:6:7:8:20
21:exp:44:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:23:6:7:8:20
21:exp:44:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:23:6:7:8:20
21:exp:44:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-384, short tag
depends_on:4:23:6:7:8
21:exp:44:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:23:6:7:8
21:exp:44:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:23:6:7:8
21:exp:44:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:23:6:7:8:20
21:exp:44:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:23:6:7:8:20
21:exp:44:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:23:6:7:8:20
21:exp:44:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-256
depends_on:4:23:6:13
21:exp:44:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:23:6:13
21:exp:44:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:23:6:13
21:exp:44:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-256, EtM
depends_on:4:23:6:13:20
21:exp:44:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:23:6:13:20
21:exp:44:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:23:6:13:20
21:exp:44:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-256, short tag
depends_on:4:23:6:13
21:exp:44:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:23:6:13
21:exp:44:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:23:6:13
21:exp:44:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:23:6:13:20
21:exp:44:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:23:6:13:20
21:exp:44:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:23:6:13:20
21:exp:44:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-1
depends_on:4:23:6:21
21:exp:44:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:23:6:21
21:exp:44:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:23:6:21
21:exp:44:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-1, EtM
depends_on:4:23:6:21:20
21:exp:44:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:23:6:21:20
21:exp:44:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:23:6:21:20
21:exp:44:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-1, short tag
depends_on:4:23:6:21
21:exp:44:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:23:6:21
21:exp:44:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:23:6:21
21:exp:44:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:23:6:21:20
21:exp:44:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:23:6:21:20
21:exp:44:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:23:6:21:20
21:exp:44:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, MD5
depends_on:4:23:6:22
21:exp:44:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:23:6:22
21:exp:44:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:23:6:22
21:exp:44:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, MD5, EtM
depends_on:4:23:6:22:20
21:exp:44:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:23:6:22:20
21:exp:44:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:23:6:22:20
21:exp:44:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, MD5, short tag
depends_on:4:23:6:22
21:exp:44:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:23:6:22
21:exp:44:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:23:6:22
21:exp:44:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, MD5, short tag, EtM
depends_on:4:23:6:22:20
21:exp:44:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:23:6:22:20
21:exp:44:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-128-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:23:6:22:20
21:exp:44:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, SHA-384
depends_on:4:23:5:7:8
21:exp:44:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, SHA-384, EtM
depends_on:4:23:5:7:8:20
21:exp:44:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, SHA-384, short tag
depends_on:4:23:5:7:8
21:exp:44:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:23:5:7:8:20
21:exp:44:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, SHA-256
depends_on:4:23:5:13
21:exp:44:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, SHA-256, EtM
depends_on:4:23:5:13:20
21:exp:44:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, SHA-256, short tag
depends_on:4:23:5:13
21:exp:44:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:23:5:13:20
21:exp:44:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, SHA-1
depends_on:4:23:5:21
21:exp:44:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, SHA-1, EtM
depends_on:4:23:5:21:20
21:exp:44:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, SHA-1, short tag
depends_on:4:23:5:21
21:exp:44:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:23:5:21:20
21:exp:44:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, MD5
depends_on:4:23:5:22
21:exp:44:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, MD5, EtM
depends_on:4:23:5:22:20
21:exp:44:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, MD5, short tag
depends_on:4:23:5:22
21:exp:44:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.1, MD5, short tag, EtM
depends_on:4:23:5:22:20
21:exp:44:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, SHA-384
depends_on:4:23:3:7:8
21:exp:44:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, SHA-384, EtM
depends_on:4:23:3:7:8:20
21:exp:44:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, SHA-384, short tag
depends_on:4:23:3:7:8
21:exp:44:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:23:3:7:8:20
21:exp:44:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, SHA-256
depends_on:4:23:3:13
21:exp:44:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, SHA-256, EtM
depends_on:4:23:3:13:20
21:exp:44:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, SHA-256, short tag
depends_on:4:23:3:13
21:exp:44:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:23:3:13:20
21:exp:44:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, SHA-1
depends_on:4:23:3:21
21:exp:44:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, SHA-1, EtM
depends_on:4:23:3:21:20
21:exp:44:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, SHA-1, short tag
depends_on:4:23:3:21
21:exp:44:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:23:3:21:20
21:exp:44:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, MD5
depends_on:4:23:3:22
21:exp:44:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, MD5, EtM
depends_on:4:23:3:22:20
21:exp:44:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, MD5, short tag
depends_on:4:23:3:22
21:exp:44:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, 1.0, MD5, short tag, EtM
depends_on:4:23:3:22:20
21:exp:44:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-128-CBC, SSL3, SHA-1
depends_on:4:23:0:21
21:exp:44:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, ARIA-128-CBC, SSL3, SHA-1, EtM
depends_on:4:23:0:21:20
21:exp:44:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, ARIA-128-CBC, SSL3, SHA-1, short tag
depends_on:4:23:0:21
21:exp:44:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, ARIA-128-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:23:0:21:20
21:exp:44:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, ARIA-128-CBC, SSL3, MD5
depends_on:4:23:0:22
21:exp:44:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, ARIA-128-CBC, SSL3, MD5, EtM
depends_on:4:23:0:22:20
21:exp:44:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, ARIA-128-CBC, SSL3, MD5, short tag
depends_on:4:23:0:22
21:exp:44:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, ARIA-128-CBC, SSL3, MD5, short tag, EtM
depends_on:4:23:0:22:20
21:exp:44:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-384
depends_on:4:23:6:7:8
21:exp:45:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:23:6:7:8
21:exp:45:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:23:6:7:8
21:exp:45:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-384, EtM
depends_on:4:23:6:7:8:20
21:exp:45:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:23:6:7:8:20
21:exp:45:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:23:6:7:8:20
21:exp:45:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-384, short tag
depends_on:4:23:6:7:8
21:exp:45:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:23:6:7:8
21:exp:45:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:23:6:7:8
21:exp:45:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:23:6:7:8:20
21:exp:45:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:23:6:7:8:20
21:exp:45:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:23:6:7:8:20
21:exp:45:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-256
depends_on:4:23:6:13
21:exp:45:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:23:6:13
21:exp:45:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:23:6:13
21:exp:45:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-256, EtM
depends_on:4:23:6:13:20
21:exp:45:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:23:6:13:20
21:exp:45:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:23:6:13:20
21:exp:45:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-256, short tag
depends_on:4:23:6:13
21:exp:45:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:23:6:13
21:exp:45:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:23:6:13
21:exp:45:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:23:6:13:20
21:exp:45:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:23:6:13:20
21:exp:45:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:23:6:13:20
21:exp:45:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-1
depends_on:4:23:6:21
21:exp:45:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:23:6:21
21:exp:45:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:23:6:21
21:exp:45:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-1, EtM
depends_on:4:23:6:21:20
21:exp:45:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:23:6:21:20
21:exp:45:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:23:6:21:20
21:exp:45:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-1, short tag
depends_on:4:23:6:21
21:exp:45:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:23:6:21
21:exp:45:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:23:6:21
21:exp:45:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:23:6:21:20
21:exp:45:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:23:6:21:20
21:exp:45:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:23:6:21:20
21:exp:45:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, MD5
depends_on:4:23:6:22
21:exp:45:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:23:6:22
21:exp:45:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:23:6:22
21:exp:45:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, MD5, EtM
depends_on:4:23:6:22:20
21:exp:45:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:23:6:22:20
21:exp:45:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:23:6:22:20
21:exp:45:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, MD5, short tag
depends_on:4:23:6:22
21:exp:45:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:23:6:22
21:exp:45:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:23:6:22
21:exp:45:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, MD5, short tag, EtM
depends_on:4:23:6:22:20
21:exp:45:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:23:6:22:20
21:exp:45:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-192-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:23:6:22:20
21:exp:45:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, SHA-384
depends_on:4:23:5:7:8
21:exp:45:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, SHA-384, EtM
depends_on:4:23:5:7:8:20
21:exp:45:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, SHA-384, short tag
depends_on:4:23:5:7:8
21:exp:45:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:23:5:7:8:20
21:exp:45:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, SHA-256
depends_on:4:23:5:13
21:exp:45:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, SHA-256, EtM
depends_on:4:23:5:13:20
21:exp:45:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, SHA-256, short tag
depends_on:4:23:5:13
21:exp:45:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:23:5:13:20
21:exp:45:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, SHA-1
depends_on:4:23:5:21
21:exp:45:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, SHA-1, EtM
depends_on:4:23:5:21:20
21:exp:45:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, SHA-1, short tag
depends_on:4:23:5:21
21:exp:45:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:23:5:21:20
21:exp:45:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, MD5
depends_on:4:23:5:22
21:exp:45:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, MD5, EtM
depends_on:4:23:5:22:20
21:exp:45:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, MD5, short tag
depends_on:4:23:5:22
21:exp:45:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.1, MD5, short tag, EtM
depends_on:4:23:5:22:20
21:exp:45:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, SHA-384
depends_on:4:23:3:7:8
21:exp:45:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, SHA-384, EtM
depends_on:4:23:3:7:8:20
21:exp:45:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, SHA-384, short tag
depends_on:4:23:3:7:8
21:exp:45:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:23:3:7:8:20
21:exp:45:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, SHA-256
depends_on:4:23:3:13
21:exp:45:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, SHA-256, EtM
depends_on:4:23:3:13:20
21:exp:45:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, SHA-256, short tag
depends_on:4:23:3:13
21:exp:45:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:23:3:13:20
21:exp:45:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, SHA-1
depends_on:4:23:3:21
21:exp:45:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, SHA-1, EtM
depends_on:4:23:3:21:20
21:exp:45:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, SHA-1, short tag
depends_on:4:23:3:21
21:exp:45:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:23:3:21:20
21:exp:45:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, MD5
depends_on:4:23:3:22
21:exp:45:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, MD5, EtM
depends_on:4:23:3:22:20
21:exp:45:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, MD5, short tag
depends_on:4:23:3:22
21:exp:45:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, 1.0, MD5, short tag, EtM
depends_on:4:23:3:22:20
21:exp:45:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-192-CBC, SSL3, SHA-1
depends_on:4:23:0:21
21:exp:45:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, ARIA-192-CBC, SSL3, SHA-1, EtM
depends_on:4:23:0:21:20
21:exp:45:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, ARIA-192-CBC, SSL3, SHA-1, short tag
depends_on:4:23:0:21
21:exp:45:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, ARIA-192-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:23:0:21:20
21:exp:45:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, ARIA-192-CBC, SSL3, MD5
depends_on:4:23:0:22
21:exp:45:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, ARIA-192-CBC, SSL3, MD5, EtM
depends_on:4:23:0:22:20
21:exp:45:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, ARIA-192-CBC, SSL3, MD5, short tag
depends_on:4:23:0:22
21:exp:45:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, ARIA-192-CBC, SSL3, MD5, short tag, EtM
depends_on:4:23:0:22:20
21:exp:45:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-384
depends_on:4:23:6:7:8
21:exp:46:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:23:6:7:8
21:exp:46:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:23:6:7:8
21:exp:46:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-384, EtM
depends_on:4:23:6:7:8:20
21:exp:46:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:23:6:7:8:20
21:exp:46:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:23:6:7:8:20
21:exp:46:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-384, short tag
depends_on:4:23:6:7:8
21:exp:46:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:23:6:7:8
21:exp:46:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:23:6:7:8
21:exp:46:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:23:6:7:8:20
21:exp:46:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:23:6:7:8:20
21:exp:46:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:23:6:7:8:20
21:exp:46:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-256
depends_on:4:23:6:13
21:exp:46:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:23:6:13
21:exp:46:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:23:6:13
21:exp:46:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-256, EtM
depends_on:4:23:6:13:20
21:exp:46:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:23:6:13:20
21:exp:46:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:23:6:13:20
21:exp:46:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-256, short tag
depends_on:4:23:6:13
21:exp:46:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:23:6:13
21:exp:46:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:23:6:13
21:exp:46:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:23:6:13:20
21:exp:46:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:23:6:13:20
21:exp:46:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:23:6:13:20
21:exp:46:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-1
depends_on:4:23:6:21
21:exp:46:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:23:6:21
21:exp:46:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:23:6:21
21:exp:46:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-1, EtM
depends_on:4:23:6:21:20
21:exp:46:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:23:6:21:20
21:exp:46:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:23:6:21:20
21:exp:46:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-1, short tag
depends_on:4:23:6:21
21:exp:46:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:23:6:21
21:exp:46:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:23:6:21
21:exp:46:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:23:6:21:20
21:exp:46:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:23:6:21:20
21:exp:46:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:23:6:21:20
21:exp:46:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, MD5
depends_on:4:23:6:22
21:exp:46:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:23:6:22
21:exp:46:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:23:6:22
21:exp:46:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, MD5, EtM
depends_on:4:23:6:22:20
21:exp:46:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:23:6:22:20
21:exp:46:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:23:6:22:20
21:exp:46:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, MD5, short tag
depends_on:4:23:6:22
21:exp:46:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:23:6:22
21:exp:46:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:23:6:22
21:exp:46:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, MD5, short tag, EtM
depends_on:4:23:6:22:20
21:exp:46:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:23:6:22:20
21:exp:46:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, ARIA-256-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:23:6:22:20
21:exp:46:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, SHA-384
depends_on:4:23:5:7:8
21:exp:46:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, SHA-384, EtM
depends_on:4:23:5:7:8:20
21:exp:46:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, SHA-384, short tag
depends_on:4:23:5:7:8
21:exp:46:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:23:5:7:8:20
21:exp:46:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, SHA-256
depends_on:4:23:5:13
21:exp:46:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, SHA-256, EtM
depends_on:4:23:5:13:20
21:exp:46:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, SHA-256, short tag
depends_on:4:23:5:13
21:exp:46:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:23:5:13:20
21:exp:46:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, SHA-1
depends_on:4:23:5:21
21:exp:46:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, SHA-1, EtM
depends_on:4:23:5:21:20
21:exp:46:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, SHA-1, short tag
depends_on:4:23:5:21
21:exp:46:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:23:5:21:20
21:exp:46:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, MD5
depends_on:4:23:5:22
21:exp:46:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, MD5, EtM
depends_on:4:23:5:22:20
21:exp:46:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, MD5, short tag
depends_on:4:23:5:22
21:exp:46:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.1, MD5, short tag, EtM
depends_on:4:23:5:22:20
21:exp:46:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, SHA-384
depends_on:4:23:3:7:8
21:exp:46:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, SHA-384, EtM
depends_on:4:23:3:7:8:20
21:exp:46:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, SHA-384, short tag
depends_on:4:23:3:7:8
21:exp:46:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:23:3:7:8:20
21:exp:46:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, SHA-256
depends_on:4:23:3:13
21:exp:46:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, SHA-256, EtM
depends_on:4:23:3:13:20
21:exp:46:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, SHA-256, short tag
depends_on:4:23:3:13
21:exp:46:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:23:3:13:20
21:exp:46:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, SHA-1
depends_on:4:23:3:21
21:exp:46:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, SHA-1, EtM
depends_on:4:23:3:21:20
21:exp:46:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, SHA-1, short tag
depends_on:4:23:3:21
21:exp:46:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:23:3:21:20
21:exp:46:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, MD5
depends_on:4:23:3:22
21:exp:46:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, MD5, EtM
depends_on:4:23:3:22:20
21:exp:46:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, MD5, short tag
depends_on:4:23:3:22
21:exp:46:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, 1.0, MD5, short tag, EtM
depends_on:4:23:3:22:20
21:exp:46:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARIA-256-CBC, SSL3, SHA-1
depends_on:4:23:0:21
21:exp:46:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, ARIA-256-CBC, SSL3, SHA-1, EtM
depends_on:4:23:0:21:20
21:exp:46:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, ARIA-256-CBC, SSL3, SHA-1, short tag
depends_on:4:23:0:21
21:exp:46:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, ARIA-256-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:23:0:21:20
21:exp:46:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, ARIA-256-CBC, SSL3, MD5
depends_on:4:23:0:22
21:exp:46:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, ARIA-256-CBC, SSL3, MD5, EtM
depends_on:4:23:0:22:20
21:exp:46:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, ARIA-256-CBC, SSL3, MD5, short tag
depends_on:4:23:0:22
21:exp:46:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, ARIA-256-CBC, SSL3, MD5, short tag, EtM
depends_on:4:23:0:22:20
21:exp:46:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-384
depends_on:4:16:6:7:8
21:exp:47:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:16:6:7:8
21:exp:47:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:16:6:7:8
21:exp:47:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-384, EtM
depends_on:4:16:6:7:8:20
21:exp:47:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:16:6:7:8:20
21:exp:47:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:16:6:7:8:20
21:exp:47:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-384, short tag
depends_on:4:16:6:7:8
21:exp:47:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:16:6:7:8
21:exp:47:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:16:6:7:8
21:exp:47:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:16:6:7:8:20
21:exp:47:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:16:6:7:8:20
21:exp:47:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:16:6:7:8:20
21:exp:47:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-256
depends_on:4:16:6:13
21:exp:47:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:16:6:13
21:exp:47:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:16:6:13
21:exp:47:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-256, EtM
depends_on:4:16:6:13:20
21:exp:47:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:16:6:13:20
21:exp:47:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:16:6:13:20
21:exp:47:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-256, short tag
depends_on:4:16:6:13
21:exp:47:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:16:6:13
21:exp:47:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:16:6:13
21:exp:47:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:16:6:13:20
21:exp:47:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:16:6:13:20
21:exp:47:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:16:6:13:20
21:exp:47:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-1
depends_on:4:16:6:21
21:exp:47:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:16:6:21
21:exp:47:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:16:6:21
21:exp:47:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-1, EtM
depends_on:4:16:6:21:20
21:exp:47:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:16:6:21:20
21:exp:47:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:16:6:21:20
21:exp:47:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-1, short tag
depends_on:4:16:6:21
21:exp:47:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:16:6:21
21:exp:47:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:16:6:21
21:exp:47:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:16:6:21:20
21:exp:47:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:16:6:21:20
21:exp:47:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:16:6:21:20
21:exp:47:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, MD5
depends_on:4:16:6:22
21:exp:47:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:16:6:22
21:exp:47:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:16:6:22
21:exp:47:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, MD5, EtM
depends_on:4:16:6:22:20
21:exp:47:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:16:6:22:20
21:exp:47:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:16:6:22:20
21:exp:47:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, MD5, short tag
depends_on:4:16:6:22
21:exp:47:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:16:6:22
21:exp:47:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:16:6:22
21:exp:47:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, MD5, short tag, EtM
depends_on:4:16:6:22:20
21:exp:47:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:16:6:22:20
21:exp:47:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:16:6:22:20
21:exp:47:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, SHA-384
depends_on:4:16:5:7:8
21:exp:47:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, SHA-384, EtM
depends_on:4:16:5:7:8:20
21:exp:47:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, SHA-384, short tag
depends_on:4:16:5:7:8
21:exp:47:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:16:5:7:8:20
21:exp:47:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, SHA-256
depends_on:4:16:5:13
21:exp:47:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, SHA-256, EtM
depends_on:4:16:5:13:20
21:exp:47:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, SHA-256, short tag
depends_on:4:16:5:13
21:exp:47:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:16:5:13:20
21:exp:47:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, SHA-1
depends_on:4:16:5:21
21:exp:47:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, SHA-1, EtM
depends_on:4:16:5:21:20
21:exp:47:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, SHA-1, short tag
depends_on:4:16:5:21
21:exp:47:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:16:5:21:20
21:exp:47:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, MD5
depends_on:4:16:5:22
21:exp:47:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, MD5, EtM
depends_on:4:16:5:22:20
21:exp:47:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, MD5, short tag
depends_on:4:16:5:22
21:exp:47:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.1, MD5, short tag, EtM
depends_on:4:16:5:22:20
21:exp:47:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, SHA-384
depends_on:4:16:3:7:8
21:exp:47:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, SHA-384, EtM
depends_on:4:16:3:7:8:20
21:exp:47:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, SHA-384, short tag
depends_on:4:16:3:7:8
21:exp:47:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:16:3:7:8:20
21:exp:47:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, SHA-256
depends_on:4:16:3:13
21:exp:47:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, SHA-256, EtM
depends_on:4:16:3:13:20
21:exp:47:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, SHA-256, short tag
depends_on:4:16:3:13
21:exp:47:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:16:3:13:20
21:exp:47:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, SHA-1
depends_on:4:16:3:21
21:exp:47:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, SHA-1, EtM
depends_on:4:16:3:21:20
21:exp:47:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, SHA-1, short tag
depends_on:4:16:3:21
21:exp:47:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:16:3:21:20
21:exp:47:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, MD5
depends_on:4:16:3:22
21:exp:47:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, MD5, EtM
depends_on:4:16:3:22:20
21:exp:47:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, MD5, short tag
depends_on:4:16:3:22
21:exp:47:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, 1.0, MD5, short tag, EtM
depends_on:4:16:3:22:20
21:exp:47:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, SSL3, SHA-1
depends_on:4:16:0:21
21:exp:47:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, SSL3, SHA-1, EtM
depends_on:4:16:0:21:20
21:exp:47:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, SSL3, SHA-1, short tag
depends_on:4:16:0:21
21:exp:47:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:16:0:21:20
21:exp:47:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, SSL3, MD5
depends_on:4:16:0:22
21:exp:47:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, SSL3, MD5, EtM
depends_on:4:16:0:22:20
21:exp:47:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, SSL3, MD5, short tag
depends_on:4:16:0:22
21:exp:47:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-128-CBC, SSL3, MD5, short tag, EtM
depends_on:4:16:0:22:20
21:exp:47:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-384
depends_on:4:16:6:7:8
21:exp:48:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:16:6:7:8
21:exp:48:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:16:6:7:8
21:exp:48:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-384, EtM
depends_on:4:16:6:7:8:20
21:exp:48:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:16:6:7:8:20
21:exp:48:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:16:6:7:8:20
21:exp:48:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-384, short tag
depends_on:4:16:6:7:8
21:exp:48:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:16:6:7:8
21:exp:48:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:16:6:7:8
21:exp:48:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:16:6:7:8:20
21:exp:48:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:16:6:7:8:20
21:exp:48:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:16:6:7:8:20
21:exp:48:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-256
depends_on:4:16:6:13
21:exp:48:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:16:6:13
21:exp:48:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:16:6:13
21:exp:48:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-256, EtM
depends_on:4:16:6:13:20
21:exp:48:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:16:6:13:20
21:exp:48:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:16:6:13:20
21:exp:48:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-256, short tag
depends_on:4:16:6:13
21:exp:48:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:16:6:13
21:exp:48:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:16:6:13
21:exp:48:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:16:6:13:20
21:exp:48:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:16:6:13:20
21:exp:48:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:16:6:13:20
21:exp:48:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-1
depends_on:4:16:6:21
21:exp:48:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:16:6:21
21:exp:48:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:16:6:21
21:exp:48:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-1, EtM
depends_on:4:16:6:21:20
21:exp:48:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:16:6:21:20
21:exp:48:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:16:6:21:20
21:exp:48:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-1, short tag
depends_on:4:16:6:21
21:exp:48:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:16:6:21
21:exp:48:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:16:6:21
21:exp:48:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:16:6:21:20
21:exp:48:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:16:6:21:20
21:exp:48:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:16:6:21:20
21:exp:48:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, MD5
depends_on:4:16:6:22
21:exp:48:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:16:6:22
21:exp:48:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:16:6:22
21:exp:48:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, MD5, EtM
depends_on:4:16:6:22:20
21:exp:48:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:16:6:22:20
21:exp:48:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:16:6:22:20
21:exp:48:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, MD5, short tag
depends_on:4:16:6:22
21:exp:48:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:16:6:22
21:exp:48:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:16:6:22
21:exp:48:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, MD5, short tag, EtM
depends_on:4:16:6:22:20
21:exp:48:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:16:6:22:20
21:exp:48:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:16:6:22:20
21:exp:48:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, SHA-384
depends_on:4:16:5:7:8
21:exp:48:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, SHA-384, EtM
depends_on:4:16:5:7:8:20
21:exp:48:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, SHA-384, short tag
depends_on:4:16:5:7:8
21:exp:48:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:16:5:7:8:20
21:exp:48:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, SHA-256
depends_on:4:16:5:13
21:exp:48:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, SHA-256, EtM
depends_on:4:16:5:13:20
21:exp:48:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, SHA-256, short tag
depends_on:4:16:5:13
21:exp:48:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:16:5:13:20
21:exp:48:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, SHA-1
depends_on:4:16:5:21
21:exp:48:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, SHA-1, EtM
depends_on:4:16:5:21:20
21:exp:48:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, SHA-1, short tag
depends_on:4:16:5:21
21:exp:48:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:16:5:21:20
21:exp:48:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, MD5
depends_on:4:16:5:22
21:exp:48:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, MD5, EtM
depends_on:4:16:5:22:20
21:exp:48:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, MD5, short tag
depends_on:4:16:5:22
21:exp:48:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.1, MD5, short tag, EtM
depends_on:4:16:5:22:20
21:exp:48:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, SHA-384
depends_on:4:16:3:7:8
21:exp:48:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, SHA-384, EtM
depends_on:4:16:3:7:8:20
21:exp:48:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, SHA-384, short tag
depends_on:4:16:3:7:8
21:exp:48:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:16:3:7:8:20
21:exp:48:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, SHA-256
depends_on:4:16:3:13
21:exp:48:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, SHA-256, EtM
depends_on:4:16:3:13:20
21:exp:48:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, SHA-256, short tag
depends_on:4:16:3:13
21:exp:48:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:16:3:13:20
21:exp:48:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, SHA-1
depends_on:4:16:3:21
21:exp:48:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, SHA-1, EtM
depends_on:4:16:3:21:20
21:exp:48:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, SHA-1, short tag
depends_on:4:16:3:21
21:exp:48:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:16:3:21:20
21:exp:48:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, MD5
depends_on:4:16:3:22
21:exp:48:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, MD5, EtM
depends_on:4:16:3:22:20
21:exp:48:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, MD5, short tag
depends_on:4:16:3:22
21:exp:48:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, 1.0, MD5, short tag, EtM
depends_on:4:16:3:22:20
21:exp:48:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, SSL3, SHA-1
depends_on:4:16:0:21
21:exp:48:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, SSL3, SHA-1, EtM
depends_on:4:16:0:21:20
21:exp:48:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, SSL3, SHA-1, short tag
depends_on:4:16:0:21
21:exp:48:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:16:0:21:20
21:exp:48:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, SSL3, MD5
depends_on:4:16:0:22
21:exp:48:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, SSL3, MD5, EtM
depends_on:4:16:0:22:20
21:exp:48:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, SSL3, MD5, short tag
depends_on:4:16:0:22
21:exp:48:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-192-CBC, SSL3, MD5, short tag, EtM
depends_on:4:16:0:22:20
21:exp:48:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-384
depends_on:4:16:6:7:8
21:exp:49:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:16:6:7:8
21:exp:49:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:16:6:7:8
21:exp:49:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-384, EtM
depends_on:4:16:6:7:8:20
21:exp:49:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:16:6:7:8:20
21:exp:49:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:16:6:7:8:20
21:exp:49:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-384, short tag
depends_on:4:16:6:7:8
21:exp:49:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:16:6:7:8
21:exp:49:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:16:6:7:8
21:exp:49:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:16:6:7:8:20
21:exp:49:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:16:6:7:8:20
21:exp:49:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:16:6:7:8:20
21:exp:49:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-256
depends_on:4:16:6:13
21:exp:49:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:16:6:13
21:exp:49:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:16:6:13
21:exp:49:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-256, EtM
depends_on:4:16:6:13:20
21:exp:49:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:16:6:13:20
21:exp:49:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:16:6:13:20
21:exp:49:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-256, short tag
depends_on:4:16:6:13
21:exp:49:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:16:6:13
21:exp:49:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:16:6:13
21:exp:49:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:16:6:13:20
21:exp:49:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:16:6:13:20
21:exp:49:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:16:6:13:20
21:exp:49:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-1
depends_on:4:16:6:21
21:exp:49:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:16:6:21
21:exp:49:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:16:6:21
21:exp:49:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-1, EtM
depends_on:4:16:6:21:20
21:exp:49:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:16:6:21:20
21:exp:49:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:16:6:21:20
21:exp:49:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-1, short tag
depends_on:4:16:6:21
21:exp:49:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:16:6:21
21:exp:49:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:16:6:21
21:exp:49:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:16:6:21:20
21:exp:49:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:16:6:21:20
21:exp:49:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:16:6:21:20
21:exp:49:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, MD5
depends_on:4:16:6:22
21:exp:49:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:16:6:22
21:exp:49:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:16:6:22
21:exp:49:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, MD5, EtM
depends_on:4:16:6:22:20
21:exp:49:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:16:6:22:20
21:exp:49:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:16:6:22:20
21:exp:49:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, MD5, short tag
depends_on:4:16:6:22
21:exp:49:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:16:6:22
21:exp:49:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:16:6:22
21:exp:49:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, MD5, short tag, EtM
depends_on:4:16:6:22:20
21:exp:49:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:16:6:22:20
21:exp:49:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:16:6:22:20
21:exp:49:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, SHA-384
depends_on:4:16:5:7:8
21:exp:49:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, SHA-384, EtM
depends_on:4:16:5:7:8:20
21:exp:49:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, SHA-384, short tag
depends_on:4:16:5:7:8
21:exp:49:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:16:5:7:8:20
21:exp:49:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, SHA-256
depends_on:4:16:5:13
21:exp:49:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, SHA-256, EtM
depends_on:4:16:5:13:20
21:exp:49:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, SHA-256, short tag
depends_on:4:16:5:13
21:exp:49:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:16:5:13:20
21:exp:49:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, SHA-1
depends_on:4:16:5:21
21:exp:49:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, SHA-1, EtM
depends_on:4:16:5:21:20
21:exp:49:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, SHA-1, short tag
depends_on:4:16:5:21
21:exp:49:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:16:5:21:20
21:exp:49:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, MD5
depends_on:4:16:5:22
21:exp:49:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, MD5, EtM
depends_on:4:16:5:22:20
21:exp:49:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, MD5, short tag
depends_on:4:16:5:22
21:exp:49:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.1, MD5, short tag, EtM
depends_on:4:16:5:22:20
21:exp:49:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, SHA-384
depends_on:4:16:3:7:8
21:exp:49:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, SHA-384, EtM
depends_on:4:16:3:7:8:20
21:exp:49:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, SHA-384, short tag
depends_on:4:16:3:7:8
21:exp:49:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:16:3:7:8:20
21:exp:49:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, SHA-256
depends_on:4:16:3:13
21:exp:49:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, SHA-256, EtM
depends_on:4:16:3:13:20
21:exp:49:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, SHA-256, short tag
depends_on:4:16:3:13
21:exp:49:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:16:3:13:20
21:exp:49:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, SHA-1
depends_on:4:16:3:21
21:exp:49:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, SHA-1, EtM
depends_on:4:16:3:21:20
21:exp:49:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, SHA-1, short tag
depends_on:4:16:3:21
21:exp:49:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:16:3:21:20
21:exp:49:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, MD5
depends_on:4:16:3:22
21:exp:49:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, MD5, EtM
depends_on:4:16:3:22:20
21:exp:49:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, MD5, short tag
depends_on:4:16:3:22
21:exp:49:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, 1.0, MD5, short tag, EtM
depends_on:4:16:3:22:20
21:exp:49:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, SSL3, SHA-1
depends_on:4:16:0:21
21:exp:49:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, SSL3, SHA-1, EtM
depends_on:4:16:0:21:20
21:exp:49:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, SSL3, SHA-1, short tag
depends_on:4:16:0:21
21:exp:49:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:16:0:21:20
21:exp:49:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, SSL3, MD5
depends_on:4:16:0:22
21:exp:49:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, SSL3, MD5, EtM
depends_on:4:16:0:22:20
21:exp:49:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, SSL3, MD5, short tag
depends_on:4:16:0:22
21:exp:49:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, CAMELLIA-256-CBC, SSL3, MD5, short tag, EtM
depends_on:4:16:0:22:20
21:exp:49:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-384
depends_on:4:24:6:7:8
21:exp:50:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-384, CID 4+4
depends_on:19:4:24:6:7:8
21:exp:50:exp:38:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-384, CID 4+0
depends_on:19:4:24:6:7:8
21:exp:50:exp:38:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-384, EtM
depends_on:4:24:6:7:8:20
21:exp:50:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-384, EtM, CID 4+4
depends_on:19:4:24:6:7:8:20
21:exp:50:exp:38:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-384, EtM, CID 4+0
depends_on:19:4:24:6:7:8:20
21:exp:50:exp:38:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-384, short tag
depends_on:4:24:6:7:8
21:exp:50:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-384, short tag, CID 4+4
depends_on:19:4:24:6:7:8
21:exp:50:exp:38:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-384, short tag, CID 4+0
depends_on:19:4:24:6:7:8
21:exp:50:exp:38:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-384, short tag, EtM
depends_on:4:24:6:7:8:20
21:exp:50:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-384, short tag, EtM, CID 4+4
depends_on:19:4:24:6:7:8:20
21:exp:50:exp:38:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-384, short tag, EtM, CID 4+0
depends_on:19:4:24:6:7:8:20
21:exp:50:exp:38:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-256
depends_on:4:24:6:13
21:exp:50:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-256, CID 4+4
depends_on:19:4:24:6:13
21:exp:50:exp:39:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-256, CID 4+0
depends_on:19:4:24:6:13
21:exp:50:exp:39:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-256, EtM
depends_on:4:24:6:13:20
21:exp:50:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-256, EtM, CID 4+4
depends_on:19:4:24:6:13:20
21:exp:50:exp:39:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-256, EtM, CID 4+0
depends_on:19:4:24:6:13:20
21:exp:50:exp:39:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-256, short tag
depends_on:4:24:6:13
21:exp:50:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-256, short tag, CID 4+4
depends_on:19:4:24:6:13
21:exp:50:exp:39:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-256, short tag, CID 4+0
depends_on:19:4:24:6:13
21:exp:50:exp:39:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-256, short tag, EtM
depends_on:4:24:6:13:20
21:exp:50:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-256, short tag, EtM, CID 4+4
depends_on:19:4:24:6:13:20
21:exp:50:exp:39:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-256, short tag, EtM, CID 4+0
depends_on:19:4:24:6:13:20
21:exp:50:exp:39:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-1
depends_on:4:24:6:21
21:exp:50:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-1, CID 4+4
depends_on:19:4:24:6:21
21:exp:50:exp:40:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-1, CID 4+0
depends_on:19:4:24:6:21
21:exp:50:exp:40:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-1, EtM
depends_on:4:24:6:21:20
21:exp:50:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-1, EtM, CID 4+4
depends_on:19:4:24:6:21:20
21:exp:50:exp:40:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-1, EtM, CID 4+0
depends_on:19:4:24:6:21:20
21:exp:50:exp:40:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-1, short tag
depends_on:4:24:6:21
21:exp:50:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-1, short tag, CID 4+4
depends_on:19:4:24:6:21
21:exp:50:exp:40:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-1, short tag, CID 4+0
depends_on:19:4:24:6:21
21:exp:50:exp:40:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-1, short tag, EtM
depends_on:4:24:6:21:20
21:exp:50:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-1, short tag, EtM, CID 4+4
depends_on:19:4:24:6:21:20
21:exp:50:exp:40:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, SHA-1, short tag, EtM, CID 4+0
depends_on:19:4:24:6:21:20
21:exp:50:exp:40:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, MD5
depends_on:4:24:6:22
21:exp:50:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, MD5, CID 4+4
depends_on:19:4:24:6:22
21:exp:50:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, MD5, CID 4+0
depends_on:19:4:24:6:22
21:exp:50:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, MD5, EtM
depends_on:4:24:6:22:20
21:exp:50:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, MD5, EtM, CID 4+4
depends_on:19:4:24:6:22:20
21:exp:50:exp:41:int:1:int:0:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, MD5, EtM, CID 4+0
depends_on:19:4:24:6:22:20
21:exp:50:exp:41:int:1:int:0:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, MD5, short tag
depends_on:4:24:6:22
21:exp:50:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, MD5, short tag, CID 4+4
depends_on:19:4:24:6:22
21:exp:50:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, MD5, short tag, CID 4+0
depends_on:19:4:24:6:22
21:exp:50:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, MD5, short tag, EtM
depends_on:4:24:6:22:20
21:exp:50:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.2, MD5, short tag, EtM, CID 4+4
depends_on:19:4:24:6:22:20
21:exp:50:exp:41:int:1:int:1:exp:24:int:4:int:4
Record crypt, little space, BLOWFISH-CBC, 1.2, MD5, short tag, EtM, CID 4+0
depends_on:19:4:24:6:22:20
21:exp:50:exp:41:int:1:int:1:exp:24:int:4:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, SHA-384
depends_on:4:24:5:7:8
21:exp:50:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, SHA-384, EtM
depends_on:4:24:5:7:8:20
21:exp:50:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, SHA-384, short tag
depends_on:4:24:5:7:8
21:exp:50:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, SHA-384, short tag, EtM
depends_on:4:24:5:7:8:20
21:exp:50:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, SHA-256
depends_on:4:24:5:13
21:exp:50:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, SHA-256, EtM
depends_on:4:24:5:13:20
21:exp:50:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, SHA-256, short tag
depends_on:4:24:5:13
21:exp:50:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, SHA-256, short tag, EtM
depends_on:4:24:5:13:20
21:exp:50:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, SHA-1
depends_on:4:24:5:21
21:exp:50:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, SHA-1, EtM
depends_on:4:24:5:21:20
21:exp:50:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, SHA-1, short tag
depends_on:4:24:5:21
21:exp:50:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, SHA-1, short tag, EtM
depends_on:4:24:5:21:20
21:exp:50:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, MD5
depends_on:4:24:5:22
21:exp:50:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, MD5, EtM
depends_on:4:24:5:22:20
21:exp:50:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, MD5, short tag
depends_on:4:24:5:22
21:exp:50:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.1, MD5, short tag, EtM
depends_on:4:24:5:22:20
21:exp:50:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, SHA-384
depends_on:4:24:3:7:8
21:exp:50:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, SHA-384, EtM
depends_on:4:24:3:7:8:20
21:exp:50:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, SHA-384, short tag
depends_on:4:24:3:7:8
21:exp:50:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, SHA-384, short tag, EtM
depends_on:4:24:3:7:8:20
21:exp:50:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, SHA-256
depends_on:4:24:3:13
21:exp:50:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, SHA-256, EtM
depends_on:4:24:3:13:20
21:exp:50:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, SHA-256, short tag
depends_on:4:24:3:13
21:exp:50:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, SHA-256, short tag, EtM
depends_on:4:24:3:13:20
21:exp:50:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, SHA-1
depends_on:4:24:3:21
21:exp:50:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, SHA-1, EtM
depends_on:4:24:3:21:20
21:exp:50:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, SHA-1, short tag
depends_on:4:24:3:21
21:exp:50:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, SHA-1, short tag, EtM
depends_on:4:24:3:21:20
21:exp:50:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, MD5
depends_on:4:24:3:22
21:exp:50:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, MD5, EtM
depends_on:4:24:3:22:20
21:exp:50:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, MD5, short tag
depends_on:4:24:3:22
21:exp:50:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, 1.0, MD5, short tag, EtM
depends_on:4:24:3:22:20
21:exp:50:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, SSL3, SHA-1
depends_on:4:24:0:21
21:exp:50:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, SSL3, SHA-1, EtM
depends_on:4:24:0:21:20
21:exp:50:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, SSL3, SHA-1, short tag
depends_on:4:24:0:21
21:exp:50:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, SSL3, SHA-1, short tag, EtM
depends_on:4:24:0:21:20
21:exp:50:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, SSL3, MD5
depends_on:4:24:0:22
21:exp:50:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, SSL3, MD5, EtM
depends_on:4:24:0:22:20
21:exp:50:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, SSL3, MD5, short tag
depends_on:4:24:0:22
21:exp:50:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, BLOWFISH-CBC, SSL3, MD5, short tag, EtM
depends_on:4:24:0:22:20
21:exp:50:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, AES128-GCM, 1.2
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:10
21:exp:51:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES128-GCM, 1.3
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:25:10
21:exp:51:exp:41:int:0:int:0:exp:52:int:0:int:0
Record crypt, little space, AES128-GCM, 1.2, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
21:exp:51:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES128-GCM, 1.2, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
21:exp:51:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES128-GCM, 1.2, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:10
21:exp:51:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES128-GCM, 1.2, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
21:exp:51:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES128-GCM, 1.2, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
21:exp:51:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES-192-GCM, 1.2
depends_on:9:6:10
21:exp:53:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES-192-GCM, 1.3
depends_on:9:25:10
21:exp:53:exp:41:int:0:int:0:exp:52:int:0:int:0
Record crypt, little space, AES-192-GCM, 1.2, CID 4+4
depends_on:19:9:6:10
21:exp:53:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES-192-GCM, 1.2, CID 4+0
depends_on:19:9:6:10
21:exp:53:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES-192-GCM, 1.2, short tag
depends_on:9:6:10
21:exp:53:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES-192-GCM, 1.2, short tag, CID 4+4
depends_on:19:9:6:10
21:exp:53:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES-192-GCM, 1.2, short tag, CID 4+0
depends_on:19:9:6:10
21:exp:53:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES256-GCM, 1.2
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:10
21:exp:54:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES256-GCM, 1.3
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:25:10
21:exp:54:exp:41:int:0:int:0:exp:52:int:0:int:0
Record crypt, little space, AES256-GCM, 1.2, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
21:exp:54:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES256-GCM, 1.2, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
21:exp:54:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES256-GCM, 1.2, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:10
21:exp:54:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES256-GCM, 1.2, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
21:exp:54:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES256-GCM, 1.2, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:10
21:exp:54:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-GCM, 1.2
depends_on:16:6:10
21:exp:55:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-GCM, 1.2, CID 4+4
depends_on:19:16:6:10
21:exp:55:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-GCM, 1.2, CID 4+0
depends_on:19:16:6:10
21:exp:55:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-GCM, 1.2, short tag
depends_on:16:6:10
21:exp:55:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-GCM, 1.2, short tag, CID 4+4
depends_on:19:16:6:10
21:exp:55:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-GCM, 1.2, short tag, CID 4+0
depends_on:19:16:6:10
21:exp:55:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-GCM, 1.2
depends_on:16:6:10
21:exp:56:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-GCM, 1.2, CID 4+4
depends_on:19:16:6:10
21:exp:56:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-GCM, 1.2, CID 4+0
depends_on:19:16:6:10
21:exp:56:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-GCM, 1.2, short tag
depends_on:16:6:10
21:exp:56:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-GCM, 1.2, short tag, CID 4+4
depends_on:19:16:6:10
21:exp:56:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-GCM, 1.2, short tag, CID 4+0
depends_on:19:16:6:10
21:exp:56:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-GCM, 1.2
depends_on:16:6:10
21:exp:57:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-GCM, 1.2, CID 4+4
depends_on:19:16:6:10
21:exp:57:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-GCM, 1.2, CID 4+0
depends_on:19:16:6:10
21:exp:57:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-GCM, 1.2, short tag
depends_on:16:6:10
21:exp:57:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-GCM, 1.2, short tag, CID 4+4
depends_on:19:16:6:10
21:exp:57:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-GCM, 1.2, short tag, CID 4+0
depends_on:19:16:6:10
21:exp:57:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES128-CCM, 1.2
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:12
21:exp:58:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES128-CCM, 1.3
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:25:12
21:exp:58:exp:41:int:0:int:0:exp:52:int:0:int:0
Record crypt, little space, AES128-CCM, 1.2, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
21:exp:58:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES128-CCM, 1.2, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
21:exp:58:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES128-CCM, 1.2, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:12
21:exp:58:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES128-CCM, 1.2, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
21:exp:58:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES128-CCM, 1.2, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
21:exp:58:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES-192-CCM, 1.2
depends_on:9:6:12
21:exp:59:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES-192-CCM, 1.3
depends_on:9:25:12
21:exp:59:exp:41:int:0:int:0:exp:52:int:0:int:0
Record crypt, little space, AES-192-CCM, 1.2, CID 4+4
depends_on:19:9:6:12
21:exp:59:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES-192-CCM, 1.2, CID 4+0
depends_on:19:9:6:12
21:exp:59:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES-192-CCM, 1.2, short tag
depends_on:9:6:12
21:exp:59:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES-192-CCM, 1.2, short tag, CID 4+4
depends_on:19:9:6:12
21:exp:59:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES-192-CCM, 1.2, short tag, CID 4+0
depends_on:19:9:6:12
21:exp:59:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, AES256-CCM, 1.2
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:12
21:exp:60:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, AES256-CCM, 1.3
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:25:12
21:exp:60:exp:41:int:0:int:0:exp:52:int:0:int:0
Record crypt, little space, AES256-CCM, 1.2, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
21:exp:60:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, AES256-CCM, 1.2, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
21:exp:60:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, AES256-CCM, 1.2, short tag
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:9:6:12
21:exp:60:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, AES256-CCM, 1.2, short tag, CID 4+4
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
21:exp:60:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, AES256-CCM, 1.2, short tag, CID 4+0
Add SSL to redbean Your redbean can now interoperate with clients that require TLS crypto. This is accomplished using a protocol polyglot that lets us distinguish between HTTP and HTTPS regardless of the port number. Certificates will be generated automatically, if none are supplied by the user. Footprint increases by only a few hundred kb so redbean in MODY=tiny is now 1.0mb - Add lseek() polyfills for ZIP executable - Automatically polyfill /tmp/FOO paths on NT - Fix readdir() / ftw() / nftw() bugs on Windows - Introduce -B flag for slower SSL that's stronger - Remove mbedtls features Cosmopolitan doesn't need - Have base64 decoder support the uri-safe alternative - Remove Truncated HMAC because it's forbidden by the IETF - Add all the mbedtls test suites and make them go 3x faster - Support opendir() / readdir() / closedir() on ZIP executable - Use Everest for ECDHE-ECDSA because it's so good it's so good - Add tinier implementation of sha1 since it's not worth the rom - Add chi-square monte-carlo mean correlation tests for getrandom() - Source entropy on Windows from the proper interface everyone uses We're continuing to outperform NGINX and other servers on raw message throughput. Using SSL means that instead of 1,000,000 qps you can get around 300,000 qps. However redbean isn't as fast as NGINX yet at SSL handshakes, since redbean can do 2,627 per second and NGINX does 4.3k Right now, the SSL UX story works best if you give your redbean a key signing key since that can be easily generated by openssl using a one liner then redbean will do all the things that are impossibly hard to do like signing ecdsa and rsa certificates that'll work in chrome. We should integrate the let's encrypt acme protocol in the future. Live Demo: https://redbean.justine.lol/ Root Cert: https://redbean.justine.lol/redbean1.crt
2021-06-24 19:31:26 +00:00
depends_on:19:9:6:12
21:exp:60:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CCM, 1.2
depends_on:16:6:12
21:exp:61:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CCM, 1.2, CID 4+4
depends_on:19:16:6:12
21:exp:61:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CCM, 1.2, CID 4+0
depends_on:19:16:6:12
21:exp:61:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-128-CCM, 1.2, short tag
depends_on:16:6:12
21:exp:61:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-128-CCM, 1.2, short tag, CID 4+4
depends_on:19:16:6:12
21:exp:61:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-128-CCM, 1.2, short tag, CID 4+0
depends_on:19:16:6:12
21:exp:61:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CCM, 1.2
depends_on:16:6:12
21:exp:62:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CCM, 1.2, CID 4+4
depends_on:19:16:6:12
21:exp:62:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CCM, 1.2, CID 4+0
depends_on:19:16:6:12
21:exp:62:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-192-CCM, 1.2, short tag
depends_on:16:6:12
21:exp:62:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-192-CCM, 1.2, short tag, CID 4+4
depends_on:19:16:6:12
21:exp:62:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-192-CCM, 1.2, short tag, CID 4+0
depends_on:19:16:6:12
21:exp:62:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CCM, 1.2
depends_on:16:6:12
21:exp:63:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CCM, 1.2, CID 4+4
depends_on:19:16:6:12
21:exp:63:exp:41:int:0:int:0:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CCM, 1.2, CID 4+0
depends_on:19:16:6:12
21:exp:63:exp:41:int:0:int:0:exp:24:int:4:int:0
Record crypt, little space, CAMELLIA-256-CCM, 1.2, short tag
depends_on:16:6:12
21:exp:63:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, CAMELLIA-256-CCM, 1.2, short tag, CID 4+4
depends_on:19:16:6:12
21:exp:63:exp:41:int:0:int:1:exp:24:int:4:int:4
Record crypt, little space, CAMELLIA-256-CCM, 1.2, short tag, CID 4+0
depends_on:19:16:6:12
21:exp:63:exp:41:int:0:int:1:exp:24:int:4:int:0
Record crypt, little space, ARC4-128, 1.2, SHA-384
depends_on:26:6:7:8
21:exp:64:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.2, SHA-384, EtM
depends_on:26:6:7:8:20
21:exp:64:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.2, SHA-384, short tag
depends_on:26:6:7:8
21:exp:64:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.2, SHA-384, short tag, EtM
depends_on:26:6:7:8:20
21:exp:64:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.2, SHA-256
depends_on:26:6:13
21:exp:64:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.2, SHA-256, EtM
depends_on:26:6:13:20
21:exp:64:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.2, SHA-256, short tag
depends_on:26:6:13
21:exp:64:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.2, SHA-256, short tag, EtM
depends_on:26:6:13:20
21:exp:64:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.2, SHA-1
depends_on:26:6:21
21:exp:64:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.2, SHA-1, EtM
depends_on:26:6:21:20
21:exp:64:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.2, SHA-1, short tag
depends_on:26:6:21
21:exp:64:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.2, SHA-1, short tag, EtM
depends_on:26:6:21:20
21:exp:64:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.2, MD5
depends_on:26:6:22
21:exp:64:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.2, MD5, EtM
depends_on:26:6:22:20
21:exp:64:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.2, MD5, short tag
depends_on:26:6:22
21:exp:64:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.2, MD5, short tag, EtM
depends_on:26:6:22:20
21:exp:64:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, SHA-384
depends_on:26:5:7:8
21:exp:64:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, SHA-384, EtM
depends_on:26:5:7:8:20
21:exp:64:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, SHA-384, short tag
depends_on:26:5:7:8
21:exp:64:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, SHA-384, short tag, EtM
depends_on:26:5:7:8:20
21:exp:64:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, SHA-256
depends_on:26:5:13
21:exp:64:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, SHA-256, EtM
depends_on:26:5:13:20
21:exp:64:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, SHA-256, short tag
depends_on:26:5:13
21:exp:64:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, SHA-256, short tag, EtM
depends_on:26:5:13:20
21:exp:64:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, SHA-1
depends_on:26:5:21
21:exp:64:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, SHA-1, EtM
depends_on:26:5:21:20
21:exp:64:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, SHA-1, short tag
depends_on:26:5:21
21:exp:64:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, SHA-1, short tag, EtM
depends_on:26:5:21:20
21:exp:64:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, MD5
depends_on:26:5:22
21:exp:64:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, MD5, EtM
depends_on:26:5:22:20
21:exp:64:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, MD5, short tag
depends_on:26:5:22
21:exp:64:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.1, MD5, short tag, EtM
depends_on:26:5:22:20
21:exp:64:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, SHA-384
depends_on:26:3:7:8
21:exp:64:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, SHA-384, EtM
depends_on:26:3:7:8:20
21:exp:64:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, SHA-384, short tag
depends_on:26:3:7:8
21:exp:64:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, SHA-384, short tag, EtM
depends_on:26:3:7:8:20
21:exp:64:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, SHA-256
depends_on:26:3:13
21:exp:64:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, SHA-256, EtM
depends_on:26:3:13:20
21:exp:64:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, SHA-256, short tag
depends_on:26:3:13
21:exp:64:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, SHA-256, short tag, EtM
depends_on:26:3:13:20
21:exp:64:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, SHA-1
depends_on:26:3:21
21:exp:64:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, SHA-1, EtM
depends_on:26:3:21:20
21:exp:64:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, SHA-1, short tag
depends_on:26:3:21
21:exp:64:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, SHA-1, short tag, EtM
depends_on:26:3:21:20
21:exp:64:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, MD5
depends_on:26:3:22
21:exp:64:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, MD5, EtM
depends_on:26:3:22:20
21:exp:64:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, MD5, short tag
depends_on:26:3:22
21:exp:64:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, 1.0, MD5, short tag, EtM
depends_on:26:3:22:20
21:exp:64:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, ARC4-128, SSL3, SHA-1
depends_on:26:0:21
21:exp:64:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, ARC4-128, SSL3, SHA-1, EtM
depends_on:26:0:21:20
21:exp:64:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, ARC4-128, SSL3, SHA-1, short tag
depends_on:26:0:21
21:exp:64:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, ARC4-128, SSL3, SHA-1, short tag, EtM
depends_on:26:0:21:20
21:exp:64:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, ARC4-128, SSL3, MD5
depends_on:26:0:22
21:exp:64:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, ARC4-128, SSL3, MD5, EtM
depends_on:26:0:22:20
21:exp:64:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, ARC4-128, SSL3, MD5, short tag
depends_on:26:0:22
21:exp:64:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, ARC4-128, SSL3, MD5, short tag, EtM
depends_on:26:0:22:20
21:exp:64:exp:41:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, SHA-384
depends_on:27:6:7:8
21:exp:65:exp:38:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, SHA-384, EtM
depends_on:27:6:7:8:20
21:exp:65:exp:38:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, SHA-384, short tag
depends_on:27:6:7:8
21:exp:65:exp:38:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, SHA-384, short tag, EtM
depends_on:27:6:7:8:20
21:exp:65:exp:38:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, SHA-256
depends_on:27:6:13
21:exp:65:exp:39:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, SHA-256, EtM
depends_on:27:6:13:20
21:exp:65:exp:39:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, SHA-256, short tag
depends_on:27:6:13
21:exp:65:exp:39:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, SHA-256, short tag, EtM
depends_on:27:6:13:20
21:exp:65:exp:39:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, SHA-1
depends_on:27:6:21
21:exp:65:exp:40:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, SHA-1, EtM
depends_on:27:6:21:20
21:exp:65:exp:40:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, SHA-1, short tag
depends_on:27:6:21
21:exp:65:exp:40:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, SHA-1, short tag, EtM
depends_on:27:6:21:20
21:exp:65:exp:40:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, MD5
depends_on:27:6:22
21:exp:65:exp:41:int:0:int:0:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, MD5, EtM
depends_on:27:6:22:20
21:exp:65:exp:41:int:1:int:0:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, MD5, short tag
depends_on:27:6:22
21:exp:65:exp:41:int:0:int:1:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.2, MD5, short tag, EtM
depends_on:27:6:22:20
21:exp:65:exp:41:int:1:int:1:exp:24:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, SHA-384
depends_on:27:5:7:8
21:exp:65:exp:38:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, SHA-384, EtM
depends_on:27:5:7:8:20
21:exp:65:exp:38:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, SHA-384, short tag
depends_on:27:5:7:8
21:exp:65:exp:38:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, SHA-384, short tag, EtM
depends_on:27:5:7:8:20
21:exp:65:exp:38:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, SHA-256
depends_on:27:5:13
21:exp:65:exp:39:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, SHA-256, EtM
depends_on:27:5:13:20
21:exp:65:exp:39:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, SHA-256, short tag
depends_on:27:5:13
21:exp:65:exp:39:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, SHA-256, short tag, EtM
depends_on:27:5:13:20
21:exp:65:exp:39:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, SHA-1
depends_on:27:5:21
21:exp:65:exp:40:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, SHA-1, EtM
depends_on:27:5:21:20
21:exp:65:exp:40:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, SHA-1, short tag
depends_on:27:5:21
21:exp:65:exp:40:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, SHA-1, short tag, EtM
depends_on:27:5:21:20
21:exp:65:exp:40:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, MD5
depends_on:27:5:22
21:exp:65:exp:41:int:0:int:0:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, MD5, EtM
depends_on:27:5:22:20
21:exp:65:exp:41:int:1:int:0:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, MD5, short tag
depends_on:27:5:22
21:exp:65:exp:41:int:0:int:1:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.1, MD5, short tag, EtM
depends_on:27:5:22:20
21:exp:65:exp:41:int:1:int:1:exp:23:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, SHA-384
depends_on:27:3:7:8
21:exp:65:exp:38:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, SHA-384, EtM
depends_on:27:3:7:8:20
21:exp:65:exp:38:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, SHA-384, short tag
depends_on:27:3:7:8
21:exp:65:exp:38:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, SHA-384, short tag, EtM
depends_on:27:3:7:8:20
21:exp:65:exp:38:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, SHA-256
depends_on:27:3:13
21:exp:65:exp:39:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, SHA-256, EtM
depends_on:27:3:13:20
21:exp:65:exp:39:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, SHA-256, short tag
depends_on:27:3:13
21:exp:65:exp:39:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, SHA-256, short tag, EtM
depends_on:27:3:13:20
21:exp:65:exp:39:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, SHA-1
depends_on:27:3:21
21:exp:65:exp:40:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, SHA-1, EtM
depends_on:27:3:21:20
21:exp:65:exp:40:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, SHA-1, short tag
depends_on:27:3:21
21:exp:65:exp:40:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, SHA-1, short tag, EtM
depends_on:27:3:21:20
21:exp:65:exp:40:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, MD5
depends_on:27:3:22
21:exp:65:exp:41:int:0:int:0:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, MD5, EtM
depends_on:27:3:22:20
21:exp:65:exp:41:int:1:int:0:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, MD5, short tag
depends_on:27:3:22
21:exp:65:exp:41:int:0:int:1:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, 1.0, MD5, short tag, EtM
depends_on:27:3:22:20
21:exp:65:exp:41:int:1:int:1:exp:22:int:0:int:0
Record crypt, little space, NULL cipher, SSL3, SHA-1
depends_on:27:0:21
21:exp:65:exp:40:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, NULL cipher, SSL3, SHA-1, EtM
depends_on:27:0:21:20
21:exp:65:exp:40:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, NULL cipher, SSL3, SHA-1, short tag
depends_on:27:0:21
21:exp:65:exp:40:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, NULL cipher, SSL3, SHA-1, short tag, EtM
depends_on:27:0:21:20
21:exp:65:exp:40:int:1:int:1:exp:21:int:0:int:0
Record crypt, little space, NULL cipher, SSL3, MD5
depends_on:27:0:22
21:exp:65:exp:41:int:0:int:0:exp:21:int:0:int:0
Record crypt, little space, NULL cipher, SSL3, MD5, EtM
depends_on:27:0:22:20
21:exp:65:exp:41:int:1:int:0:exp:21:int:0:int:0
Record crypt, little space, NULL cipher, SSL3, MD5, short tag
depends_on:27:0:22
21:exp:65:exp:41:int:0:int:1:exp:21:int:0:int:0
Record crypt, little space, NULL cipher, SSL3, MD5, short tag, EtM
depends_on:27:0:22:20
21:exp:65:exp:41:int:1:int:1:exp:21:int:0:int:0
Decrypt CBC !EtM, AES MD5 !trunc, empty plaintext, minpad
depends_on:9:22
22:exp:37:exp:41:int:0:exp:36
Decrypt CBC !EtM, AES MD5 !trunc, empty plaintext, maxpad
depends_on:9:22
22:exp:37:exp:41:int:0:exp:67
Decrypt CBC !EtM, AES MD5 trunc, empty plaintext, minpad
depends_on:9:22
22:exp:37:exp:41:int:1:exp:36
Decrypt CBC !EtM, AES MD5 trunc, empty plaintext, maxpad
depends_on:9:22
22:exp:37:exp:41:int:1:exp:67
Decrypt CBC !EtM, AES MD5 !trunc, padlen=0
depends_on:9:22
22:exp:37:exp:41:int:0:int:0
Decrypt CBC !EtM, AES MD5 !trunc, padlen=240
depends_on:9:22
22:exp:37:exp:41:int:0:int:240
Decrypt CBC !EtM, AES MD5 trunc, padlen=0
depends_on:9:22
22:exp:37:exp:41:int:1:int:0
Decrypt CBC !EtM, AES MD5 trunc, padlen=240
depends_on:9:22
22:exp:37:exp:41:int:1:int:240
Decrypt CBC !EtM, AES MD5 !trunc, padlen=1
depends_on:9:22
22:exp:37:exp:41:int:0:int:1
Decrypt CBC !EtM, AES MD5 !trunc, padlen=241
depends_on:9:22
22:exp:37:exp:41:int:0:int:241
Decrypt CBC !EtM, AES MD5 trunc, padlen=1
depends_on:9:22
22:exp:37:exp:41:int:1:int:1
Decrypt CBC !EtM, AES MD5 trunc, padlen=241
depends_on:9:22
22:exp:37:exp:41:int:1:int:241
Decrypt CBC !EtM, AES MD5 !trunc, padlen=15
depends_on:9:22
22:exp:37:exp:41:int:0:int:15
Decrypt CBC !EtM, AES MD5 !trunc, padlen=255
depends_on:9:22
22:exp:37:exp:41:int:0:int:255
Decrypt CBC !EtM, AES MD5 trunc, padlen=15
depends_on:9:22
22:exp:37:exp:41:int:1:int:15
Decrypt CBC !EtM, AES MD5 trunc, padlen=255
depends_on:9:22
22:exp:37:exp:41:int:1:int:255
Decrypt CBC !EtM, AES SHA1 !trunc, empty plaintext, minpad
depends_on:9:21
22:exp:37:exp:40:int:0:exp:36
Decrypt CBC !EtM, AES SHA1 !trunc, empty plaintext, maxpad
depends_on:9:21
22:exp:37:exp:40:int:0:exp:67
Decrypt CBC !EtM, AES SHA1 trunc, empty plaintext, minpad
depends_on:9:21
22:exp:37:exp:40:int:1:exp:36
Decrypt CBC !EtM, AES SHA1 trunc, empty plaintext, maxpad
depends_on:9:21
22:exp:37:exp:40:int:1:exp:67
Decrypt CBC !EtM, AES SHA1 !trunc, padlen=0
depends_on:9:21
22:exp:37:exp:40:int:0:int:0
Decrypt CBC !EtM, AES SHA1 !trunc, padlen=240
depends_on:9:21
22:exp:37:exp:40:int:0:int:240
Decrypt CBC !EtM, AES SHA1 trunc, padlen=0
depends_on:9:21
22:exp:37:exp:40:int:1:int:0
Decrypt CBC !EtM, AES SHA1 trunc, padlen=240
depends_on:9:21
22:exp:37:exp:40:int:1:int:240
Decrypt CBC !EtM, AES SHA1 !trunc, padlen=1
depends_on:9:21
22:exp:37:exp:40:int:0:int:1
Decrypt CBC !EtM, AES SHA1 !trunc, padlen=241
depends_on:9:21
22:exp:37:exp:40:int:0:int:241
Decrypt CBC !EtM, AES SHA1 trunc, padlen=1
depends_on:9:21
22:exp:37:exp:40:int:1:int:1
Decrypt CBC !EtM, AES SHA1 trunc, padlen=241
depends_on:9:21
22:exp:37:exp:40:int:1:int:241
Decrypt CBC !EtM, AES SHA1 !trunc, padlen=15
depends_on:9:21
22:exp:37:exp:40:int:0:int:15
Decrypt CBC !EtM, AES SHA1 !trunc, padlen=255
depends_on:9:21
22:exp:37:exp:40:int:0:int:255
Decrypt CBC !EtM, AES SHA1 trunc, padlen=15
depends_on:9:21
22:exp:37:exp:40:int:1:int:15
Decrypt CBC !EtM, AES SHA1 trunc, padlen=255
depends_on:9:21
22:exp:37:exp:40:int:1:int:255
Decrypt CBC !EtM, AES SHA256 !trunc, empty plaintext, minpad
depends_on:9:13
22:exp:37:exp:39:int:0:exp:36
Decrypt CBC !EtM, AES SHA256 !trunc, empty plaintext, maxpad
depends_on:9:13
22:exp:37:exp:39:int:0:exp:67
Decrypt CBC !EtM, AES SHA256 trunc, empty plaintext, minpad
depends_on:9:13
22:exp:37:exp:39:int:1:exp:36
Decrypt CBC !EtM, AES SHA256 trunc, empty plaintext, maxpad
depends_on:9:13
22:exp:37:exp:39:int:1:exp:67
Decrypt CBC !EtM, AES SHA256 !trunc, padlen=0
depends_on:9:13
22:exp:37:exp:39:int:0:int:0
Decrypt CBC !EtM, AES SHA256 !trunc, padlen=240
depends_on:9:13
22:exp:37:exp:39:int:0:int:240
Decrypt CBC !EtM, AES SHA256 trunc, padlen=0
depends_on:9:13
22:exp:37:exp:39:int:1:int:0
Decrypt CBC !EtM, AES SHA256 trunc, padlen=240
depends_on:9:13
22:exp:37:exp:39:int:1:int:240
Decrypt CBC !EtM, AES SHA256 !trunc, padlen=1
depends_on:9:13
22:exp:37:exp:39:int:0:int:1
Decrypt CBC !EtM, AES SHA256 !trunc, padlen=241
depends_on:9:13
22:exp:37:exp:39:int:0:int:241
Decrypt CBC !EtM, AES SHA256 trunc, padlen=1
depends_on:9:13
22:exp:37:exp:39:int:1:int:1
Decrypt CBC !EtM, AES SHA256 trunc, padlen=241
depends_on:9:13
22:exp:37:exp:39:int:1:int:241
Decrypt CBC !EtM, AES SHA256 !trunc, padlen=15
depends_on:9:13
22:exp:37:exp:39:int:0:int:15
Decrypt CBC !EtM, AES SHA256 !trunc, padlen=255
depends_on:9:13
22:exp:37:exp:39:int:0:int:255
Decrypt CBC !EtM, AES SHA256 trunc, padlen=15
depends_on:9:13
22:exp:37:exp:39:int:1:int:15
Decrypt CBC !EtM, AES SHA256 trunc, padlen=255
depends_on:9:13
22:exp:37:exp:39:int:1:int:255
Decrypt CBC !EtM, AES SHA384 !trunc, empty plaintext, minpad
depends_on:9:7:8
22:exp:37:exp:38:int:0:exp:36
Decrypt CBC !EtM, AES SHA384 !trunc, empty plaintext, maxpad
depends_on:9:7:8
22:exp:37:exp:38:int:0:exp:67
Decrypt CBC !EtM, AES SHA384 trunc, empty plaintext, minpad
depends_on:9:7:8
22:exp:37:exp:38:int:1:exp:36
Decrypt CBC !EtM, AES SHA384 trunc, empty plaintext, maxpad
depends_on:9:7:8
22:exp:37:exp:38:int:1:exp:67
Decrypt CBC !EtM, AES SHA384 !trunc, padlen=0
depends_on:9:7:8
22:exp:37:exp:38:int:0:int:0
Decrypt CBC !EtM, AES SHA384 !trunc, padlen=240
depends_on:9:7:8
22:exp:37:exp:38:int:0:int:240
Decrypt CBC !EtM, AES SHA384 trunc, padlen=0
depends_on:9:7:8
22:exp:37:exp:38:int:1:int:0
Decrypt CBC !EtM, AES SHA384 trunc, padlen=240
depends_on:9:7:8
22:exp:37:exp:38:int:1:int:240
Decrypt CBC !EtM, AES SHA384 !trunc, padlen=1
depends_on:9:7:8
22:exp:37:exp:38:int:0:int:1
Decrypt CBC !EtM, AES SHA384 !trunc, padlen=241
depends_on:9:7:8
22:exp:37:exp:38:int:0:int:241
Decrypt CBC !EtM, AES SHA384 trunc, padlen=1
depends_on:9:7:8
22:exp:37:exp:38:int:1:int:1
Decrypt CBC !EtM, AES SHA384 trunc, padlen=241
depends_on:9:7:8
22:exp:37:exp:38:int:1:int:241
Decrypt CBC !EtM, AES SHA384 !trunc, padlen=15
depends_on:9:7:8
22:exp:37:exp:38:int:0:int:15
Decrypt CBC !EtM, AES SHA384 !trunc, padlen=255
depends_on:9:7:8
22:exp:37:exp:38:int:0:int:255
Decrypt CBC !EtM, AES SHA384 trunc, padlen=15
depends_on:9:7:8
22:exp:37:exp:38:int:1:int:15
Decrypt CBC !EtM, AES SHA384 trunc, padlen=255
depends_on:9:7:8
22:exp:37:exp:38:int:1:int:255
Decrypt CBC !EtM, ARIA MD5 !trunc, empty plaintext, minpad
depends_on:23:22
22:exp:44:exp:41:int:0:exp:36
Decrypt CBC !EtM, ARIA MD5 !trunc, empty plaintext, maxpad
depends_on:23:22
22:exp:44:exp:41:int:0:exp:67
Decrypt CBC !EtM, ARIA MD5 trunc, empty plaintext, minpad
depends_on:23:22
22:exp:44:exp:41:int:1:exp:36
Decrypt CBC !EtM, ARIA MD5 trunc, empty plaintext, maxpad
depends_on:23:22
22:exp:44:exp:41:int:1:exp:67
Decrypt CBC !EtM, ARIA MD5 !trunc, padlen=0
depends_on:23:22
22:exp:44:exp:41:int:0:int:0
Decrypt CBC !EtM, ARIA MD5 !trunc, padlen=240
depends_on:23:22
22:exp:44:exp:41:int:0:int:240
Decrypt CBC !EtM, ARIA MD5 trunc, padlen=0
depends_on:23:22
22:exp:44:exp:41:int:1:int:0
Decrypt CBC !EtM, ARIA MD5 trunc, padlen=240
depends_on:23:22
22:exp:44:exp:41:int:1:int:240
Decrypt CBC !EtM, ARIA MD5 !trunc, padlen=1
depends_on:23:22
22:exp:44:exp:41:int:0:int:1
Decrypt CBC !EtM, ARIA MD5 !trunc, padlen=241
depends_on:23:22
22:exp:44:exp:41:int:0:int:241
Decrypt CBC !EtM, ARIA MD5 trunc, padlen=1
depends_on:23:22
22:exp:44:exp:41:int:1:int:1
Decrypt CBC !EtM, ARIA MD5 trunc, padlen=241
depends_on:23:22
22:exp:44:exp:41:int:1:int:241
Decrypt CBC !EtM, ARIA MD5 !trunc, padlen=15
depends_on:23:22
22:exp:44:exp:41:int:0:int:15
Decrypt CBC !EtM, ARIA MD5 !trunc, padlen=255
depends_on:23:22
22:exp:44:exp:41:int:0:int:255
Decrypt CBC !EtM, ARIA MD5 trunc, padlen=15
depends_on:23:22
22:exp:44:exp:41:int:1:int:15
Decrypt CBC !EtM, ARIA MD5 trunc, padlen=255
depends_on:23:22
22:exp:44:exp:41:int:1:int:255
Decrypt CBC !EtM, ARIA SHA1 !trunc, empty plaintext, minpad
depends_on:23:21
22:exp:44:exp:40:int:0:exp:36
Decrypt CBC !EtM, ARIA SHA1 !trunc, empty plaintext, maxpad
depends_on:23:21
22:exp:44:exp:40:int:0:exp:67
Decrypt CBC !EtM, ARIA SHA1 trunc, empty plaintext, minpad
depends_on:23:21
22:exp:44:exp:40:int:1:exp:36
Decrypt CBC !EtM, ARIA SHA1 trunc, empty plaintext, maxpad
depends_on:23:21
22:exp:44:exp:40:int:1:exp:67
Decrypt CBC !EtM, ARIA SHA1 !trunc, padlen=0
depends_on:23:21
22:exp:44:exp:40:int:0:int:0
Decrypt CBC !EtM, ARIA SHA1 !trunc, padlen=240
depends_on:23:21
22:exp:44:exp:40:int:0:int:240
Decrypt CBC !EtM, ARIA SHA1 trunc, padlen=0
depends_on:23:21
22:exp:44:exp:40:int:1:int:0
Decrypt CBC !EtM, ARIA SHA1 trunc, padlen=240
depends_on:23:21
22:exp:44:exp:40:int:1:int:240
Decrypt CBC !EtM, ARIA SHA1 !trunc, padlen=1
depends_on:23:21
22:exp:44:exp:40:int:0:int:1
Decrypt CBC !EtM, ARIA SHA1 !trunc, padlen=241
depends_on:23:21
22:exp:44:exp:40:int:0:int:241
Decrypt CBC !EtM, ARIA SHA1 trunc, padlen=1
depends_on:23:21
22:exp:44:exp:40:int:1:int:1
Decrypt CBC !EtM, ARIA SHA1 trunc, padlen=241
depends_on:23:21
22:exp:44:exp:40:int:1:int:241
Decrypt CBC !EtM, ARIA SHA1 !trunc, padlen=15
depends_on:23:21
22:exp:44:exp:40:int:0:int:15
Decrypt CBC !EtM, ARIA SHA1 !trunc, padlen=255
depends_on:23:21
22:exp:44:exp:40:int:0:int:255
Decrypt CBC !EtM, ARIA SHA1 trunc, padlen=15
depends_on:23:21
22:exp:44:exp:40:int:1:int:15
Decrypt CBC !EtM, ARIA SHA1 trunc, padlen=255
depends_on:23:21
22:exp:44:exp:40:int:1:int:255
Decrypt CBC !EtM, ARIA SHA256 !trunc, empty plaintext, minpad
depends_on:23:13
22:exp:44:exp:39:int:0:exp:36
Decrypt CBC !EtM, ARIA SHA256 !trunc, empty plaintext, maxpad
depends_on:23:13
22:exp:44:exp:39:int:0:exp:67
Decrypt CBC !EtM, ARIA SHA256 trunc, empty plaintext, minpad
depends_on:23:13
22:exp:44:exp:39:int:1:exp:36
Decrypt CBC !EtM, ARIA SHA256 trunc, empty plaintext, maxpad
depends_on:23:13
22:exp:44:exp:39:int:1:exp:67
Decrypt CBC !EtM, ARIA SHA256 !trunc, padlen=0
depends_on:23:13
22:exp:44:exp:39:int:0:int:0
Decrypt CBC !EtM, ARIA SHA256 !trunc, padlen=240
depends_on:23:13
22:exp:44:exp:39:int:0:int:240
Decrypt CBC !EtM, ARIA SHA256 trunc, padlen=0
depends_on:23:13
22:exp:44:exp:39:int:1:int:0
Decrypt CBC !EtM, ARIA SHA256 trunc, padlen=240
depends_on:23:13
22:exp:44:exp:39:int:1:int:240
Decrypt CBC !EtM, ARIA SHA256 !trunc, padlen=1
depends_on:23:13
22:exp:44:exp:39:int:0:int:1
Decrypt CBC !EtM, ARIA SHA256 !trunc, padlen=241
depends_on:23:13
22:exp:44:exp:39:int:0:int:241
Decrypt CBC !EtM, ARIA SHA256 trunc, padlen=1
depends_on:23:13
22:exp:44:exp:39:int:1:int:1
Decrypt CBC !EtM, ARIA SHA256 trunc, padlen=241
depends_on:23:13
22:exp:44:exp:39:int:1:int:241
Decrypt CBC !EtM, ARIA SHA256 !trunc, padlen=15
depends_on:23:13
22:exp:44:exp:39:int:0:int:15
Decrypt CBC !EtM, ARIA SHA256 !trunc, padlen=255
depends_on:23:13
22:exp:44:exp:39:int:0:int:255
Decrypt CBC !EtM, ARIA SHA256 trunc, padlen=15
depends_on:23:13
22:exp:44:exp:39:int:1:int:15
Decrypt CBC !EtM, ARIA SHA256 trunc, padlen=255
depends_on:23:13
22:exp:44:exp:39:int:1:int:255
Decrypt CBC !EtM, ARIA SHA384 !trunc, empty plaintext, minpad
depends_on:23:7:8
22:exp:44:exp:38:int:0:exp:36
Decrypt CBC !EtM, ARIA SHA384 !trunc, empty plaintext, maxpad
depends_on:23:7:8
22:exp:44:exp:38:int:0:exp:67
Decrypt CBC !EtM, ARIA SHA384 trunc, empty plaintext, minpad
depends_on:23:7:8
22:exp:44:exp:38:int:1:exp:36
Decrypt CBC !EtM, ARIA SHA384 trunc, empty plaintext, maxpad
depends_on:23:7:8
22:exp:44:exp:38:int:1:exp:67
Decrypt CBC !EtM, ARIA SHA384 !trunc, padlen=0
depends_on:23:7:8
22:exp:44:exp:38:int:0:int:0
Decrypt CBC !EtM, ARIA SHA384 !trunc, padlen=240
depends_on:23:7:8
22:exp:44:exp:38:int:0:int:240
Decrypt CBC !EtM, ARIA SHA384 trunc, padlen=0
depends_on:23:7:8
22:exp:44:exp:38:int:1:int:0
Decrypt CBC !EtM, ARIA SHA384 trunc, padlen=240
depends_on:23:7:8
22:exp:44:exp:38:int:1:int:240
Decrypt CBC !EtM, ARIA SHA384 !trunc, padlen=1
depends_on:23:7:8
22:exp:44:exp:38:int:0:int:1
Decrypt CBC !EtM, ARIA SHA384 !trunc, padlen=241
depends_on:23:7:8
22:exp:44:exp:38:int:0:int:241
Decrypt CBC !EtM, ARIA SHA384 trunc, padlen=1
depends_on:23:7:8
22:exp:44:exp:38:int:1:int:1
Decrypt CBC !EtM, ARIA SHA384 trunc, padlen=241
depends_on:23:7:8
22:exp:44:exp:38:int:1:int:241
Decrypt CBC !EtM, ARIA SHA384 !trunc, padlen=15
depends_on:23:7:8
22:exp:44:exp:38:int:0:int:15
Decrypt CBC !EtM, ARIA SHA384 !trunc, padlen=255
depends_on:23:7:8
22:exp:44:exp:38:int:0:int:255
Decrypt CBC !EtM, ARIA SHA384 trunc, padlen=15
depends_on:23:7:8
22:exp:44:exp:38:int:1:int:15
Decrypt CBC !EtM, ARIA SHA384 trunc, padlen=255
depends_on:23:7:8
22:exp:44:exp:38:int:1:int:255
Decrypt CBC !EtM, CAMELLIA MD5 !trunc, empty plaintext, minpad
depends_on:16:22
22:exp:47:exp:41:int:0:exp:36
Decrypt CBC !EtM, CAMELLIA MD5 !trunc, empty plaintext, maxpad
depends_on:16:22
22:exp:47:exp:41:int:0:exp:67
Decrypt CBC !EtM, CAMELLIA MD5 trunc, empty plaintext, minpad
depends_on:16:22
22:exp:47:exp:41:int:1:exp:36
Decrypt CBC !EtM, CAMELLIA MD5 trunc, empty plaintext, maxpad
depends_on:16:22
22:exp:47:exp:41:int:1:exp:67
Decrypt CBC !EtM, CAMELLIA MD5 !trunc, padlen=0
depends_on:16:22
22:exp:47:exp:41:int:0:int:0
Decrypt CBC !EtM, CAMELLIA MD5 !trunc, padlen=240
depends_on:16:22
22:exp:47:exp:41:int:0:int:240
Decrypt CBC !EtM, CAMELLIA MD5 trunc, padlen=0
depends_on:16:22
22:exp:47:exp:41:int:1:int:0
Decrypt CBC !EtM, CAMELLIA MD5 trunc, padlen=240
depends_on:16:22
22:exp:47:exp:41:int:1:int:240
Decrypt CBC !EtM, CAMELLIA MD5 !trunc, padlen=1
depends_on:16:22
22:exp:47:exp:41:int:0:int:1
Decrypt CBC !EtM, CAMELLIA MD5 !trunc, padlen=241
depends_on:16:22
22:exp:47:exp:41:int:0:int:241
Decrypt CBC !EtM, CAMELLIA MD5 trunc, padlen=1
depends_on:16:22
22:exp:47:exp:41:int:1:int:1
Decrypt CBC !EtM, CAMELLIA MD5 trunc, padlen=241
depends_on:16:22
22:exp:47:exp:41:int:1:int:241
Decrypt CBC !EtM, CAMELLIA MD5 !trunc, padlen=15
depends_on:16:22
22:exp:47:exp:41:int:0:int:15
Decrypt CBC !EtM, CAMELLIA MD5 !trunc, padlen=255
depends_on:16:22
22:exp:47:exp:41:int:0:int:255
Decrypt CBC !EtM, CAMELLIA MD5 trunc, padlen=15
depends_on:16:22
22:exp:47:exp:41:int:1:int:15
Decrypt CBC !EtM, CAMELLIA MD5 trunc, padlen=255
depends_on:16:22
22:exp:47:exp:41:int:1:int:255
Decrypt CBC !EtM, CAMELLIA SHA1 !trunc, empty plaintext, minpad
depends_on:16:21
22:exp:47:exp:40:int:0:exp:36
Decrypt CBC !EtM, CAMELLIA SHA1 !trunc, empty plaintext, maxpad
depends_on:16:21
22:exp:47:exp:40:int:0:exp:67
Decrypt CBC !EtM, CAMELLIA SHA1 trunc, empty plaintext, minpad
depends_on:16:21
22:exp:47:exp:40:int:1:exp:36
Decrypt CBC !EtM, CAMELLIA SHA1 trunc, empty plaintext, maxpad
depends_on:16:21
22:exp:47:exp:40:int:1:exp:67
Decrypt CBC !EtM, CAMELLIA SHA1 !trunc, padlen=0
depends_on:16:21
22:exp:47:exp:40:int:0:int:0
Decrypt CBC !EtM, CAMELLIA SHA1 !trunc, padlen=240
depends_on:16:21
22:exp:47:exp:40:int:0:int:240
Decrypt CBC !EtM, CAMELLIA SHA1 trunc, padlen=0
depends_on:16:21
22:exp:47:exp:40:int:1:int:0
Decrypt CBC !EtM, CAMELLIA SHA1 trunc, padlen=240
depends_on:16:21
22:exp:47:exp:40:int:1:int:240
Decrypt CBC !EtM, CAMELLIA SHA1 !trunc, padlen=1
depends_on:16:21
22:exp:47:exp:40:int:0:int:1
Decrypt CBC !EtM, CAMELLIA SHA1 !trunc, padlen=241
depends_on:16:21
22:exp:47:exp:40:int:0:int:241
Decrypt CBC !EtM, CAMELLIA SHA1 trunc, padlen=1
depends_on:16:21
22:exp:47:exp:40:int:1:int:1
Decrypt CBC !EtM, CAMELLIA SHA1 trunc, padlen=241
depends_on:16:21
22:exp:47:exp:40:int:1:int:241
Decrypt CBC !EtM, CAMELLIA SHA1 !trunc, padlen=15
depends_on:16:21
22:exp:47:exp:40:int:0:int:15
Decrypt CBC !EtM, CAMELLIA SHA1 !trunc, padlen=255
depends_on:16:21
22:exp:47:exp:40:int:0:int:255
Decrypt CBC !EtM, CAMELLIA SHA1 trunc, padlen=15
depends_on:16:21
22:exp:47:exp:40:int:1:int:15
Decrypt CBC !EtM, CAMELLIA SHA1 trunc, padlen=255
depends_on:16:21
22:exp:47:exp:40:int:1:int:255
Decrypt CBC !EtM, CAMELLIA SHA256 !trunc, empty plaintext, minpad
depends_on:16:13
22:exp:47:exp:39:int:0:exp:36
Decrypt CBC !EtM, CAMELLIA SHA256 !trunc, empty plaintext, maxpad
depends_on:16:13
22:exp:47:exp:39:int:0:exp:67
Decrypt CBC !EtM, CAMELLIA SHA256 trunc, empty plaintext, minpad
depends_on:16:13
22:exp:47:exp:39:int:1:exp:36
Decrypt CBC !EtM, CAMELLIA SHA256 trunc, empty plaintext, maxpad
depends_on:16:13
22:exp:47:exp:39:int:1:exp:67
Decrypt CBC !EtM, CAMELLIA SHA256 !trunc, padlen=0
depends_on:16:13
22:exp:47:exp:39:int:0:int:0
Decrypt CBC !EtM, CAMELLIA SHA256 !trunc, padlen=240
depends_on:16:13
22:exp:47:exp:39:int:0:int:240
Decrypt CBC !EtM, CAMELLIA SHA256 trunc, padlen=0
depends_on:16:13
22:exp:47:exp:39:int:1:int:0
Decrypt CBC !EtM, CAMELLIA SHA256 trunc, padlen=240
depends_on:16:13
22:exp:47:exp:39:int:1:int:240
Decrypt CBC !EtM, CAMELLIA SHA256 !trunc, padlen=1
depends_on:16:13
22:exp:47:exp:39:int:0:int:1
Decrypt CBC !EtM, CAMELLIA SHA256 !trunc, padlen=241
depends_on:16:13
22:exp:47:exp:39:int:0:int:241
Decrypt CBC !EtM, CAMELLIA SHA256 trunc, padlen=1
depends_on:16:13
22:exp:47:exp:39:int:1:int:1
Decrypt CBC !EtM, CAMELLIA SHA256 trunc, padlen=241
depends_on:16:13
22:exp:47:exp:39:int:1:int:241
Decrypt CBC !EtM, CAMELLIA SHA256 !trunc, padlen=15
depends_on:16:13
22:exp:47:exp:39:int:0:int:15
Decrypt CBC !EtM, CAMELLIA SHA256 !trunc, padlen=255
depends_on:16:13
22:exp:47:exp:39:int:0:int:255
Decrypt CBC !EtM, CAMELLIA SHA256 trunc, padlen=15
depends_on:16:13
22:exp:47:exp:39:int:1:int:15
Decrypt CBC !EtM, CAMELLIA SHA256 trunc, padlen=255
depends_on:16:13
22:exp:47:exp:39:int:1:int:255
Decrypt CBC !EtM, CAMELLIA SHA384 !trunc, empty plaintext, minpad
depends_on:16:7:8
22:exp:47:exp:38:int:0:exp:36
Decrypt CBC !EtM, CAMELLIA SHA384 !trunc, empty plaintext, maxpad
depends_on:16:7:8
22:exp:47:exp:38:int:0:exp:67
Decrypt CBC !EtM, CAMELLIA SHA384 trunc, empty plaintext, minpad
depends_on:16:7:8
22:exp:47:exp:38:int:1:exp:36
Decrypt CBC !EtM, CAMELLIA SHA384 trunc, empty plaintext, maxpad
depends_on:16:7:8
22:exp:47:exp:38:int:1:exp:67
Decrypt CBC !EtM, CAMELLIA SHA384 !trunc, padlen=0
depends_on:16:7:8
22:exp:47:exp:38:int:0:int:0
Decrypt CBC !EtM, CAMELLIA SHA384 !trunc, padlen=240
depends_on:16:7:8
22:exp:47:exp:38:int:0:int:240
Decrypt CBC !EtM, CAMELLIA SHA384 trunc, padlen=0
depends_on:16:7:8
22:exp:47:exp:38:int:1:int:0
Decrypt CBC !EtM, CAMELLIA SHA384 trunc, padlen=240
depends_on:16:7:8
22:exp:47:exp:38:int:1:int:240
Decrypt CBC !EtM, CAMELLIA SHA384 !trunc, padlen=1
depends_on:16:7:8
22:exp:47:exp:38:int:0:int:1
Decrypt CBC !EtM, CAMELLIA SHA384 !trunc, padlen=241
depends_on:16:7:8
22:exp:47:exp:38:int:0:int:241
Decrypt CBC !EtM, CAMELLIA SHA384 trunc, padlen=1
depends_on:16:7:8
22:exp:47:exp:38:int:1:int:1
Decrypt CBC !EtM, CAMELLIA SHA384 trunc, padlen=241
depends_on:16:7:8
22:exp:47:exp:38:int:1:int:241
Decrypt CBC !EtM, CAMELLIA SHA384 !trunc, padlen=15
depends_on:16:7:8
22:exp:47:exp:38:int:0:int:15
Decrypt CBC !EtM, CAMELLIA SHA384 !trunc, padlen=255
depends_on:16:7:8
22:exp:47:exp:38:int:0:int:255
Decrypt CBC !EtM, CAMELLIA SHA384 trunc, padlen=15
depends_on:16:7:8
22:exp:47:exp:38:int:1:int:15
Decrypt CBC !EtM, CAMELLIA SHA384 trunc, padlen=255
depends_on:16:7:8
22:exp:47:exp:38:int:1:int:255
Decrypt CBC !EtM, 3DES MD5 !trunc, empty plaintext, minpad
depends_on:29:22
22:exp:68:exp:41:int:0:exp:36
Decrypt CBC !EtM, 3DES MD5 !trunc, empty plaintext, maxpad
depends_on:29:22
22:exp:68:exp:41:int:0:exp:67
Decrypt CBC !EtM, 3DES MD5 trunc, empty plaintext, minpad
depends_on:29:22
22:exp:68:exp:41:int:1:exp:36
Decrypt CBC !EtM, 3DES MD5 trunc, empty plaintext, maxpad
depends_on:29:22
22:exp:68:exp:41:int:1:exp:67
Decrypt CBC !EtM, 3DES MD5 !trunc, padlen=0
depends_on:29:22
22:exp:68:exp:41:int:0:int:0
Decrypt CBC !EtM, 3DES MD5 !trunc, padlen=248
depends_on:29:22
22:exp:68:exp:41:int:0:int:248
Decrypt CBC !EtM, 3DES MD5 trunc, padlen=0
depends_on:29:22
22:exp:68:exp:41:int:1:int:0
Decrypt CBC !EtM, 3DES MD5 trunc, padlen=248
depends_on:29:22
22:exp:68:exp:41:int:1:int:248
Decrypt CBC !EtM, 3DES MD5 !trunc, padlen=1
depends_on:29:22
22:exp:68:exp:41:int:0:int:1
Decrypt CBC !EtM, 3DES MD5 !trunc, padlen=249
depends_on:29:22
22:exp:68:exp:41:int:0:int:249
Decrypt CBC !EtM, 3DES MD5 trunc, padlen=1
depends_on:29:22
22:exp:68:exp:41:int:1:int:1
Decrypt CBC !EtM, 3DES MD5 trunc, padlen=249
depends_on:29:22
22:exp:68:exp:41:int:1:int:249
Decrypt CBC !EtM, 3DES MD5 !trunc, padlen=7
depends_on:29:22
22:exp:68:exp:41:int:0:int:7
Decrypt CBC !EtM, 3DES MD5 !trunc, padlen=255
depends_on:29:22
22:exp:68:exp:41:int:0:int:255
Decrypt CBC !EtM, 3DES MD5 trunc, padlen=7
depends_on:29:22
22:exp:68:exp:41:int:1:int:7
Decrypt CBC !EtM, 3DES MD5 trunc, padlen=255
depends_on:29:22
22:exp:68:exp:41:int:1:int:255
Decrypt CBC !EtM, 3DES SHA1 !trunc, empty plaintext, minpad
depends_on:29:21
22:exp:68:exp:40:int:0:exp:36
Decrypt CBC !EtM, 3DES SHA1 !trunc, empty plaintext, maxpad
depends_on:29:21
22:exp:68:exp:40:int:0:exp:67
Decrypt CBC !EtM, 3DES SHA1 trunc, empty plaintext, minpad
depends_on:29:21
22:exp:68:exp:40:int:1:exp:36
Decrypt CBC !EtM, 3DES SHA1 trunc, empty plaintext, maxpad
depends_on:29:21
22:exp:68:exp:40:int:1:exp:67
Decrypt CBC !EtM, 3DES SHA1 !trunc, padlen=0
depends_on:29:21
22:exp:68:exp:40:int:0:int:0
Decrypt CBC !EtM, 3DES SHA1 !trunc, padlen=248
depends_on:29:21
22:exp:68:exp:40:int:0:int:248
Decrypt CBC !EtM, 3DES SHA1 trunc, padlen=0
depends_on:29:21
22:exp:68:exp:40:int:1:int:0
Decrypt CBC !EtM, 3DES SHA1 trunc, padlen=248
depends_on:29:21
22:exp:68:exp:40:int:1:int:248
Decrypt CBC !EtM, 3DES SHA1 !trunc, padlen=1
depends_on:29:21
22:exp:68:exp:40:int:0:int:1
Decrypt CBC !EtM, 3DES SHA1 !trunc, padlen=249
depends_on:29:21
22:exp:68:exp:40:int:0:int:249
Decrypt CBC !EtM, 3DES SHA1 trunc, padlen=1
depends_on:29:21
22:exp:68:exp:40:int:1:int:1
Decrypt CBC !EtM, 3DES SHA1 trunc, padlen=249
depends_on:29:21
22:exp:68:exp:40:int:1:int:249
Decrypt CBC !EtM, 3DES SHA1 !trunc, padlen=7
depends_on:29:21
22:exp:68:exp:40:int:0:int:7
Decrypt CBC !EtM, 3DES SHA1 !trunc, padlen=255
depends_on:29:21
22:exp:68:exp:40:int:0:int:255
Decrypt CBC !EtM, 3DES SHA1 trunc, padlen=7
depends_on:29:21
22:exp:68:exp:40:int:1:int:7
Decrypt CBC !EtM, 3DES SHA1 trunc, padlen=255
depends_on:29:21
22:exp:68:exp:40:int:1:int:255
Decrypt CBC !EtM, 3DES SHA256 !trunc, empty plaintext, minpad
depends_on:29:13
22:exp:68:exp:39:int:0:exp:36
Decrypt CBC !EtM, 3DES SHA256 !trunc, empty plaintext, maxpad
depends_on:29:13
22:exp:68:exp:39:int:0:exp:67
Decrypt CBC !EtM, 3DES SHA256 trunc, empty plaintext, minpad
depends_on:29:13
22:exp:68:exp:39:int:1:exp:36
Decrypt CBC !EtM, 3DES SHA256 trunc, empty plaintext, maxpad
depends_on:29:13
22:exp:68:exp:39:int:1:exp:67
Decrypt CBC !EtM, 3DES SHA256 !trunc, padlen=0
depends_on:29:13
22:exp:68:exp:39:int:0:int:0
Decrypt CBC !EtM, 3DES SHA256 !trunc, padlen=248
depends_on:29:13
22:exp:68:exp:39:int:0:int:248
Decrypt CBC !EtM, 3DES SHA256 trunc, padlen=0
depends_on:29:13
22:exp:68:exp:39:int:1:int:0
Decrypt CBC !EtM, 3DES SHA256 trunc, padlen=248
depends_on:29:13
22:exp:68:exp:39:int:1:int:248
Decrypt CBC !EtM, 3DES SHA256 !trunc, padlen=1
depends_on:29:13
22:exp:68:exp:39:int:0:int:1
Decrypt CBC !EtM, 3DES SHA256 !trunc, padlen=249
depends_on:29:13
22:exp:68:exp:39:int:0:int:249
Decrypt CBC !EtM, 3DES SHA256 trunc, padlen=1
depends_on:29:13
22:exp:68:exp:39:int:1:int:1
Decrypt CBC !EtM, 3DES SHA256 trunc, padlen=249
depends_on:29:13
22:exp:68:exp:39:int:1:int:249
Decrypt CBC !EtM, 3DES SHA256 !trunc, padlen=7
depends_on:29:13
22:exp:68:exp:39:int:0:int:7
Decrypt CBC !EtM, 3DES SHA256 !trunc, padlen=255
depends_on:29:13
22:exp:68:exp:39:int:0:int:255
Decrypt CBC !EtM, 3DES SHA256 trunc, padlen=7
depends_on:29:13
22:exp:68:exp:39:int:1:int:7
Decrypt CBC !EtM, 3DES SHA256 trunc, padlen=255
depends_on:29:13
22:exp:68:exp:39:int:1:int:255
Decrypt CBC !EtM, 3DES SHA384 !trunc, empty plaintext, minpad
depends_on:29:7:8
22:exp:68:exp:38:int:0:exp:36
Decrypt CBC !EtM, 3DES SHA384 !trunc, empty plaintext, maxpad
depends_on:29:7:8
22:exp:68:exp:38:int:0:exp:67
Decrypt CBC !EtM, 3DES SHA384 trunc, empty plaintext, minpad
depends_on:29:7:8
22:exp:68:exp:38:int:1:exp:36
Decrypt CBC !EtM, 3DES SHA384 trunc, empty plaintext, maxpad
depends_on:29:7:8
22:exp:68:exp:38:int:1:exp:67
Decrypt CBC !EtM, 3DES SHA384 !trunc, padlen=0
depends_on:29:7:8
22:exp:68:exp:38:int:0:int:0
Decrypt CBC !EtM, 3DES SHA384 !trunc, padlen=248
depends_on:29:7:8
22:exp:68:exp:38:int:0:int:248
Decrypt CBC !EtM, 3DES SHA384 trunc, padlen=0
depends_on:29:7:8
22:exp:68:exp:38:int:1:int:0
Decrypt CBC !EtM, 3DES SHA384 trunc, padlen=248
depends_on:29:7:8
22:exp:68:exp:38:int:1:int:248
Decrypt CBC !EtM, 3DES SHA384 !trunc, padlen=1
depends_on:29:7:8
22:exp:68:exp:38:int:0:int:1
Decrypt CBC !EtM, 3DES SHA384 !trunc, padlen=249
depends_on:29:7:8
22:exp:68:exp:38:int:0:int:249
Decrypt CBC !EtM, 3DES SHA384 trunc, padlen=1
depends_on:29:7:8
22:exp:68:exp:38:int:1:int:1
Decrypt CBC !EtM, 3DES SHA384 trunc, padlen=249
depends_on:29:7:8
22:exp:68:exp:38:int:1:int:249
Decrypt CBC !EtM, 3DES SHA384 !trunc, padlen=7
depends_on:29:7:8
22:exp:68:exp:38:int:0:int:7
Decrypt CBC !EtM, 3DES SHA384 !trunc, padlen=255
depends_on:29:7:8
22:exp:68:exp:38:int:0:int:255
Decrypt CBC !EtM, 3DES SHA384 trunc, padlen=7
depends_on:29:7:8
22:exp:68:exp:38:int:1:int:7
Decrypt CBC !EtM, 3DES SHA384 trunc, padlen=255
depends_on:29:7:8
22:exp:68:exp:38:int:1:int:255
SSL TLS 1.3 Key schedule: Secret evolution #1
depends_on:25
26:exp:39:hex:"":hex:"":hex:"33ad0a1c607ec03b09e6cd9893680ce210adf300aa1f2660e1b22e10f170f92a"
SSL TLS 1.3 Key schedule: Secret evolution #2
26:exp:39:hex:"33ad0a1c607ec03b09e6cd9893680ce210adf300aa1f2660e1b22e10f170f92a":hex:"df4a291baa1eb7cfa6934b29b474baad2697e29f1f920dcc77c8a0a088447624":hex:"fb9fc80689b3a5d02c33243bf69a1b1b20705588a794304a6e7120155edf149a"
SSL TLS 1.3 Key schedule: Secret evolution #3
26:exp:39:hex:"fb9fc80689b3a5d02c33243bf69a1b1b20705588a794304a6e7120155edf149a":hex:"":hex:"7f2882bb9b9a46265941653e9c2f19067118151e21d12e57a7b6aca1f8150c8d"
SSL TLS 1.3 Key schedule: HKDF Expand Label #1
23:exp:39:hex:"a2067265e7f0652a923d5d72ab0467c46132eeb968b6a32d311c805868548814":exp:69:hex:"":int:16:hex:"844780a7acad9f980fa25c114e43402a"
SSL TLS 1.3 Key schedule: HKDF Expand Label #2
23:exp:39:hex:"a2067265e7f0652a923d5d72ab0467c46132eeb968b6a32d311c805868548814":exp:70:hex:"":int:12:hex:"4c042ddc120a38d1417fc815"
SSL TLS 1.3 Key schedule: HKDF Expand Label #3
23:exp:39:hex:"ff0e5b965291c608c1e8cd267eefc0afcc5e98a2786373f0db47b04786d72aea":exp:69:hex:"":int:16:hex:"7154f314e6be7dc008df2c832baa1d39"
SSL TLS 1.3 Key schedule: HKDF Expand Label #4
23:exp:39:hex:"ff0e5b965291c608c1e8cd267eefc0afcc5e98a2786373f0db47b04786d72aea":exp:70:hex:"":int:12:hex:"71abc2cae4c699d47c600268"
SSL TLS 1.3 Key schedule: HKDF Expand Label #5 (RFC 8448)
23:exp:39:hex:"b67b7d690cc16c4e75e54213cb2d37b4e9c912bcded9105d42befd59d391ad38":exp:70:hex:"":int:12:hex:"5d313eb2671276ee13000b30"
SSL TLS 1.3 Key schedule: HKDF Expand Label #6 (RFC 8448)
23:exp:39:hex:"b67b7d690cc16c4e75e54213cb2d37b4e9c912bcded9105d42befd59d391ad38":exp:69:hex:"":int:16:hex:"3fce516009c21727d0f2e4e86ee403bc"
SSL TLS 1.3 Key schedule: HKDF Expand Label #7 (RFC 8448)
23:exp:39:hex:"b3eddb126e067f35a780b3abf45e2d8f3b1a950738f52e9600746a0e27a55a21":exp:70:hex:"":int:12:hex:"5bd3c71b836e0b76bb73265f"
SSL TLS 1.3 Key schedule: HKDF Expand Label #8 (RFC 8448)
23:exp:39:hex:"b3eddb126e067f35a780b3abf45e2d8f3b1a950738f52e9600746a0e27a55a21":exp:69:hex:"":int:16:hex:"dbfaa693d1762c5b666af5d950258d01"
SSL TLS 1.3 Key schedule: HKDF Expand Label #9 (RFC 8448)
23:exp:39:hex:"2faac08f851d35fea3604fcb4de82dc62c9b164a70974d0462e27f1ab278700f":exp:71:hex:"":int:32:hex:"5ace394c26980d581243f627d1150ae27e37fa52364e0a7f20ac686d09cd0e8e"
SSL TLS 1.3 Key schedule: HKDF Expand Label #10 (RFC 8448)
23:exp:39:hex:"7df235f2031d2a051287d02b0241b0bfdaf86cc856231f2d5aba46c434ec196c":exp:72:hex:"0000":int:32:hex:"4ecd0eb6ec3b4d87f5d6028f922ca4c5851a277fd41311c9e62d2c9492e1c4f3"
SSL TLS 1.3 Key schedule: Traffic key generation #1
24:exp:39:hex:"a2067265e7f0652a923d5d72ab0467c46132eeb968b6a32d311c805868548814":hex:"ff0e5b965291c608c1e8cd267eefc0afcc5e98a2786373f0db47b04786d72aea":int:12:int:16:hex:"844780a7acad9f980fa25c114e43402a":hex:"4c042ddc120a38d1417fc815":hex:"7154f314e6be7dc008df2c832baa1d39":hex:"71abc2cae4c699d47c600268"
SSL TLS 1.3 Key schedule: Traffic key generation #2 (RFC 8448)
24:exp:39:hex:"a2067265e7f0652a923d5d72ab0467c46132eeb968b6a32d311c805868548814":hex:"ff0e5b965291c608c1e8cd267eefc0afcc5e98a2786373f0db47b04786d72aea":int:12:int:16:hex:"844780a7acad9f980fa25c114e43402a":hex:"4c042ddc120a38d1417fc815":hex:"7154f314e6be7dc008df2c832baa1d39":hex:"71abc2cae4c699d47c600268"
SSL TLS 1.3 Key schedule: Derive-Secret( ., "derived", "")
25:exp:39:hex:"33ad0a1c607ec03b09e6cd9893680ce210adf300aa1f2660e1b22e10f170f92a":exp:73:hex:"":int:32:exp:74:hex:"6f2615a108c702c5678f54fc9dbab69716c076189c48250cebeac3576c3611ba"
SSL TLS 1.3 Key schedule: Derive-Secret( ., "s ap traffic", hash) #1
25:exp:39:hex:"7f2882bb9b9a46265941653e9c2f19067118151e21d12e57a7b6aca1f8150c8d":exp:75:hex:"22844b930e5e0a59a09d5ac35fc032fc91163b193874a265236e568077378d8b":int:32:exp:76:hex:"3fc35ea70693069a277956afa23b8f4543ce68ac595f2aace05cd7a1c92023d5"
SSL TLS 1.3 Key schedule: Derive-Secret( ., "c e traffic", hash)
25:exp:39:hex:"9b2188e9b2fc6d64d71dc329900e20bb41915000f678aa839cbb797cb7d8332c":exp:77:hex:"08ad0fa05d7c7233b1775ba2ff9f4c5b8b59276b7f227f13a976245f5d960913":int:32:exp:76:hex:"3fbbe6a60deb66c30a32795aba0eff7eaa10105586e7be5c09678d63b6caab62"
SSL TLS 1.3 Key schedule: Derive-Secret( ., "e exp master", hash)
25:exp:39:hex:"9b2188e9b2fc6d64d71dc329900e20bb41915000f678aa839cbb797cb7d8332c":exp:78:hex:"08ad0fa05d7c7233b1775ba2ff9f4c5b8b59276b7f227f13a976245f5d960913":int:32:exp:76:hex:"b2026866610937d7423e5be90862ccf24c0e6091186d34f812089ff5be2ef7df"
SSL TLS 1.3 Key schedule: Derive-Secret( ., "c hs traffic", hash)
25:exp:39:hex:"005cb112fd8eb4ccc623bb88a07c64b3ede1605363fc7d0df8c7ce4ff0fb4ae6":exp:79:hex:"f736cb34fe25e701551bee6fd24c1cc7102a7daf9405cb15d97aafe16f757d03":int:32:exp:76:hex:"2faac08f851d35fea3604fcb4de82dc62c9b164a70974d0462e27f1ab278700f"
SSL TLS 1.3 Key schedule: Derive-Secret( ., "s hs traffic", hash)
25:exp:39:hex:"005cb112fd8eb4ccc623bb88a07c64b3ede1605363fc7d0df8c7ce4ff0fb4ae6":exp:80:hex:"f736cb34fe25e701551bee6fd24c1cc7102a7daf9405cb15d97aafe16f757d03":int:32:exp:76:hex:"fe927ae271312e8bf0275b581c54eef020450dc4ecffaa05a1a35d27518e7803"
SSL TLS 1.3 Key schedule: Derive-Secret( ., "c ap traffic", hash)
25:exp:39:hex:"e2d32d4ed66dd37897a0e80c84107503ce58bf8aad4cb55a5002d77ecb890ece":exp:81:hex:"b0aeffc46a2cfe33114e6fd7d51f9f04b1ca3c497dab08934a774a9d9ad7dbf3":int:32:exp:76:hex:"2abbf2b8e381d23dbebe1dd2a7d16a8bf484cb4950d23fb7fb7fa8547062d9a1"
SSL TLS 1.3 Key schedule: Derive-Secret( ., "s ap traffic", hash) #2
25:exp:39:hex:"e2d32d4ed66dd37897a0e80c84107503ce58bf8aad4cb55a5002d77ecb890ece":exp:75:hex:"b0aeffc46a2cfe33114e6fd7d51f9f04b1ca3c497dab08934a774a9d9ad7dbf3":int:32:exp:76:hex:"cc21f1bf8feb7dd5fa505bd9c4b468a9984d554a993dc49e6d285598fb672691"
SSL TLS 1.3 Key schedule: Derive-Secret( ., "exp master", hash)
25:exp:39:hex:"e2d32d4ed66dd37897a0e80c84107503ce58bf8aad4cb55a5002d77ecb890ece":exp:82:hex:"b0aeffc46a2cfe33114e6fd7d51f9f04b1ca3c497dab08934a774a9d9ad7dbf3":int:32:exp:76:hex:"3fd93d4ffddc98e64b14dd107aedf8ee4add23f4510f58a4592d0b201bee56b4"
SSL TLS 1.3 Key schedule: Derive-Secret( ., "res master", hash)
25:exp:39:hex:"e2d32d4ed66dd37897a0e80c84107503ce58bf8aad4cb55a5002d77ecb890ece":exp:83:hex:"c3c122e0bd907a4a3ff6112d8fd53dbf89c773d9552e8b6b9d56d361b3a97bf6":int:32:exp:76:hex:"5e95bdf1f89005ea2e9aa0ba85e728e3c19c5fe0c699e3f5bee59faebd0b5406"
SSL TLS_PRF MBEDTLS_SSL_TLS_PRF_NONE
27:exp:84:hex:"":hex:"":char*:"test tls_prf label":hex:"":exp:85
SSL TLS_PRF MBEDTLS_SSL_TLS_PRF_SSL3
depends_on:0
27:exp:86:hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":char*:"test tls_prf label":hex:"3ff3d192aa599255339def5a9723444a":int:0
SSL TLS_PRF MBEDTLS_SSL_TLS_PRF_TLS1 TLS 1.0 enabled
depends_on:3
27:exp:87:hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":char*:"test tls_prf label":hex:"8defca540d41d4c79d390027295bb4e6":int:0
SSL TLS_PRF MBEDTLS_SSL_TLS_PRF_TLS1 TLS 1.1 enabled
depends_on:5
27:exp:87:hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":char*:"test tls_prf label":hex:"8defca540d41d4c79d390027295bb4e6":int:0
SSL TLS_PRF MBEDTLS_SSL_TLS_PRF_SHA384
depends_on:7:8:6
27:exp:88:hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":char*:"test tls_prf label":hex:"a4206a36eef93f496611c2b7806625c3":int:0
SSL TLS_PRF MBEDTLS_SSL_TLS_PRF_SHA256
depends_on:13:6
27:exp:89:hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":char*:"test tls_prf label":hex:"7f9998393198a02c8d731ccc2ef90b2c":int:0
SSL TLS_PRF MBEDTLS_SSL_TLS_PRF_SSL3 not enabled
depends_on:30
27:exp:86:hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":char*:"test tls_prf label":hex:"3ff3d192aa599255339def5a9723444a":exp:85
SSL TLS_PRF MBEDTLS_SSL_TLS_PRF_TLS1 TLS 1.X not enabled
depends_on:31:32
27:exp:87:hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":char*:"test tls_prf label":hex:"8defca540d41d4c79d390027295bb4e6":exp:85
SSL TLS_PRF MBEDTLS_SSL_TLS_PRF_SHA384 SHA-512 not enabled
depends_on:33
27:exp:88:hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":char*:"test tls_prf label":hex:"a4206a36eef93f496611c2b7806625c3":exp:85
SSL TLS_PRF MBEDTLS_SSL_TLS_PRF_SHA256 SHA-256 not enabled
depends_on:34
27:exp:89:hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":hex:"1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef":char*:"test tls_prf label":hex:"7f9998393198a02c8d731ccc2ef90b2c":exp:85
Session serialization, save-load: no ticket, no cert
28:int:0:char*:""
Session serialization, save-load: small ticket, no cert
depends_on:35:36
28:int:42:char*:""
Session serialization, save-load: large ticket, no cert
depends_on:35:36
28:int:1023:char*:""
Session serialization, save-load: no ticket, cert
depends_on:37:38:14:15:13:39
28:int:0:char*:"zip:third_party/mbedtls/test/data/server5.crt"
Session serialization, save-load: small ticket, cert
depends_on:35:36:37:38:14:15:13:39
28:int:42:char*:"zip:third_party/mbedtls/test/data/server5.crt"
Session serialization, save-load: large ticket, cert
depends_on:35:36:37:38:14:15:13:39
28:int:1023:char*:"zip:third_party/mbedtls/test/data/server5.crt"
Session serialization, load-save: no ticket, no cert
29:int:0:char*:""
Session serialization, load-save: small ticket, no cert
depends_on:35:36
29:int:42:char*:""
Session serialization, load-save: large ticket, no cert
depends_on:35:36
29:int:1023:char*:""
Session serialization, load-save: no ticket, cert
depends_on:37:38:14:15:13:39
29:int:0:char*:"zip:third_party/mbedtls/test/data/server5.crt"
Session serialization, load-save: small ticket, cert
depends_on:35:36:37:38:14:15:13:39
29:int:42:char*:"zip:third_party/mbedtls/test/data/server5.crt"
Session serialization, load-save: large ticket, cert
depends_on:35:36:37:38:14:15:13:39
29:int:1023:char*:"zip:third_party/mbedtls/test/data/server5.crt"
Session serialization, save buffer size: no ticket, no cert
30:int:0:char*:""
Session serialization, save buffer size: small ticket, no cert
depends_on:35:36
30:int:42:char*:""
Session serialization, save buffer size: large ticket, no cert
depends_on:35:36
30:int:1023:char*:""
Session serialization, save buffer size: no ticket, cert
depends_on:37:38:14:15:13:39
30:int:0:char*:"zip:third_party/mbedtls/test/data/server5.crt"
Session serialization, save buffer size: small ticket, cert
depends_on:35:36:37:38:14:15:13:39
30:int:42:char*:"zip:third_party/mbedtls/test/data/server5.crt"
Session serialization, save buffer size: large ticket, cert
depends_on:35:36:37:38:14:15:13:39
30:int:1023:char*:"zip:third_party/mbedtls/test/data/server5.crt"
Session serialization, load buffer size: no ticket, no cert
31:int:0:char*:""
Session serialization, load buffer size: small ticket, no cert
depends_on:35:36
31:int:42:char*:""
Session serialization, load buffer size: large ticket, no cert
depends_on:35:36
31:int:1023:char*:""
Session serialization, load buffer size: no ticket, cert
depends_on:37:38:14:15:13:39
31:int:0:char*:"zip:third_party/mbedtls/test/data/server5.crt"
Session serialization, load buffer size: small ticket, cert
depends_on:35:36:37:38:14:15:13:39
31:int:42:char*:"zip:third_party/mbedtls/test/data/server5.crt"
Session serialization, load buffer size: large ticket, cert
depends_on:35:36:37:38:14:15:13:39
31:int:1023:char*:"zip:third_party/mbedtls/test/data/server5.crt"
Constant-flow HMAC: MD5
depends_on:22
47:exp:41
Constant-flow HMAC: SHA1
depends_on:21
47:exp:40
Constant-flow HMAC: SHA256
depends_on:13
47:exp:39
Constant-flow HMAC: SHA384
depends_on:7:8
47:exp:38
Constant-flow memcpy from offset: small
48:int:0:int:5:int:10
Constant-flow memcpy from offset: medium
48:int:0:int:255:int:32
Constant-flow memcpy from offset: large
48:int:100:int:339:int:48