[pass] Killing plaintext git:// in favor of https:// cloning

Timmo Verlaan tverlaan at gmail.com
Fri Feb 26 20:02:40 CET 2016

How many of them are unique?
Every unique item in a week/month time could be considered an install and
will try another way to install it (via https). All the other ones are
basically syncing. You could whitelist them for plain git and blacklist
everything else. Then after some more months try to move them over too.

Ofcourse I would also understand if you value availability of password
store more then secure access (albeit via central cert auth).

My two cents :-)

Best regards,

On Fri, Feb 26, 2016, 16:50 Jason A. Donenfeld <Jason at zx2c4.com> wrote:

> Welp, in the last 2 days:
> krantz log # grep git-daemon messages | grep 'Connection from' | wc -l
> 3079
> So, I guess git:// will be sticking around, alas.
> _______________________________________________
> Password-Store mailing list
> Password-Store at lists.zx2c4.com
> http://lists.zx2c4.com/mailman/listinfo/password-store
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/password-store/attachments/20160226/079e7696/attachment.html>

More information about the Password-Store mailing list