search for: aynth

...? >> >> It seems that if ssl_cipher_list is defined, >> ssl_protocols = !SSLv2 !SSLv3 >> >> results in TLS1.2 being the only one active, but if it is defined, 1.0, >> 1.1, and 1.2 are all active? > > ssl_protocols = !SSLv2 !SSLv3 > > and you are fine, aynthing else is nonsense because when TLSv1.3 will be > released you go to each and every server to add it to the config? likely > not! Configuration management. :) Also, no, you need to do more than just disable SSLv3. You need to disable several cipher groups allowed in TLSv1.0 and TLSv1.1,...

On Mon, Dec 01, 2014 at 09:27:48PM -0800, Darren Pilgrim wrote: > On 12/1/2014 4:43 PM, Will Yardley wrote: > > Can you use both ssl_protocols *and* ssl_cipher_list in the same config > > (in a way that's sane)? > > > Is there a way to exclude these ciphers, while still keeping my config > > easy to parse and avoiding duplicative or deprecated configs? > >

...uldn't !SSLv2 and !SSLv3 be sufficient? > > It seems that if ssl_cipher_list is defined, > ssl_protocols = !SSLv2 !SSLv3 > > results in TLS1.2 being the only one active, but if it is defined, 1.0, > 1.1, and 1.2 are all active? ssl_protocols = !SSLv2 !SSLv3 and you are fine, aynthing else is nonsense because when TLSv1.3 will be released you go to each and every server to add it to the config? likely not! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital s...

...t if ssl_cipher_list is defined, >>> ssl_protocols = !SSLv2 !SSLv3 >>> >>> results in TLS1.2 being the only one active, but if it is defined, 1.0, >>> 1.1, and 1.2 are all active? >> >> ssl_protocols = !SSLv2 !SSLv3 >> >> and you are fine, aynthing else is nonsense because when TLSv1.3 will be >> released you go to each and every server to add it to the config? likely >> not! > > Configuration management. :) mis-management is the right word for disable future procotols > Also, no, you need to do more than just disabl...

Hi All, I am using convert() function in RTAQ package to convert the text file into xts object.The code I am using is shown below: convert(from="2010-07-01",to="2010-07-01",datasource="C:\\TAQdata",datadestination="C:\\datadestination",trades=T,quotes=F,ticker="SUBX",dir=F) The problem is that I am not getting the text files named Ticker.trades

I'm thinking of migrating from 1.1.7 (default RPM on SUSE 11.1) to 2.0.6 compiled from source using the default locations. Any Gotchas to expect that are different to an upgrade from 1.2? Any hints from moving from RPM to compiling from source and retaining the default configuration under /usr/local? TIA -- Brian Duffell RiscPC600 | VRPC Sa-Adjust RISC OS 6.10 96Mb Linux PCs