Re:OpenSSH: client bug CVE-2016-0777
by __jal on Thursday January 14, 2016 @02:28PM
(#10903761)
It does depend. This may be leftover behavior from my contract days, but I've always had at least one key per entity with which I interact[1].
The reasoning is that it is far easier for me (or the entity, but that's a bit different) to delete one keyfile to sever access than it is for me to rekey everything else. I don't want access to things I'm not actively engaged with - compromises happen, even to engineers' laptops, and that conversation with former employers is too much like calling up your exes to tell them about a VD test result for my comfort.
As far as it being digital identification, lots of companies have IDs separate from your DL/passport. This is usually because the company ID provides access to something your other ID doesn't. Same principle.
[1] There are lots reasons to have lots of different keys, and only having one per entity is pretty rare for me.
The reasoning is that it is far easier for me (or the entity, but that's a bit different) to delete one keyfile to sever access than it is for me to rekey everything else. I don't want access to things I'm not actively engaged with - compromises happen, even to engineers' laptops, and that conversation with former employers is too much like calling up your exes to tell them about a VD test result for my comfort.
As far as it being digital identification, lots of companies have IDs separate from your DL/passport. This is usually because the company ID provides access to something your other ID doesn't. Same principle.
[1] There are lots reasons to have lots of different keys, and only having one per entity is pretty rare for me.