Thom2000
Joined 3 years ago
Karma
24
Submissions
23
Member since
Dec 5
Recent submissions
Comment · 11 days ago
FWIW this future lint `non_exhaustive_omitted_patterns` will help a bit: https://github.com/rust-lang/rust/issues/89554
Comment · 2 months ago
> (If the author reads this, my name changed from Noel to Neal at some point. I don't really mind though; my name is a bit unusual and I've been called all sorts of things.)
I think it'd be good to update the about page with that info: https://noelwelsh.com/landing/about/
Comment · 2 months ago
> Your free server will likely have a blacklisted ip address.
>
> Oracle is exceptionally frustrating to use in the first place. Pay the 5$ a month and use AWS or Digital Ocean
Funny thing that you mention this because according to Xenedra it's my DO IP that's blacklisted (even though I have it for years with no bad activities) but the free Oracle one is fine.
I was quite surprised by that.
Comment · 3 months ago
Yep. Especially with non-wildcard certs this leaks all service names (privacy concern).
Comment · 3 months ago
Sadly most tools still doesn't support it: https://github.com/cert-manager/cert-manager/issues/8373#iss...
And then the issue is protecting the private key of the issuer and monitoring certificates (it's a good idea to do that anyway).
Comment · 5 months ago
> The artist, JT Nimoy, was an Emacs user but still thought it would be fun to set up a dichotomy--some fun details on this blog
I don't see any details about setting up a dichotomy in that article (just that the author was a happy Emacs user). Or maybe that was in that HN meetup you mention?
Comment · 5 months ago
Github still doesn't support SHA-256 git repos (https://github.com/orgs/community/discussions/12490) even though their competitors (Gitlab, Codeberg) have that for ages now.
Comment · 7 months ago
Sadly services such as Github don't support these so it's mostly good for internal infrastructure.
Comment · 10 months ago
> PGP supports RSA. That's enough reason to avoid it.
I hate to break the narrative but age also supports RSA, for SSH compat:
Comment · 10 months ago
I wonder if they think of a deeper integration of this into the age binary. Currently the invocation looks extremely ugly:
age -r $(go run filippo.io/torchwood/cmd/age-keylookup@main [email protected])Comment · 1 year ago
> My biggest hurdle was getting it to export to a nice looking PDF that could be emailed or printed later.
If you can export to structured data such as JSON, I guess Typst would be a perfect fit for that job.
Comment · 1 year ago
Exactly!
Bearer tokens should be replaced with schemes based on signing and the private keys should never be directly exposed (if they are there's no difference between them and a bearer token). Signing agents do just that. Github's API is based on HTTP but mutual TLS authentication with a signing agent should be sufficient.
Comment · 1 year ago
FWIW it's possible to run readme examples automatically add part of tests: https://github.com/parallaxsecond/rust-cryptoki/blob/main/cr...