検索

@[email protected] So far, I'm able to reproduce it with #LetsEncrypt certs issued from #certbot, #caddy, and #certmanager, both fresh and a month or two old.

Firefox 123.0.1 doesn't trust any of them.

Again, it still works because the OS CA trust includes it, so most users won't notice anything broken (yet).

If you're using #Caddy with #Jenkins, here's a way to make that a little less obvious to script kiddies: route /* { reverse_proxy localhost:8080 { @unauthed status 401 403 handle_response @unauthed {
header -x-jenkins
header -x-jenkins-session
header -x-hudson
copy_response
}
}
}

I really like #Caddy, but sweet glory has it been a nightmare game of endless whack-a-mole for #SElinux. #Linux