Page MenuHomePhabricator

Deprecate and remove 'bastion-restricted' hosts
Open, LowPublic

Description

The restricted bastion was created long ago back when we recommended ssh agent forwarding for VM access. Out of an abundance of caution, we had people with root keys forward through a separate bastion to avoid the risk of key sniffing.

We no longer use forwarding, and haven't been especially compulsive about segregating ssh traffic between the different bastions. We should just eliminate the special bastions and standardize on everyone using standard public bastions; this will slightly simplify our setup and also ensure that admins are drinking the same champagne as our users.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

FWIW I see some value in having the cumin authorized_keys entries have an IP restriction on a host not accessible to most people, but otherwise agree with the proposal.

FWIW I see some value in having the cumin authorized_keys entries have an IP restriction on a host not accessible to most people, but otherwise agree with the proposal.

Can you tell me more about what this would look like? Do you mean that there would be a 'bastion-cumin' host for cumin access, and then we retool all the pam restrictions to permit bastion and root logins only on that host?