#14999 (moved) is about a possible mass migration to doing QuotedString right... but we can at least fix the things introduced in #8405 (moved), since we know they won't break any users.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
One thing that breaks with quotedstring in this case: NUL characters in the string. Does this matter? Do we even support this? The control.c implementation is kind of assuming that everything we send out over the control port can be represented as a nul-terminated string.
\r and \n are also potentially problematic for control port clients that make simplifying assumptions about the response protocol. (I think I'm guilty of writing one. :P) Maybe tor should reject SOCKS username/password with any dangerous characters? BTW, is a hostile SOCKS client part of the threat model?
After conversation with atagar yesterday, I think we think that we need a better format here: the handling of NULs, control chars, and newlines in QuotedString won't actually work for us on this.
Trac: Status: needs_review to needs_revision Summary: Strings introduced in #8405 (moved) should be proper QuotedStrings to bring some sanity to quoted strings in the controller api