Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Dependency fencing #20

Open
cdstanford opened this issue Apr 10, 2023 · 0 comments
Open

Dependency fencing #20

cdstanford opened this issue Apr 10, 2023 · 0 comments
Labels
roadmap-unplanned Ideas for future work

Comments

@cdstanford
Copy link
Collaborator

cdstanford commented Apr 10, 2023 •
edited
Loading

another idea to support: fencing dependencies -- crate U is restricted and can only be used by certain trusted dependencies X, Y, Z

in the workspace Cargo.toml, say "this dep can only be used by crate X, Y, Z"
(you can do this as a postprocessing step. maybe we should just make cargo fence for this down the road)

e.g.:

we're pulling in yubikey which pulls in pcsc-sys; this is only for thing son the cli side but we have a workspace where our server-side stuff lives too (but should never ever use this)
@cdstanford cdstanford added the enhancement New feature or request label Apr 10, 2023
@cdstanford cdstanford added roadmap-unplanned Ideas for future work and removed enhancement New feature or request labels May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
roadmap-unplanned Ideas for future work
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cdstanford