Mmm, my memory of using Git + https is that it requests a password each time you try to upload or download .. if there is an additional connector that gets around that, I'd still be interested in 'where' it's storing it's password.
The current pattern that *nix employs for user-space and applications is IMO flawed. Programs typically run in the same space in which secure files (keyfiles etc) exist, so any unscrupulous code could potentially (a) steal your credentials and (b) steal all your personal files...
Mmm, my memory of using Git + https is that it requests a password each time you try to upload or download .. if there is an additional connector that gets around that, I'd still be interested in 'where' it's storing it's password.The current pattern that *nix employs for user-space and applications is IMO flawed. Programs typically run in the same space in which secure files (keyfiles etc) exist, so any unscrupulous code could potentially (a) steal your credentials and (b) steal all your personal files...
The current pattern that *nix employs for user-space and applications is IMO flawed. Programs typically run in the same space in which secure files (keyfiles etc) exist, so any unscrupulous code could potentially (a) steal your credentials and (b) steal all your personal files...
