-
-
Replying to @rootkovska
@rootkovska@mtrojnar look at "man sshd". ForceCommand in the sshd config or command="command" in authorized_keys1 reply 0 retweets 1 like -
Replying to @tehjh
@rootkovska@mtrojnar ssh is usually used that way as transport for RW git access. does not imply shell access.1 reply 0 retweets 0 likes -
Replying to @tehjh1 reply 0 retweets 1 like
-
Replying to @rootkovska
@rootkovska@mtrojnar maybe some setups do it that way, but e.g. with gitolite, the authorized_keys looks like this:https://gist.github.com/thejh/d035bdcb4cb4d754181b …1 reply 1 retweet 4 likes -
Replying to @rootkovska
@rootkovska@tehjh When I suggested ssh, I (obviously to me) implied the per-key forced commands and the full set of no-*. I use this daily.1 reply 0 retweets 2 likes -
Replying to @rootkovska1 reply 0 retweets 1 like
-
Replying to @rootkovska
@rootkovska@solardiz I assume that the ssh devs know that adding new important opt-out flags is dangerous and avoid it. /cc@damienmiller2 replies 1 retweet 2 likes
@rootkovska @solardiz @damienmiller I guess an "opt-out from all features" or a "treat all features as opt-in" flag would be nice to have
-
-
Replying to @tehjh
@tehjh@rootkovska@solardiz done - it will be in the next OpenSSH release (7.2) https://anongit.mindrot.org/openssh.git/commit/?id=383f10fb84a0fee3c01f9d97594f3e22aa3cd5e0 …4 replies 19 retweets 34 likes -
Replying to @damienmiller
@damienmiller@rootkovska@solardiz cool, thanks! :)0 replies 0 retweets 1 like
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.