Conversation

Notices

1. Embed this notice
   Matthew Garrett (mjg59@nondeterministic.computer)'s status on Monday, 25-Mar-2024 10:21:11 JST Matthew Garrett

   • Ryan Castellucci :nonbinary_flag:

   @ryanc Oh hmm is this a "If we send any sort of extension packet here existing clients will break" situation?

   • Embed this notice
     Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Monday, 25-Mar-2024 10:21:10 JST Ryan Castellucci :nonbinary_flag:

     in reply to

     @mjg59 Well, you could stuff extension data into the comments field of the protocol version info, but the server sends its message before the client, so splicing to the right backend would be a bit fucky.

   • Embed this notice
     Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Monday, 25-Mar-2024 10:22:07 JST Ryan Castellucci :nonbinary_flag:

     in reply to

     @mjg59 Yes. I believe I have a patch for dropbear to do that if you want it.

   • Embed this notice
     Matthew Garrett (mjg59@nondeterministic.computer)'s status on Monday, 25-Mar-2024 10:22:08 JST Matthew Garrett

     in reply to

     • Ryan Castellucci :nonbinary_flag:

     @ryanc Looking at the RFC it sounds like the server is allowed to send additional information in the connection - a client that understood this would presumably be able to alter its behaviour (eg, send a desired hostname, get connected to the appropriate backend, re-start negotiation)?