Conversation

Notices

1. Embed this notice
   Liv, Honeycomb Engineer 🐝 (olivvybee@honeycomb.engineer)'s status on Sunday, 18-Aug-2024 05:03:43 JST Liv, Honeycomb Engineer 🐝

   @stgiga I imagine that depends on the particular dns host, I don’t think it’s standardised that much

   • Embed this notice
     Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Sunday, 18-Aug-2024 05:03:42 JST Ryan Castellucci :nonbinary_flag:

     in reply to

     @olivvybee @stgiga it

     1) definitely violates the spec
     2) will probably work fine in dig

   • Embed this notice
     Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Sunday, 18-Aug-2024 05:04:27 JST Ryan Castellucci :nonbinary_flag:

     in reply to

     @olivvybee @stgiga being pedantic, it should probably be _pronouns for the text record

   • Embed this notice
     Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Sunday, 18-Aug-2024 05:06:59 JST Ryan Castellucci :nonbinary_flag:

     in reply to

     @olivvybee @stgiga wait I looked up the spec, binary data is allowed? Welp..

   • Embed this notice
     Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Sunday, 18-Aug-2024 05:08:13 JST Ryan Castellucci :nonbinary_flag:

     in reply to

     @olivvybee @stgiga https://github.com/tailhook/dns-parser/issues/22#issue-267569151

   • Embed this notice
     Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Sunday, 18-Aug-2024 05:09:21 JST Ryan Castellucci :nonbinary_flag:

     in reply to

     @olivvybee @stgiga as an aside, UTF-8 works in wifi ssids