Work in progress, will deploy soon and let you guys know when is ready,
I still need to add some features so is generic, usable on other
situtions.
https://git.sr.ht/~rek2/nnrpd-password
Also writing a Usenet/Matrix portal, also work in progress.
OK this is already deployed and working, feel free to submit patches,
there are a lot to do still but is working now and is live on my own
server.
Happy Hacking
ReK2
On 27.07.23 21:36, rek2 hispagatos wrote:
OK this is already deployed and working, feel free to submit patches,
there are a lot to do still but is working now and is live on my own
server.
Happy Hacking
ReK2
great work!
i dont know about rust and pgsql so i need ask question:
this code is safe against sql injection?
no need to check if username is alphanum before passing to db?
fn clean() splits by whitespace and parses to string only?yes, I am learning rust so I am sure there is more idiomatic ways and
I was testing against the information I got from: https://www.eyrie.org/~eagle/software/inn/docs-2.7/external-auth.html
But I found it to be mistaken or I did not understood it right, because
it says it only sends 2 pieces of information the Name and Password information but it actually sends more so I had to do adjustments like:
On 28.07.23, rek2 hispagatos wrote:
I was testing against the information I got from:
https://www.eyrie.org/~eagle/software/inn/docs-2.7/external-auth.html
But I found it to be mistaken or I did not understood it right, because
it says it only sends 2 pieces of information the Name and Password
information but it actually sends more so I had to do adjustments like:
"In addition, nnrpd generally also passes, if available, the fields
mentioned as intended for resolvers; in rare instances this data may be useful for authenticators."
But everytime i read rust, i dont like their syntax xD
Yes indeed, I figure that out the hard way :D :D with debuggin :D
I get lost in translation a lot.
.....
Happy Hacking
reK2
On 28.07.23, rek2 hispagatos wrote:
Yes indeed, I figure that out the hard way :D :D with debuggin :D
I get lost in translation a lot.
.....
Happy Hacking
reK2
who writes with debugs is king!
and much more king if you dont know what you're doing :D
i wrote a little too with greece coffee!
https://github.com/go-while/go-inn2-auth
same binary as daemon and authenticator/resolver? .oO*
daemon listens on tcp port (maybe socket later)
cli talks via tcp textproto with daemon
multiple workers and parallel requests
daemon can act as cache, less requests to databases (later)
read users from json file, reloads every 60s if hash changed
places for mysql, pgsql, redis are there but need testing first
test on command line looks good for me but did not install to try...
not sure how to configure inn.conf xD
Looking good, I will test it
...
, everything seems so much simpler with Go
;)
I will love to engage to write a small two way gateway between a
usergroup and a lemmy group( a reddit alike decentralized service part
of the fediverse ).
Happy Hacking
ReK2
ok i'm near to have a working test bench
you are using "res" in your config?
would explain why you got all lines
will provide instruction soon
On 29.07.23, rek2 hispagatos wrote:
Looking good, I will test it
can you provide a readme to your tool?
with your inn config for readers and how to implement the binary?
still had no time to test mine, not even tried to lookup the config :D
i don't know if this code does anything good
at least it dit not crash over night in infinite loop
hammered with millions of requests and mem <20KB?! with 3 users added
On 2023-07-31, Billy G. (go-while) <no-reply@no.spam> wrote:
ok i'm near to have a working test bench
nice!
you are using "res" in your config?
would explain why you got all lines
would be nice to know under which circumstances inn2 sends user+pass
only or more lines, as reference documentation states, or does it always
pass all 7 lines to stdin actually?
Hi Billy,
would be nice to know under which circumstances inn2 sends user+pass
only or more lines, as reference documentation states, or does it always
pass all 7 lines to stdin actually?
Actually, nnrpd always provides the 7 lines (when of course the related information is available).
The documentation needs fixing. Thanks for having pointed that out!
would be nice to know under which circumstances inn2 sends user+pass
only or more lines, as reference documentation states, or does it always >>> pass all 7 lines to stdin actually?
Actually, nnrpd always provides the 7 lines (when of course the related
information is available).
The documentation needs fixing. Thanks for having pointed that out!
PD: Julien, check the start of the thread, the documentation about authentificator does need an update please, I was going nuts until I
hadd debug/logging features to my program because it was not following
what was there (in the doc) :)
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 308 |
Nodes: | 16 (2 / 14) |
Uptime: | 91:39:59 |
Calls: | 6,923 |
Calls today: | 1 |
Files: | 12,382 |
Messages: | 5,434,029 |