[TLS] Issue 26: Implementation pitfalls

To: tls at ietf.org
Subject: [TLS] Issue 26: Implementation pitfalls
From: Eric Rescorla <ekr at networkresonance.com>
Date: Sun, 03 Jun 2007 07:58:47 -0700
Cc:
List-archive: <http://www1.ietf.org/pipermail/tls>
List-help: <mailto:tls-request@lists.ietf.org?subject=help>
List-id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-post: <mailto:tls@lists.ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
User-agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)

http://www3.tools.ietf.org/wg/tls/trac/ticket/26

Pasi suggested an implementation pitfalls section. I'm lukewarm
on this.

Proposed resolution: add if someone else writes. 

-Ekr

_______________________________________________
TLS mailing list
TLS at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls

Follow-Ups:
- RE: [TLS] Issue 26: Implementation pitfalls
  - From: Pasi.Eronen

Prev by Date: [TLS] Issue 16: Alert clarifications
Next by Date: [TLS] Issue 30: Reject RSA public exponent 1
Previous by thread: [TLS] Issue 16: Alert clarifications
Next by thread: RE: [TLS] Issue 26: Implementation pitfalls
Index(es):
- Date
- Thread

[TLS] Issue 26: Implementation pitfalls

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.