๐Ÿ’พ Archived View for bbs.geminispace.org โ€บ u โ€บ alexlehm โ€บ 64 captured on 2023-07-22 at 18:03:14. Gemini links have been rewritten to link to archived content

View Raw

More Information

โžก๏ธ Next capture (2023-09-08)

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

Re: "I'm glad there's now an dedicated place for discussion..."

Comment in: s/misfin

This are different kinds of port scans I assume, ECONNRESET means that the client closed the connection directly, so that checked if the port was open, the other one is a TLS connect without a client cert when one is required. The 3rd one I am not sure, maybe its a connect that tries a HTTPS request

๐Ÿค– alexlehm

2023-05-14 ยท 2 months ago

5 Later Comments โ†“

๐Ÿค– alexlehm

you simulate the connections with telnet when you just do control-+ and then close (or use netcat) and the 2nd with using openssl s_client without a client cert

๐Ÿš€ lem

@alexlehm is on the money, they're just port scanning artifacts. I've been getting them too. You'll see the same thing if you nmap your mailserver.

๐Ÿš€ lem

It'd probably be safe to comment out the `print(err)` in `receive_forever` if you don't want them to show up - after losing some messages day one I was erring on the side of caution lol.

๐Ÿ satch

okay, my knowledge of these things is not what it should be

thank you both @lem and @alexlehm for the info

๐Ÿค– alexlehm

I am getting a lot of these on the gemini server as well

โ€” /u/alexlehm/image/2.png

Original Post

๐ŸŒ’ s/misfin

I'm glad there's now an dedicated place for discussion about misfin. I've been struggling to receive messages successfully, but just this morning I did (followed by lots of errors): gemini://satch.xyz/er.txt Do you know what might be going on? I'm running simply the reference implementation without any of my modifications (for the moment).

๐Ÿ’ฌ satch ยท 6 comments ยท 2023-05-14 ยท 2 months ago