Lib.rs

› hostname › Reviews

These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.

The current version of hostname is 0.4.0.

0.3.0 (older version) Rating: Positive Thoroughness: Low Understanding: Medium

Approved without comment by dpc on 2020-02-24

0.2.0 (older version) Rating: Negative Thoroughness: Medium Understanding: Medium

by kornelski on 2023-09-19

Show review…

Forgets to set NUL string terminator on Windows

0.1.5 (older version) Rating: Negative Thoroughness: High Understanding: High

by HeroicKatora on 2019-08-31

No references and not compliant to all possible implementations of the POSIX interfaces it utilizes. Manifestation of the unsafety requires the hostname to be set to a 255 byte string by the machine operator and is thus not directly exploitable, especially on Linux or glibc where it is impossible to configure the system into such a state.

This is not meant to assign blame towards the author, Crate repository is properly abandoned and reverse dependencies should switch to another implementation.

These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.

The current version of hostname is 0.4.0.

0.3.1 (older version) unknown

From kornelski/crev-proofs copy of salsa.debian.org.

Only in debcargo (unstable). Changelog:

  • Team upload.
  • Package hostname 0.3.1 from crates.io using debcargo 2.6.1
  • Update copyright file.
  • Bump dev-depends on version-sync.

cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.

safe-to-run

This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…

does-not-implement-crypto (implies crypto-safe)

Inspection reveals that the crate in question does not attempt to implement any cryptographic algorithms on its own.

Note that certification of this does not require an expert on all forms of cryptography: it's expected for crates we import to be "good enough" citizens, so they'll at least be forthcoming if they try to implement something cryptographic. When in doubt, please ask an expert.

crypto-safe
Implied by other criteria

All crypto algorithms in this crate have been reviewed by a relevant expert.

Note: If a crate does not implement crypto, use does-not-implement-crypto, which implies crypto-safe, but does not require expert review in order to audit for.

unknown

May have been packaged automatically without a review

Lib.rs has been able to verify that all files in the crate's tarball, except Cargo.lock, are in the crate's repository. Please note that this check is still in beta, and absence of this confirmation does not mean that the files don't match.

Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories, so there is a possibility that published crates have a misleading repository URL, or contain different code from the code in the repository.

To review the actual code of the crate, it's best to use cargo crev open hostname. Alternatively, you can download the tarball of hostname v0.4.0 or view the source online.