RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Reported (1)

RFC 6143, "The Remote Framebuffer Protocol", March 2011

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: rai

Errata ID: 4951
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Simon Kissane
Date Reported: 2017-02-26

Section 7.2.2 says: 

   The client encrypts the challenge with DES, using a password supplied
   by the user as the key.  To form the key, the password is truncated
   to eight characters, or padded with null bytes on the right.  The
   client then sends the resulting 16-byte response:

It should say:

   The client encrypts the challenge with DES, using a password supplied
   by the user as the key.  To form the key, the password is truncated
   to eight characters, or padded with null bytes on the right; then the
   bits of each byte of the key are reversed. The client then sends the
   resulting 16-byte response:

Notes:

Added text "; then the bits of each byte of the key are reversed" is essential to implementation of a VNC client or server which interoperates with existing VNC clients or servers, but the text fails to mention this.

See https://www.vidarholen.net/contents/junk/vnc.html

I confirmed the claims of the above web page while writing my own VNC server. I implemented VNC authentication without mirroring the bytes of the DES key and TigerVNC 1.5.0 could not authenticate to my VNC server. When I added code to mirror each byte of the DES key as described by the above web page, TigerVNC 1.5.0 could authenticate to my test VNC server.

Status: Rejected (1)

RFC 6143, "The Remote Framebuffer Protocol", March 2011

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: rai

Errata ID: 2745
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Mykyta Yevstifeyev
Date Reported: 2011-03-07
Rejected by: Robert Sparks
Date Rejected: 2011-03-08

Section 11 says: 

11. References

11.1. Normative References

   [RFC1950]  Deutsch, L. and J-L. Gailly, "ZLIB Compressed Data Format
              Specification version 3.3", RFC 1950, May 1996.

   [RFC1951]  Deutsch, P., "DEFLATE Compressed Data Format Specification
              version 1.3", RFC 1951, May 1996.

   [XLIBREF]  Nye, A., "XLIB Reference Manual R5", June 1994.

11.2. Informative References

   [RFC4254]  Ylonen, T. and C. Lonvick, "The Secure Shell (SSH)
              Connection Protocol", RFC 4254, January 2006.

   [RFC4301]  Kent, S. and K. Seo, "Security Architecture for the
              Internet Protocol", RFC 4301, December 2005.

   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
              May 2008.

It should say:

11. References

11.1. Normative References

   [RFC1950]  Deutsch, L. and J-L. Gailly, "ZLIB Compressed Data Format
              Specification version 3.3", RFC 1950, May 1996.

   [RFC1951]  Deutsch, P., "DEFLATE Compressed Data Format Specification
              version 1.3", RFC 1951, May 1996.

   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
              May 2008.

   [XLIBREF]  Nye, A., "XLIB Reference Manual R5", June 1994.

11.2. Informative References

   [RFC4254]  Ylonen, T. and C. Lonvick, "The Secure Shell (SSH)
              Connection Protocol", RFC 4254, January 2006.

   [RFC4301]  Kent, S. and K. Seo, "Security Architecture for the
              Internet Protocol", RFC 4301, December 2005.

Notes:


--VERIFIER NOTES--

Report New Errata



Advanced Search