search for: tmraz

...8e. You weren't clear which version you > upgraded from, but you mentioned testing against openssl-0.9.8e-27.el5_10.1 > (from March 2014, nevertheless), which works. > > I would hazard a guess that this is the change causing your problem. > > * Fri Jun 26 2015 Tomas Mraz <tmraz at redhat.com> 0.9.8e-36 > - also change the default DH parameters in s_server to 1024 bits > > Here's some more info, > > https://www.openssl.org/blog/blog/2015/05/20/logjam-freak-upcoming-changes/ > > RH must have backported this fix to 0.9.8e. > > There seem...

In article <55D2ED32.6040000 at hogranch.com>, John R Pierce <pierce at hogranch.com> wrote: > On 8/18/2015 1:27 AM, Tony Mountifield wrote: > >> You should now be using mysql55 on CentOS-5, not mysql-5.0 > > That may well be the case, but isn't relevant to the point I'm making, > > which is that something changed in openssl-0.9.8e-36 that has broken

....2 on the > command line, else I suspect you could recompile the source RPM, > removing patches if required. Hello Tom, It's indeed an interesting way. I didn't think about something just disabled. I browsed, gnutls rpm changelog and I saw this : * Thu May 3 2012 Tomas Mraz <tmraz at redhat.com> 2.8.5-7 - more TLS-1.2 compatibility fixes (TLS-1.2 stays disabled by default) So TLS 1.2 seems there but disabled by default : So maybe lftp can't use it because it can't force it. I tried browsing the code and RPM patches but I was unable to find where this disable thi...

Note: I am digest subscriber so if you could copy me directly on any reply to the list I would appreciate it very much. I sent this to the OpenSSH list (secureshell at securityfocus.com) yesterday and received no response so I am asking here in hopes that someone else has run across this problem on CentOS. We have encountered a situation that requires sftp access to one of our server by an

Hello Team, We ship our own software own top of Centos 5.2 OS and install other applications and rpms on top of rpms available in 5.2 Centos. We are in the process of upgrading to a later version of openssh (5.8 version of openssh is already available), however the latest src.rpm version of openssh available on Centos site is still

...-q --changelog openssl-0.9.8e. You weren't clear which version you upgraded from, but you mentioned testing against openssl-0.9.8e-27.el5_10.1 (from March 2014, nevertheless), which works. I would hazard a guess that this is the change causing your problem. * Fri Jun 26 2015 Tomas Mraz <tmraz at redhat.com> 0.9.8e-36 - also change the default DH parameters in s_server to 1024 bits Here's some more info, https://www.openssl.org/blog/blog/2015/05/20/logjam-freak-upcoming-changes/ RH must have backported this fix to 0.9.8e. There seem to be many reports out there that the op...

On Tue, Aug 02, 2016 at 02:56:26PM +0000, Olivier BONHOMME wrote: > Hello Tom, > > It's indeed an interesting way. I didn't think about something just disabled. I > browsed, gnutls rpm changelog and I saw this : > > * Thu May 3 2012 Tomas Mraz <tmraz at redhat.com> 2.8.5-7 > - more TLS-1.2 compatibility fixes (TLS-1.2 stays disabled by default) > > So TLS 1.2 seems there but disabled by default : So maybe lftp can't use it > because it can't force it. > > I tried browsing the code and RPM patches but I was unable...

Hello everybody, I am writing on that mailing list because I have an issue using lftp and I would love to have more infos about features available on the LFTP version provided by CentOS 6. I try to connect to a ftp server in secured mode using FTPS explicit and I would love to use TLSv1.2. After several tries, I understood that the TLS negociation was not possible using TLSv1.2 (It works only

On 2019-10-09 14:58, Jonathan Billings wrote: > On Wed, Oct 09, 2019 at 02:47:19PM -0500, Valeri Galtsev wrote: >> Could someone enlighten me about the following file: >> >> /etc/subuid >> >> ? This file appears to be owned by "setup" package. This is CentOS 7 system, >> and until now these files if existed were never changed. Today I have added

...s larger than 64 GiB to die with a cipher_crypt: EVP_Cipher failed error. The check implementing this limit has been recently rolled back by Red Hat: https://rhn.redhat.com/errata/RHBA-2015-0772.html The reason for dropping it is stated in the package's ChangeLog: Thu Mar 26 2015 Tom?? Mr?z tmraz at redhat.com 1.0.1e-30.8 drop the AES-GCM restriction of 2^32 operations because the IV is always 96 bits (32 bit fixed field + 64 bit invocation field) According to our own analysis, the change does not remove an operations count restriction (specified in Sec 8.3 of NIST SP 800-38D and dependent...