Re: [openssl-users] Problem in installing gem puma

2015-08-19 Thread Venkataraman Srinivasan
Thank you Michael Wojcik On 19-Aug-15 7:25 PM, Michael Wojcik wrote: This is not an OpenSSL issue; it's an autoconf one. From your installation log: - "gcc -o conftest.exe -IC:/Ruby21/include/ruby-2.1.0/i386-mingw32 -IC:/Ruby21/include/ruby-2.1.0/ruby/backward -IC:/Ruby21/include/ruby-2.

[openssl-users] The manpages are on the website now

2015-08-19 Thread Salz, Rich
As a new feature, all releases are now online, including master. There is still some links broken. We could use some Perl hacking help. If you know how to add "-podpath" searching into Pod::XHTML, please get in touch. -- Senior Architect, Akamai Technologies IM: richs...@jabber.at Twitter: Ric

Re: [openssl-users] BEAST and SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS

2015-08-19 Thread Jakob Bohm
On 19/08/2015 16:37, Salz, Rich wrote: Try this as a starting point: https://security.ias.edu/poodle-and-beast-isnt-love-story-sslv3-cipher-vulnerability ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-us

Re: [openssl-users] Problem in installing gem puma

2015-08-19 Thread Michael Wojcik
This is not an OpenSSL issue; it's an autoconf one. >From your installation log: - "gcc -o conftest.exe -IC:/Ruby21/include/ruby-2.1.0/i386-mingw32 -IC:/Ruby21/include/ruby-2.1.0/ruby/backward -IC:/Ruby21/include/ruby-2.1.0 -I. -DFD_SETSIZE=2048 -D_WIN32_WINNT=0x0501 -D__MINGW_USE_VC2005_CO

Re: [openssl-users] BEAST and SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS

2015-08-19 Thread Salz, Rich
Try this as a starting point: https://security.ias.edu/poodle-and-beast-isnt-love-story-sslv3-cipher-vulnerability ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] BEAST and SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS

2015-08-19 Thread Salz, Rich
> What about 3DES with appropriate IV, downgrade and replay > countermeasures, what exactly is wrong with those ciphers that is beyond > salvage?(By salvage I mean significantly better than plain text when talking > to > clients that don't support anything more modern, such as certain Microsoft >

Re: [openssl-users] BEAST and SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS

2015-08-19 Thread jonetsu
Thanks for your comments - much appreciated. What is exactly the "poodle patch" and how doe sit come into providing some form of protection against the BEAST attack ? -- View this message in context: http://openssl.6102.n7.nabble.com/BEAST-and-SSL-OP-DONT-INSERT-EMPTY-FRAGMENTS-tp59291p59743.

[openssl-users] Problem in installing gem puma

2015-08-19 Thread V Srinivasan
Dear All, I am using Windows 7 ruby version :: ruby 2.1.6p336 (2015-04-13 revision 50298) [i386-mingw32] gem version :: 2.2.3 I have a problem in installing gem puma |PS C:\Users\VSrinivasan\mystuff\SampleApp> gem install puma Temporarily enhancing PATH to include DevKit... Building nativ

Re: [openssl-users] BEAST and SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS

2015-08-19 Thread Jakob Bohm
On 19/08/2015 00:26, Salz, Rich wrote: There are *no* secure SSLv3 ciphers. If you need to support it (for legacy clients), then best you can do is use the "poodle patch," the SCSV indicator which will at least prevents clients that are capable of more from being downgraded. What about 3DES