Bug#739596: tlsdate: Will be broken once the SSL handshake does not include timestamps anymore?

2014-02-20 Thread intrigeri
Package: tlsdate
Version: 0.0.5-2
Severity: normal

Hi,

my understanding is that tlsdate will be broken once Nick's proposal
is accepted, and SSL handshakes don't include timestamps anymore.

Is this correct?
If it is, is including tlsdate in a stable Debian release a good idea?

Cheers,
--
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#739596: tlsdate: Will be broken once the SSL handshake does not include timestamps anymore?

2014-02-20 Thread Jacob Appelbaum
That is incorrect.

tlsdate will continue to function, of course. There are already
non-compliant TLS servers that do not return time or return skewed
time. We attempt to compensate for that kind of server provided data
in a few different ways. There may also be new TLS servers that
implement Nick's TLS changes.

Furthermore, the next release of tlsdate to go into Debian will have
the added code (from Nick) to fetch the data/time via HTTP, not just
the SSL/TLS handshake data.

On 2/20/14, intrig...@debian.org intrig...@debian.org wrote:
 Package: tlsdate
 Version: 0.0.5-2
 Severity: normal

 Hi,

 my understanding is that tlsdate will be broken once Nick's proposal
 is accepted, and SSL handshakes don't include timestamps anymore.

 Is this correct?
 If it is, is including tlsdate in a stable Debian release a good idea?

 Cheers,
 --
   intrigeri
   | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
   | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org