4 ms·
Whats to stop malicious git repos changing an alias after you have already added it to your freshrc? I think locking to a specific git ref needs to be top prior
by lukeholder 14y ago
Whats to stop malicious git repos changing an alias after you have already added it to your freshrc? I think locking to a specific git ref needs to be top priority.
- twe4ked 14y agoAbsolutely. This is on the road map (https://github.com/freshshell/fresh/issues/11 https://github.com/freshshell/fresh/issues/11). At the moment running `fresh update` is the only way to update the source repos. I realise this isn't ideal, but we never update repos without you knowing.
- nathanaelkane 14y agoI like the idea of locking an entry to a git ref, I've created a ticket on the issue tracker: https://github.com/freshshell/fresh/issues/25 https://github.com/freshshell/fresh/issues/25. Edit: woops it was already a ticket, closed mine.
- jasoncodes 14y agoLocking to a specific git reference (https://github.com/freshshell/fresh/issues/11 https://github.com/freshshell/fresh/issues/11) has been implemented. You can now use `--ref` to lock to a particular git reference. `fresh update` will grab the new version.