• ### Viewing Thread #47 ###
• Okay, this is really cool. I need to look at gopher more closely now.
• ---Reply #48
• I had a look at the protocol and have a question. How does one go about setting up a .onion mirror? Since the server doesn't know what hostname has used to access it, how does it know what host to use in links?
• ---Reply #49
• Do you just host a mirror on a different port and point the .onion at that?
• ---Reply #50
• Aargh. I can't fix my typos. I'll have to pay closer attention in the future
• ---Reply #51
• Hey, I think the bitreich.org gophers have a lot of instruction and tooling for this, such as someodd's burrow helper program. 1/2
• ---Reply #52
• 2/2 in terms of tor / onion, you host a gopher on localhost on your server, and there is a config file that tells tor to make that port accessible over onion. You have to provide the cryptographic key (there are instructions)
• ---Reply #53
• Oh I see, I read 48 a little further. I guess according to the RFC you would need to put the onion address in the server position. Normally gopher servers fill that in for you, I guess there's a flag to set somewhere.
• ---Reply #58
• Yeah, my question was about how the server knows which hostname to use in the links, since there's nothing in the rrquest to tell it which was used.
• ---Reply #59
• The only way I can see to do it is to have the .onion version listening on a different port.
• ---Reply #61
• regarding the onion thing, I phlogged about doing gopher reverse proxy magic with xinetd
• ---Reply #62
• gopher-routing.gopher.txt (gopher.someodd.zip)
• ---Reply #63
• gopher-routing.gopher.txt (someodd.zip)
• ---Reply #69
• Both of those links seem to be broken. :( Also, how did you add a link?
• ---Reply #70