💾 Archived View for bbs.geminispace.org › s › misfin › 5595 captured on 2023-11-14 at 08:55:20. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-11-04)
-=-=-=-=-=-=-
I've changed a few things in the misfin code:
- pass flake8 test
- rename the main package from "transponder" to "misfin"
- Add a setup.py: "pip install ." will install all the required dependencies
- Add a "misfin" command-line program (it uses the "click" module), everything can be done with this command
Git repo link below
misfin gitlab repository (cipres)
Sep 26 · 7 weeks ago · 👍 flipperzero, clseibold
😎 flipperzero · Sep 27 at 06:35:
thought i'd drop in with some troubleshooting/notes
i'm able to successfully run the setup.py, then afterwards generate via "misfin make-cert user blurb localhost user.pem" and have a server run in the background via "misfin receive-as user.pem" and ^Z so I can run as "bg".
When I try to run
misfin send-as user.pem rfc@misfin.org "message"
it seems to hang for a bit then reports this log
(will be posted in 2nd message)
😎 flipperzero · Sep 27 at 06:46:
Here's the log in question. I'm having a hard time figuring out why this might be happening. I remember seeing mention of broadcasting over a specific port, maybe having to do with a blocked port? If it's gemini tho, it should be fine, as I'm running a gemini server unless that might introduce interference. My next thought is that I've seen mention that, for whatever reason, the port for misfin which is 1958 iirc? Doesn't seem to be open across a lot of networks, I'm not sure why or if I'm inferring that correctly. Let me know what you think, thank you.
😎 flipperzero · Sep 27 at 12:38:
update: I went ahead and sent to "alexlehm@gemini.lehmann.cx" instead of "rfc@misfin.org" and it seemd to have done the trick returning a "20 xxxxxx..." code. I'd seen previously that perhaps the rfc address is improperly configured? in either case, I've now been able to do this running a server on 127.0.0.1 to resolve to my hostname. I can't wait to see what else new happens with misfin. If anyone would like to try, please attempt to send a message to flipperzero@hashnix.club
@flipperzero Connection refused on hashnix.club port 1958, either the port is blocked or the cert is wrong. Did you create the cert with "hashnix.club" for the hostname ?
😎 flipperzero · Sep 27 at 13:20:
whenever i try to do "misfin make-cert flipperzero "flip0" hashnix.club title.pem" or "misfin make-cert flipperzero "flip0" ip.v.4.address title.pem" it seems to generate fine enough, but when I run "misfin receive-as title.pem" I get this back.
it seems to be similar to the last time i got this, tho I'm unable to modify the misfin.py file in the python3 dist package .egg
@flipperzero Are you sure nothing is listening on port 1958 ? What does "hashnix.club" resolve to ? I see that hashnix.club has an ipv4 and an ipv6 address, so i wonder if this could be the issue, but it shouldn't ..
@flipperzero Hhmmm, misfin always uses AF_INET, meaning it will always try to bind an ipv4 address. Can you try changing AF_INET to AF_INET6 in receive_forever() ?
😎 flipperzero · Sep 27 at 15:56:
@gemalaya hmmm I see what you're saying. I'm out this morning atm but once i'm back at my desk i'll give that a go
@flipperzero lmk when you want me to test again
I was able to send to alexlehm@gemini.lehmann.cx from behind IPv4 NAT w/ port forwarding. And steve@k0stk.ddns.net is listening for messages.
Is there a config option for specifying a bind address? To make misfin work for my configuration I had to edit misfin.py to force a bind to my NIC address rather than the certificate hostname.
🚀 clseibold · Sep 28 at 00:13:
@BBSman I just tried to send to your misfin server, and I'm getting a 40 temporary error back.
Thanks for trying to send to me.
The error that is reported on my end is:
Error during receive - here's what we recovered:
(address elided)
UnboundLocalError local variable 'req' referenced before assignment
Aborting due to exception.
Edit: Should have said I am using the gitlab.com/cipress python client with python v3.7.3 (not v2.7.16 as previously stated) and had to patch letter.py to be able to generate a certificate.
Edit 2: Figured out which python version my misfin client is using.
😎 flipperzero · Sep 28 at 05:38:
@gemalaya whats your address? i'll test again, i edited the IP6 field you told me about and its working now.
@satch give the test another go
@BBSman I tried to send you a message but I got this
"Connection to k0stk.ddns.net (port 1958) refused "
Thats because my listener was down for repairs. It is back up now and I've been able to send to it from an external system.
@BBSman my message to you worked
@flipperzero mine to you failed errno 111
Added a --ipv6 option as well for "misfin send-as", to force ipv6 in case the remote server listens on an ipv6 address.
@flipperzero Don't have any public address. Glad it fixed your problem, you can update and use --ipv6 now ...