Live data from Hacker News

Viewing profile — codesniperjoe

codesniperjoe

HN member
Joined
Wed, Dec 21, 2022, 5:30 PM UTC
HN karma
151
Public activity
27 items

About codesniperjoe

https://paepcke.de

Recent public activity

  1. comment
    Comment #34699911

    Warning: Do not go to this site with enabled javascript! They spam your uplink DNS provider with thousands of uniq, uncachable (fingerprinting?) 'test' dns keys without your consen…

  2. comment
    Comment #34536253

    Projects Console screen reader infrastructure Vessel - Integrated Application Containers for FreeBSD Enable the NFS server to run in a vnet prison Pytest support for the FreeBSD te…

  3. story
  4. comment
    Comment #34479423

    TLDR: Avoid it if you can!

  5. comment
    Comment #34478965

    TDLR: How You Respond to Security Researchers Says Everything ... [ About Your Business State ].

  6. story
  7. comment
    Comment #34463808

    The compiler (go) is part of a static read-only (compressed/in-memory) RootFS. Build on a air-gap build server, touching only signed/verified/reviewed code from git-offline mirror …

  8. comment
    Comment #34453985

    Yes, the base idea is not that new. I store since years every GO based application I use as small (few kb) source code tree checkout only, no binary at all. At runtime the wrapper …

  9. comment
    Comment #34450666

    For this new feature you pay indeed with the need for r/w and executable tmpfs/overlay somewhere. This does not replace classic ASLR: OpenBSD 5.7 activated position-independent sta…

  10. comment
    Comment #34450537

    Plain, simple and effective as always! The highly complex 'black magic' is 'sort --random' and (re-)link it all again. :) Makefile.relink: cc -o sshd `echo ${OBJS} | tr ' ' '\n' | …

  11. comment
    Comment #34450060

    Finally! At least, someone finally understands that static, fully predictable, reproduce-able-builds are only an convenience feature for the attacker side.

  12. story
  13. comment
    Comment #34429739

    In general I would tend to agree, but have lately took a look at the gh dependencies this tool draws in today? [0] This is not a (classic) unix cli tool, as it was some month befor…

  14. comment
    Comment #34429159

    We should really pin a daily reminder about the unfixable SSL truststore dumpster fire situation (every day a different one) to the top of YC!

  15. comment
    Comment #34390005

    Netflix contributes. Real Code. Rock stable. High quality. For so many years. So its not only the Free-Beer-License for them. I have never seen a single commit comming back from ot…

  16. comment
    Comment #34387465

    FreeBSD Hammer2 [r/o][pending] Lots of work will end up (as often) in the ports section, if nobody has a strong point why it is usefull to maintain it in base. Users/use-cases feed…

  17. comment
    Comment #34322485

    If google is on the way to fix this, a look at the resources on (EVERYONES LOCAL!) not de-duplicated $GOMODCACHE would be very welcome too! (At least from an enviromental perspecti…

  18. comment
    Comment #34308004

    If you need a local & offline first tool to log/track/archive changes from all kind of git repos yourself, from: * github.com * sourcehut (sr.ht) * gitlab.com * codeberg.org * ... …

  19. comment
    Comment #34289684

    TLDR: gps tracker with backup battery and activated sim card found in sealed car ECU (BTO from china, to save some pennies, in a high-security-custom build car)

  20. comment
    Comment #34257038

    Thank you! That is a quick (helpful) fix! Beside of checks for the integrity of SelfSigned Certificates, I do not used this function directly. My assumption about the TLS impact wa…

  21. comment
    Comment #34250354

    One example, the started (and then stuck) net/ip to net/netip migration? The tailscale netip package is great (as external pkg), but without commit to a full migration plan, just s…

  22. comment
    Comment #34250221

    > TLS handshakes now return a CertificateVerificationError if they fail because of, well, certificate verification. ... as long the crypto/x509 CheckSignatureFrom ignores the pathl…

  23. comment
    Comment #34249800

    Go is great. But if you look close enough, go also has some dark corners. The reason the biggest parts of go/crypto is well designed, good readable code, is mostly the work of one …

  24. comment
    Comment #34249630

    > Finally, reviewing the BoringCrypto integration by Russ. Do you think there is a rollback/cleanup possible of current boring/fips situation? (eg. push it back into a seperate sta…

  25. comment
    Comment #34093584

    Maphash is an (non-cryptographic-secure) hash function, like CRC32 / CRC64 / XXH3-64 and others, so it turns data in an (almost) uniq uint64. The main difference is, it is an hardw…