You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Need support for TLS session resumption in accordance with the TLS 1.3 specs, which makes both Session IDs and Session Tickets obsolete in favor of in-band PSK.
Currently it appears that only the obsoleted methods are available within Node. It is possible that this is simply a documentation issue, but I don't see anything that indicates the ability to exchange the key in-band from the ServerHello. The documentation of PSK within the TLS module appears to only deal with out-of-band PSK only secure connections.
Unfortunately the current documentation indicates that session tickets are compatible with TLS 1.3. Being unfamiliar with the spec it took a great deal of digging before I discovered that is not in line with the TLS 1.3 specification. At the very least it is a documentation issue, but I can't find anything that indicates in-band PSK exchange is supported within Node at all.
I understand that session resumption is simply a nice to have in HTTP land, but it appears that it is much more crucial for an FTP server which is what I am working to implement (via ftp-srv). The lack of session resumption can lead to a variety of issues with FTPS, the most obvious being a stern warning from Filezilla but more worrying is inconsistent behavior, timeouts, and transmission failures.
Describe the solution you'd like
Simplified integration of PSK based session resumption within the TLS module. Simpler said than done I'm sure, and I'm fairly ill equipped to tackle it myself without guidance. That said, I am willing to try if some pointers could be provided.
Describe alternatives you've considered
Writing the custom FTP server in another language, not a very appealing option since everything is already implemented in Node.
The text was updated successfully, but these errors were encountered:
doesdev
changed the title
Support TLS Session Resumption in Accordance with TLS 1.3 Specs (using PSK)
Support TLS session resumption in accordance with TLS 1.3 specs (using PSK)
Aug 6, 2021
Is your feature request related to a problem? Please describe.
Need support for TLS session resumption in accordance with the TLS 1.3 specs, which makes both Session IDs and Session Tickets obsolete in favor of in-band PSK.
Currently it appears that only the obsoleted methods are available within Node. It is possible that this is simply a documentation issue, but I don't see anything that indicates the ability to exchange the key in-band from the
ServerHello
. The documentation of PSK within the TLS module appears to only deal with out-of-band PSK only secure connections.Unfortunately the current documentation indicates that session tickets are compatible with TLS 1.3. Being unfamiliar with the spec it took a great deal of digging before I discovered that is not in line with the TLS 1.3 specification. At the very least it is a documentation issue, but I can't find anything that indicates in-band PSK exchange is supported within Node at all.
I understand that session resumption is simply a nice to have in HTTP land, but it appears that it is much more crucial for an FTP server which is what I am working to implement (via
ftp-srv
). The lack of session resumption can lead to a variety of issues with FTPS, the most obvious being a stern warning from Filezilla but more worrying is inconsistent behavior, timeouts, and transmission failures.Describe the solution you'd like
Simplified integration of PSK based session resumption within the TLS module. Simpler said than done I'm sure, and I'm fairly ill equipped to tackle it myself without guidance. That said, I am willing to try if some pointers could be provided.
Describe alternatives you've considered
Writing the custom FTP server in another language, not a very appealing option since everything is already implemented in Node.
The text was updated successfully, but these errors were encountered: