Add a (single) onion service for the new tor blog

added component::webpages/blog in Legacy / Trac parent::22013 in Legacy / Trac priority::medium in Legacy / Trac severity::normal in Legacy / Trac status::new in Legacy / Trac type::enhancement in Legacy / Trac labels

The reason we didn't do it for the old blog was that the old blog server never got into the main tor server rotation, so deploying the onion set-up on it was not easy.

This new blog is run by the pantheon people, so it is also not in the main tor server rotation. I expect that means it continues to be not easy.

That said, hiro has spoken of setting up a proxy, so we don't have to wonder what logs the pantheon folks keep: legacy/trac#22018 (moved). That step might make this ticket easier too.

Replying to teor:

onion service compatibility (mainly URL rewrites)

This one is an interesting question.

I have no idea how we're doing on it. Probably not perfectly yet.

Trac:
Username: ilf
Cc: N/A to ilf@zeromail.org

Important to do, but not as urgent as some of the "it's broken!" tickets.

Trac:
Priority: Medium to Low

Trac:
Owner: hiro to tpa
Component: Webpages/Blog to Internal Services/Tor Sysadmin Team

qbi: while you're moving the ticket to the tsa team, be sure not to miss the part where the blog platform itself needs to make only relative links. that is, if there are any absolute links in the blog to https://blog.torproject.org/, then it will be hard to achieve what teor asked for.

The blog is not hosted on torproject infrastructure. Onion services should run close to the backend service, so this isn't for us.

Trac:
Component: Internal Services/Tor Sysadmin Team to Internal Services/Blog

Now how difficult is this? All major browser have SNI support.

Trac:
Status: new to assigned
Owner: tpa to N/A

Trac:
Status: assigned to new

This would be great to figure out as we are encouraging others to set up onion sites. We were just called out on this in the comments of a related blog post https://blog.torproject.org/comment/273682#comment-273682