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
#516 and related seems to have removed publishing .deb releases to MSFT apt lists for things like Ubuntu, Debian, etc.
Without this, one cannot simply do apt install git-credential-manager for instance (e.g., after adding the appropriate sources).
As that is the preferred mode of install for several use cases (e.g., to avoid bloated and unnecessary dotnet dependencies), this leaves users with hand rolled scripts to install an unsigned package that has no "latest" version or regular updates.
This can lead to security concerns of its own in addition to any it is trying to mitigate by, for instance, acting as a replacement for ssh authentication.
Please consider adding support for this standard installation method back into the mix.
Thanks!
The text was updated successfully, but these errors were encountered:
Short of this, could you perhaps update your release pipeline to include symlinks to the .deb file without a version in the name?
Then one could at least issue a curl -L command pointing at https://github.com/git-ecosystem/git-credential-manager/releases/download/latest/gcm-linux_amd64.latest.deb
Feature description
#516 and related seems to have removed publishing
.deb
releases to MSFT apt lists for things like Ubuntu, Debian, etc.Without this, one cannot simply do
apt install git-credential-manager
for instance (e.g., after adding the appropriate sources).As that is the preferred mode of install for several use cases (e.g., to avoid bloated and unnecessary dotnet dependencies), this leaves users with hand rolled scripts to install an unsigned package that has no "latest" version or regular updates.
This can lead to security concerns of its own in addition to any it is trying to mitigate by, for instance, acting as a replacement for ssh authentication.
Please consider adding support for this standard installation method back into the mix.
Thanks!
The text was updated successfully, but these errors were encountered: