4 ms·
Great. Now, if instead of starting with a half-baked implementation in Java that involves 36 configuration files and an artisanally sculpted Maven build, how a
by whatnotests 10y ago
Great.
Now, if instead of starting with a half-baked implementation in Java that involves 36 configuration files and an artisanally sculpted Maven build, how about we make a spec, in terms of API docs and compliance tests.
Anything conforming to the spec which passes the tests is considered a valid implementation.
(Had to get that off my chest. Thanks.)
- T-A 10y agoLooks like Python to me: https://github.com/apache/incubator-milagro-mfa-server https://github.com/apache/incubator-milagro-mfa-server The core MFA library seems to be C, with a bunch of implementations (wrappers?) in Java, C#, JS, Python, Go and Swift: https://github.com/apache/incubator-milagro-crypto https://github.com/apache/incubator-milagro-crypto
- whatnotests 10y agoI admit I didn't even look at any code. I've been conditioned to have expectations in-line with my rant.
- musicnarcoman 10y agoThis. It makes me sad that so many projects skip this part. "We dont need a protocol specification. The code is the spec."