I've recently discovered that it's not possible to add ssh options to ssh key, if they contain double quotes, e.g.:
vyos@vyatta2# set system login user root authentication public-keys mick@mick-office options 'environment="GIT_AUTHOR_EMAILemail@example.com",environment="GIT_AUTHOR_NAME=Mihail Vasilev"' Cannot use the double quote (") character in a value string Value validation failed Set failed
I've tried to add html entities like " instead, but get into faulty .ssh/authorized_keys - it just receives " as is.
It seems to me that it would be handy to add html entities encoding here (as it goes for dhcp server options) and should not harm existing systems.
I think, I can do it quite fast myself, but I think that this feature should be interesting for other community members.
What I'm trying to obtain by this feature - be able to put config.boot under version control AND minimize administration effort required to maintain accountability of engineers.