Audiences
Security researchers:
“Help define the threat model for HDF5: malformed files, metadata trust boundaries, plugin loading, supply-chain risk, and file-format-aware validation.”
Administrators / HPC centers:
“What should your site do when users bring arbitrary HDF5 files, filters, VOL connectors, VFDs, and long-lived data into shared infrastructure?”
Developers / maintainers:
“Machine-readable HDF5 specifications, GNU poke pickles, validation tools, conformance testing, fuzzing targets, and safer extension mechanisms.”
Users / scientists:
“What do safety, security, and privacy mean when your experiment, simulation, model, or archive is stored in HDF5?”
Digital librarians / archivists:
“HDF5 as long-lived scientific data: preservation, metadata exposure, trust, validation, repair, and evidence that a file means what it claims to mean.”