crypto: rename internal mirage references to match the fork
The fork was rebranded mirage-crypto -> crypto at commit 87888f69
(initial import) but several internal labels still carried the old
name. Replace them so the visible identity matches the package
naming everywhere:
- src/c/crypto.h: header guard H__MIRAGE_CRYPTO -> H__CRYPTO.
- config/cfg.ml: Configurator.V1.create label "mirage-crypto" -> "crypto".
- rng/entropy.ml: Logs source "mirage-crypto-rng-entropy" -> "crypto-rng-entropy".
- src/crypto.mli: rewrite the top-level docstring to describe the
fork rather than mirage-crypto. The new wording explicitly names
Hannes Mehnert (mirage-crypto upstream maintainer), David Kaloper
Meršinjak (original ocaml-nocrypto author), and Thomas Pornin
(BearSSL author whose ct64 / ctmul64 primitives we vendor).
Includes links to mirage-crypto, ocaml-nocrypto, and BearSSL.
- ec/crypto_ec.mli: "Mirage-crypto-ec implements..." -> "Crypto-ec
implements..."; reference to [mirage-crypto-ec] -> [crypto-ec].
- rng/crypto_rng.mli: replace the dangling references to
Crypto_rng_mirage and Crypto_rng_miou_unix (which never existed
in the fork -- the Mirage and Miou sub-libraries were dropped per
the fork's README) with a reference to Crypto_rng_unix.
Not touched (intentional):
- The mc_* C symbol prefix. Renaming would require touching every
CAML external binding in src/native.mli and the matching C
CAMLprim definitions; that's a much larger surgery and gives
no functional benefit. Filed as future work if anyone cares.
- README.md and LICENSE files -- those carry attribution to the
upstream projects and should stay accurate.
- Comments that document provenance ("TLS regression test from
mirage-crypto", "hand-tuned mirage-crypto code", etc.) -- accurate
attribution.
- CI workflow files (.github/workflows/*.yml, .cirrus.yml,
.test-mirage.sh) -- they reference upstream mirage-crypto package
names and would need separate cleanup; they're not exercised by
the monorepo's CI anyway.
Also includes mechanical ocamlformat reflows in aes_pure.ml,
config/cfg.ml, and test/dune that the harness ran after the
previous commit.
All 4068 tests still pass (C, native OCaml, and Node.js JS paths
all agree byte-for-byte on the differential test vectors).