+1 this is a much needed feature for us

This security bug is show stopper for us using circle ci. Can you please prioirise the solution higher.

Can CircleCI please comment on this request? Are there any access controls in the works for SSH access?

This is important and will ultimately prevent CircleCI from penetrating security conscious organizations.

Would definitely appreciate this feature, as SSH access is extremely useful during critical pipeline iteration, but is not appropriate for the vast majority of users with write access to the our repos.

Super important feature that is somehow not implemented yet. SSH build container access security is probably one of the toughest things for us when working with CircleCI.

In large companies, it's dangerous to let everyone with repo write permissions ssh into machine and printenv.Also, even after hide "Rebuild with SSH", how do we avoid people create their on ssh connection editing circleci config 🤔

lots of people discussed this critical issue, why circleci don't care about this?

Big security issue for such a long time, why haven't been fixed

This seems like something we should be able to do. enable/disable access to a user role/group to SSH into a job. We don't want users to be able to just print all env variables.