MyFamily currently is a config string. It'd be nice if it was a line list like RecommendedVersions as that would make configuration files a bit more readable.
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.
The code that processes MyFamily still expects it to be a char * - this patch changes it to a smartlist * containing char *, but doesn't change how it's processed.
But it looks like this patch makes it so Tor would no longer accept the old format. That's not right, though: we need to make sure that the there can be multiple lines and multiple options on each line. Otherwise all old MyFamily lines will stop working.
I does accept both multiple lines and multiple options on the same line. I have changed the test to actually test both cases and tested manually with the following lines on torrc:
However, I did change the man page to mention only the new format. I did that to encourage the use of the new format. I can change the man page to mention both formats if you think it is better.
Oh, I see what you did. Yes, you're correct there. The code looks like it should work.
One thing that we try not to do any more, though: we try not to rewrite values that could get written back into the torrc by a SAVECONF command. What we usually do instead now is, when we want to normalize a configuration value, normalize it into a separate field of or_options_t. What do you think of the patch I've made on top of your branch, in my-family-list-fix-4498 in my public repository? The URL is