# Cargo permissions to detect tampered dependecies

**URL:** <https://internals.rust-lang.org/t/cargo-permissions-to-detect-tampered-dependecies/10236>\
**Category:** cargo\
**Created:** [May 21, 2019, 9:14pm UTC](https://internals.rust-lang.org/t/cargo-permissions-to-detect-tampered-dependecies/10236 "2019-05-21T21:14:42Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![bascule](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/bascule/32/3057_2.png) [@bascule](https://internals.rust-lang.org/u/bascule)\
**Post date:** [May 22, 2019, 5:23pm UTC](https://internals.rust-lang.org/t/cargo-permissions-to-detect-tampered-dependecies/10236/7 "2019-05-22T17:23:19Z")

</div>

> [@fcsonline](#):
>
> > I believe this is why `unsafe` not only is but has to be one of the proposed permissions.
> 
> Exactly.

[My proposal](https://internals.rust-lang.org/t/crate-capability-lists/8933/2) leveraged `unsafe` (in conjunction with Cargo features) not as a "permission", but the fundamental modeling dimension around which all other permissions are based.

---

_[View the full topic](https://internals.rust-lang.org/t/cargo-permissions-to-detect-tampered-dependecies/10236)._