stouset (Stephen Touset)
- Login: stouset
- Email: stephen@touset.org
- Registered on: 04/01/2010
- Last sign in: 10/14/2014
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 3 | 3 |
Activity
10/14/2014
-
09:13 PM Ruby Bug #9424: ruby 1.9 & 2.x has insecure SSL/TLS client defaults
- This patch looks broken.
:options => -> {
opts = …
opts |= OpenSSL::SSL::OP_NO_SSLv3 if defined?(OpenSSL::SSL::OP_NO_SSLv3)
}.call
If that last constant isn't defined, the lambda will return nil and no options will be ov...
04/18/2014
-
08:47 PM Ruby Feature #9758 (Closed): Allow setting SSLContext#extra_chain_cert in Net::HTTP
- Currently, `Net::HTTP` can only send a single SSL certificate when it
establishes a connection. Some use-cases involve sending an entire
certificate chain to the destination; for this, `SSLContext` supports
assigning to `#extra_chain_...
10/25/2012
-
08:27 AM Ruby Feature #6980: OpenSSL support for AEAD additional authenticated data and tags
- I take it given the recent feature freeze that this will *not* make it into 2.0?
09/05/2012
-
07:39 AM Ruby Feature #6980: OpenSSL support for AEAD additional authenticated data and tags
- =begin
I'm not necessarily happy with a GCM-specific (({gcm_tag})), and an (unimplemented but hypothetical) (({ccm_tag})) et al. But having a single (({tag})) method that probed for which mode it was currently in seemed too magical. I'm ... -
04:14 AM Ruby Feature #6980: OpenSSL support for AEAD additional authenticated data and tags
- Sorry, patch included unintentional whitespace changes. Reuploaded without whitespace changes.
-
04:11 AM Ruby Feature #6980 (Closed): OpenSSL support for AEAD additional authenticated data and tags
- =begin
I've added support to OpenSSL::Cipher to support AEAD modes of operation. AEAD modes allow for plaintext additional authentication data to be combined with a ciphertext to generate a "tag" (e.g., a MAC). This tag can then be veri...
12/01/2011
-
11:14 PM Ruby Feature #5653: "I strongly discourage the use of autoload in any standard libraries" (Re: autoload will be dead)
- =begin
After discussion last night with Yehuda, we both agreed that this issue isn't resolved by #2740. Since (({const_missing})) is never called when Ruby resolves a constant like (({Foo::Bar})) to (({Object::Bar})), it cannot be used ... -
10:34 AM Ruby Feature #5653: "I strongly discourage the use of autoload in any standard libraries" (Re: autoload will be dead)
- =begin
@ThomasSawyer That kind of approach falls apart when you have multiple entry points into your library that require various features.
I've long considered it (perhaps incorrectly) a best practice to organize my hierarchy as thi... -
10:16 AM Ruby Feature #5653: "I strongly discourage the use of autoload in any standard libraries" (Re: autoload will be dead)
- =begin
One thing to keep in mind is that (({const_missing})) *cannot* be used to replicate (({autoload})) currently due to Ruby cascading constant lookup to the Object namespace. Example:
>> class Foo; end
>> class Bar; end
...
07/10/2010
-
06:48 AM Ruby Feature #3478: Excruciatingly slow pathname implementation
- =begin
I haven't forgot about fixing the implementation to support Windows. I had to move apartments earlier than expected, and haven't had the free time to add the necessary fixes.
=end