<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/src/migration-scripts/ssh/1-to-2, branch 1.3.5</title>
<subtitle>VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-1x.git/atom?h=1.3.5</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=1.3.5'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2022-02-28T13:30:57+00:00</updated>
<entry>
<title>ssh: T4273: bugfix cipher and key-exchange multi nodes</title>
<updated>2022-02-28T13:30:57+00:00</updated>
<author>
<name>Christian Poessinger</name>
<email>christian@poessinger.com</email>
</author>
<published>2022-02-28T13:28:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=bdd5fe45dc8eb2466889cd7bc2b4c6a5ce290dde'/>
<id>urn:sha1:bdd5fe45dc8eb2466889cd7bc2b4c6a5ce290dde</id>
<content type='text'>
After hardning the regex validator to be preceeded with ^ and ending with $
it was no longer possible to have a comma separated list as SSH ciphers. The
migrations cript is altered to migrate the previous comma separated list
to individual multi node entries - cipher and key-exchange always had been
multinodes - so this just re-arranges some values and does not break CLI
compatibility

(cherry picked from commit 61fa1c95164e4222e79b078b1a796f41397e0ee3)
</content>
</entry>
<entry>
<title>ssh: T2691: bugfix loglevel config migration</title>
<updated>2020-07-07T17:05:00+00:00</updated>
<author>
<name>Christian Poessinger</name>
<email>christian@poessinger.com</email>
</author>
<published>2020-07-07T17:05:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=d0261c4daf31bd7fc05643e86660caee9f0442c5'/>
<id>urn:sha1:d0261c4daf31bd7fc05643e86660caee9f0442c5</id>
<content type='text'>
When migrating the conf from VyOS 1.2 to 1.3 a configuration error could appear
if the user specified "info" as loglevel instead of "INFO". There was no input
validation done in 1.2 but this is now enforced in 1.3.

In VyOS 1.3 loglevel will be always lowercase on the CLI and when migrating the
config this is transformed. Also VyOS 1.2 accpeted any arbitrary loglevel. If
an invalid loglevel is found it will be set to info.
</content>
</entry>
</feed>
