I have received a misfin message that does not identify the sending domain, so I do have any way of replying and connecting to the client IP address returns a zertificate but does establish a TLS connection. The username is @flipperzero, so if anybody knows them, I have received the mail

Ok, i take that back, a previous message identifies the domain as hashnix.club, so i know the user, i will just send them an email

Posted in: s/misfin

🤖 alexlehm

2023-09-28 · 8 months ago · 👍

5 Comments ↓

😎 flipperzero · 2023-09-28 at 11:07:

Ahh i see then what's happened. 0.0.0.0 does NOT print back my hostname but allows me to send out. Interesting. We posted at the same time btw!

— bbs.geminispace.org/u/flipperzero/5684

😎 flipperzero · 2023-09-28 at 11:12:

I still seem to run into the problem that when I run

although I can generate a certificate, anytime I try to set

under those parameters, I always get back

I wonder what's happening... I modified misfin.py even to broadcast on AF_INET6 instead of INET, and while being able to listen under receive-as, is unable to send with a "blocked" note.

🤖 alexlehm [OP] · 2023-09-28 at 11:17:

the python server does not have a bind address that can be set, i changed that by editing the line and writing 127.0.0.1 directly into it since i wanted to use it with a port forwarder

😺 gemalaya · 2023-09-28 at 12:16:

@alexlehm I added "listen_addr" to receive_forever(), but only the full server mode passed that argument (from the config file). I've just modified the code to add new arguments to "receive-as" so that we can pass a bind address, with ipv4 or ipv6, pushing the code soon.

😎 flipperzero · 2023-09-28 at 20:10:

@BBSman I've used @gemalaya's new --bind feature and my message to you worked!

@satch give it another go, my server was down earlier (had to apt upgrade/reboot, forgot to run the listener back up smfh)

Thank you all, gemalaya, clseibold/auragem, and lem, for your contributions to this space and the amazing tech you're all working on. Everything seems to be going a lot smoother now, w.o the need for forcing ipv6 (tho, still, very useful to keep as a feature in case the gemspace expands any further)