You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 18, 2019. It is now read-only.
My solution needs to be FIPS-140-2 compliant, which is partly done by using a Go wrap of openssl for all cryptography instead of the standard net/crypto packages.
If a method were exposed that allowed me to add an entry to the dialers map in dialer.go, then I could register a method to call the dialer of my choice.
I've done this on a local copy of srslog. Is the any interest in adding this to the public branch?
The text was updated successfully, but these errors were encountered:
I'm curious to see it. Being able to set a custom dialer would certainly make this more flexible. I just don't want it to break backwards-compatibility or add any risk. 😄 So let's see that thing!
My solution needs to be FIPS-140-2 compliant, which is partly done by using a Go wrap of openssl for all cryptography instead of the standard net/crypto packages.
If a method were exposed that allowed me to add an entry to the dialers map in dialer.go, then I could register a method to call the dialer of my choice.
I've done this on a local copy of srslog. Is the any interest in adding this to the public branch?
The text was updated successfully, but these errors were encountered: