‹ BackHN Continuity

Thread

Golang: Crypto/fips140: do not bloat crypto code unnecessarily

19 points · 8 comments · zx2c4

  1. nateb2022 · · focus · HN ↗
    Alberto (<a href="https:&#x2F;&#x2F;github.com&#x2F;golang&#x2F;go&#x2F;issues&#x2F;81639#issuecomment-5855332392" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;golang&#x2F;go&#x2F;issues&#x2F;81639#issuecomment-58553...) found only a 75kB difference between the &#x27;bloat&#x27; and your proposed patch in a stripped binary; and Roland (<a href="https:&#x2F;&#x2F;github.com&#x2F;golang&#x2F;go&#x2F;issues&#x2F;81639#issuecomment-5840291260" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;golang&#x2F;go&#x2F;issues&#x2F;81639#issuecomment-58402...) contended:

    &gt; the symbols in your tester2 program account for ~67kb out of a 2.3mb binary

    OP did find a &quot;600k difference&quot; in an unstripped comparison but if binary size was critical enough that 600k was a big deal, I&#x27;d assume users would be stripping the binaries outright or using a different language (tinygo perhaps) if a &lt;100kb diff was on their list of concerns.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.