You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this is going to work fine until sigstore-python wants to cache or store other application data... should we re-add that "tuf" component in there now or only solve that problem when it becomes an issue?
The text was updated successfully, but these errors were encountered:
Hmm -- I changed that as part of the appdirs refactor, although I can't remember exactly why.
I'm probably missing it, but I don't see how the current scheme poses a challenge for other caching. If we were to e.g. add an HTTP cache, I'd expect the structure to be:
Sure, conflicts would be exceptional, it's not something I would expect to happen without some ill intent... but if in the future custom sigstore instances involve a custom TUF repository, then the repository URLs (and thus directory names) in the client likely become user controlled to some extent.
It doesn't look a like a big deal but it smells just slightly wrong :)
I noticed that during the refactoring of #351 the directories changed from:
to
this is going to work fine until sigstore-python wants to cache or store other application data... should we re-add that "tuf" component in there now or only solve that problem when it becomes an issue?
The text was updated successfully, but these errors were encountered: