Info about not working with real SSH

[milkpirate]

Hey, regarding this:

Warning

This project is still under development.

• All functions are tested with pamtester.
• TOTP verification can work in real SSH authentication procedure.
• Yubico OTP verification cannot work in real SSH authentication procedure. I think it's related to the HTTP request. That remains unfixed.

I am facing the same problem with a PAM I would like to write that uses Telegram as the 2nd factor.

Just to let your know, the problem is described here: https://stackoverflow.com/questions/33248427/how-to-debug-c-shared-library-written-in-go-it-hangs-on-net-call and a solution is given in the comments.

Even though I am not experienced enough to apply it to my PAM. But if you are able to and figure it out, please let me know!

EDIT:
There are some threads like here and here here where the problem is well described and there will be no solution (since we dont have the fork/dlopen order under control, since this is done by the PAM framework).

[bianyifan]

Hi @milkpirate ,

Thank you very much for this information! It's great to know why it happens, and I guess as golang/go#15538 states, this is just a golang thing and probably has no workaround. Maybe rust can work better in this case.
Although I haven't got time to work on this as the original reason of developing this library is now replaced by other mature solution. This project would unlikely be continued.