Re: [Ledger-smb-users] My Assessment of the Heartbleed OpenSSL bug and LedgerSMB

2014-04-11 Thread Chris Travers
On Fri, Apr 11, 2014 at 4:37 PM, Rich Shepard wrote: > On Fri, 11 Apr 2014, Richard Hector wrote: > > > Heartbleed isn't a problem with the encryption though; the encryption > > didn't get broken. Any protocol could probably potentially suffer from a > > buffer overflow due to a bug in the softwar

Re: [Ledger-smb-users] My Assessment of the Heartbleed OpenSSL bug and LedgerSMB

2014-04-11 Thread Rich Shepard
On Fri, 11 Apr 2014, Richard Hector wrote: > Heartbleed isn't a problem with the encryption though; the encryption > didn't get broken. Any protocol could probably potentially suffer from a > buffer overflow due to a bug in the software. Given this one leaked info > from the server process, who's

Re: [Ledger-smb-users] My Assessment of the Heartbleed OpenSSL bug and LedgerSMB

2014-04-11 Thread ario
On Fri, 11 Apr 2014 19:15:00 +1200 Richard Hector wrote: > On 11/04/14 09:41, ario wrote: > > On Thu, 10 Apr 2014 19:04:27 +0200 > > Pongrácz István wrote: > > > >> > What if they implemented this "feature" to be able to get > >> > information without trace? : > > Then they would have succ

Re: [Ledger-smb-users] My Assessment of the Heartbleed OpenSSL bug and LedgerSMB

2014-04-11 Thread Richard Hector
On 11/04/14 09:41, ario wrote: > On Thu, 10 Apr 2014 19:04:27 +0200 > Pongrácz István wrote: > >> > What if they implemented this "feature" to be able to get information >> > without trace? : > Then they would have succeeded spectacularly with us thinking "there is > a bug" in OpenSSL. > >