orangepizza

hmmm noticed vsink ratelimited speed is about ballpark of ms terminal. maybe that's their problem as well?

Because ACME protocol server only ask CSR after domain client asked passed validation, Is it possible to do CSR based challenge in current protocol? otherwise VA have to be able...

They even try to verify certificate for internal ip (10.123.123.123) and just 192.168.0.0/16 get special treatment, I think their web is just too lex at inpit varification

made a draft on IETF: https://datatracker.ietf.org/doc/draft-suchan-acme-onion/ discussion on acme mailing list

copied from forum: After my PR for add support for draft-acme-ip on pebble merged, I looked at boulder code to implement on it too and searched possible problems about it.(like...

> > > > I think update wfe1 and 2 to send full identifiers to RA, and update RA do deal with it. > > @orangepizza One thing I forgot...

I found that I need to reboot the router to change AP's channel. otherwise it didn't show up (include restarting the interface from luci)

while I creating tls-alpn testing I found that current tls-alpn test creating wrong testing certificate (SAN DNSname included port number in it, moke verifier had same error too (not triming...

if we can't update those, ca we at least depricate them? it's already outdated and not represent current Mozilla policy

as it's just a node app, can't you just install it by npm?