• 0 Posts
  • 37 Comments
Joined 3 years ago
cake
Cake day: January 17th, 2024

help-circle
  • Excellent post, like usual with Dhole, but I feel the defense of NIST/NSA push on non-hybrid Post-Quantum Cryptography (PQC) is weak. I think the author’s arguments boil down to:

    1. NSA is pushing to use it themselves, so why would they use a scheme they know it’s unsafe.
    2. There’s no mathematical space to leave a NOBUS backdoor.
    3. Peter Schwabe, main author of ML-KEM, used to work with Bernstein and was his Ph.D student.

    My responses are:

    1. They very link they used for 2., says: “[NSA is] using double encryption already.”, so they really wouldn’t be using pure non-hybrid PQC, as opposed to how they intend the rest of us to use.
    2. The same could have been said about SIKE (another non-hybrid PQC proposal), yet it was found to be insecure. Furthermore, author of the cited blog with the mathematical argument for 2. works for Google, so she has a conflict of interest in the topic. However, I’m not an expert on the topic, so the mathematical arguments are beyond me.
    3. I get it that Bernstein has a toxic attitude, and thus a toxic community that follows him, so I guess this was added to shut up a lot of incoming toxic responses that simply link to Bernstein’s blog. But yet, I can only see this as such an irrelevant tangent to dismiss criticism.






  • I’m 100% not joking, I once was stuck the the proof of a theorem for a whole week going at it and still wasn’t able to prove it… until I dreamed of the solution, woke up at like 3 am, quickly wrote a skecth of my dream’s proof and went back to sleep. The following morning I checked that path and boom, there it finally was the solution.

    Weirdly enough, this happened twice, although that second time I didn’t woke up at 3 am, just in the following morning as usual.







  • I have a similar use-case.

    What I did for the VPN was to use Wireguard. I configured it using wg-easy, and it’s, well, very easy. What your need to do is:

    1. Install wg-easy via Docker.
    2. Configure it and create a profile.
    3. Open ports in your router to allow port-forwarding the Wireguard tunnel.
    4. (Optional). Install a Wireguard client on your cellphone. I use “WG Tunnel”, a FOSS client. Note that the author of the app is a bit of a religious nut, If you care about that kind of stuff.
    5. Scan the profile QR generated in wg-easy on your WG Tunnel.
    6. Increase the “PersistentKeepalive” parameter to something like 30 seconds in WG Tunnel. This will increase the tunnel’s resiliance to disconnections due to small packet losses; without that, Jellyfin/Navidrome will constantly disconnect.
    7. Open Navidrome/Jellyfin, and done :)

    Let me know If you have any questions, glad to help.




  • I have that exact setup. Let’s suppose you want to use layzer.lan as your domain. The way I did it:

    1. Make a DNS record that maps *.layzer.lan to your private IP (let’s say it is 192.168.0.10). You can do this by either manually editing your local DNS resolver config file, or hosting a DNS server and adding a a new entry. I did the later, and chose AdGuard for that. Either option will make your PC underestand that going to any subdomain *.layzer.lan means going to 192.168.0.10.

    2. Use a reverse proxy. I use nginx-proxy-manager, and added a proxy host for each service you want to access with the link. For example, for my Immich server that is running in port 30041, I added a proxy host such that http://immich.layzer.lan/ takes you to http://192.168.0.10:30041/. Ports 80 and 443 have to be free for nginx to take. You can also add https support from here, and it’s very easy to do if you have bough a real domain.

    Offtopic: I just noticed that on my Lemmy Android client you appear as laserjet, but on web you appear as layzerjeyt lol. Any idea why?