Joonas Kuorilehto
Joonas Kuorilehto
Does the lsmod from Raspbian help identify the dependencies? ``` root@raspberrypi:/home/pi# lsmod Module Size Used by rfcomm 49152 4 cmac 16384 3 algif_hash 16384 1 aes_arm 16384 3 aes_generic 40960...
Dependencies as a graph: https://go.dev/play/p/r_VGByiQ9Jw ```mermaid graph TD aes_generic --> aes_arm af_alg --> algif_hash af_alg --> algif_skcipher btbcm --> hci_uart bluetooth --> hci_uart bluetooth --> bnep bluetooth --> btbcm bluetooth...
I tried to put the cert to use in CertPEM and KeyPEM first as cert.pem and key.pem assuming they would be picked up from instance directory. I think what happened...
Does the CA need to change? I guess in principle it probably should for correctness but 90% would be to just change the subjects right? Maybe the CA file could...
Once you regenerate the cert you can check the cert by pasting it to this test code in go playground and run it online in browser. https://play.golang.org/p/I8S80_1P1p Hope this helps....
Confirmed new certs validate now fine with go net/http. Thanks for the fix. 🍰 I think you're right about CA not being validated. I think where it may come up...
Hm. Should check if tailscale Whois works with tailscale serve; if we could add option to bind only to localhost and possibly optional Whois based identity allowlist, that would keep...
Sysctls in a text files like wifi config makes sense to me. @stapelberg do you mean this should be built in feature then in gokrazy, or does it exist? Router7...
So should we create a pull request to Tailscale cli to set sysctl then? It already has trivial gokrazy specifics so a sysctl for us might not be too wild...
I've created the issue and PR to implement setting sysctl in Tailscale upstream. https://github.com/tailscale/tailscale/pull/11408/