💾 Archived View for gemini.bunburya.eu › newsgroups › gemini › messages › 87wni4nc7p.fsf@haraya.loca… captured on 2024-08-25 at 00:02:29. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2022-04-28)

-=-=-=-=-=-=-

Re: Molly Brown and Yggdrasil

Message headers

From: rtr <rtr@haraya.invalid>

Subject: Re: Molly Brown and Yggdrasil

Date: Wed, 09 Feb 2022 07:57:30 +0800

Message-ID: <87wni4nc7p.fsf@haraya.local.net>

Message content

meff <email@example.com> writes:

Apologies for the double follow-up.
On 2022-02-07, rtr <rtr@haraya.invalid> wrote:
> Either way, I'm also curious whether anyone tried hosting a capsule
> under Yggdrasil.
There's also the matter that you're not getting much out of the TLS on
Gemini since Yggdrasil is encrypting traffic onto the overlay
anyway. That shouldn't stop you from generating a certificate for the
Yggdrasil IP as long as you're holding onto a stable IPv6 address and
not grabbing random addresses from your /64.

Hi meff, thanks for the response. I was able to make it work. My

problem was a bunch of things not going right, partly because I

don't know how to deal with IPv6 addresses and partly because I

don't know what I'm doing in general. Anyway, I will post here

what I did to make it work just in case someone else found

themselves in the position that I was.

Yes, you're right. Molly Brown doesn't really discriminate if

you're accessing an IPv6 or IPv4 address.

However, the first problem that I had was that the HOSTNAME

variable and the certificate that you are generating must

match. While that seems obvious enough, I wasn't sure whether I

ought to include the square brackets used in IPv6 addresses. I

first generated a certificate that has an address with square

brackets as its certificate name and then set-up my HOSTNAME

variable the same way.

Molly Brown doesn't like that. The hostname variable should only be

an address without any brackets when used with IPv6. I changed it

back but then I kept getting certificate mismatch errors. So I

generated a new certificate with the one without brackets.

I thought I already solved the problem but now I kept getting

"40 -- Temporary Error". I was trying to figure out the issue and

when I ran molly as root the server popped up. So I know, by then,

that the issue was either with the rc.d script or permissions that

I've set for the folders.

(I'm running Molly Brown in FreeBSD)

After some fruitless documentation diving, I figured I should mess

with the file permissions in DOCDIR and my configuration

directory. I've set both of those folders to be owned by

daemon:daemon and played around with the file permissions. What

worked were the following:

# chmod -R 555 /your/gemini/config/path

# chmod -R 755 /your/doc/dir/path

So in gist. If you want to run Molly Brown under Yggdrasil, you'll

need to set your HOSTNAME variable and certificate variable to your

Yggdrasil address without square brackets and make sure that your

config folder and DOCDIR folder is owned by daemon with the

permissions set to 555 and 755 respectively.

If anyone's interested here's Yggdrasil Capsule:

gemini://[209:dead:1cc2:970:637b:450f:6575:9a24]/~/rtr/

Cheers everyone!

--

Ang kalayaan ay dili gihatag, ini'y giabot.

--

{gemini,gopher}://kalayaan.xyz

Related

Parent:

Re: Molly Brown and Yggdrasil (by meff <email@example.com> on Tue, 8 Feb 2022 00:58:20 -0000 (UTC))

Start of thread:

Molly Brown and Yggdrasil (by rtr <rtr@haraya.invalid> on Mon, 07 Feb 2022 21:17:35 +0800)

Children:

Re: Molly Brown and Yggdrasil (by meff <email@example.com> on Wed, 9 Feb 2022 08:02:07 -0000 (UTC))