<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/tools/write-ssh-key-fingerprints, branch 22.1</title>
<subtitle> (mirror of https://github.com/marekm72/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=22.1</id>
<link rel='self' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=22.1'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/'/>
<updated>2021-03-25T21:18:41+00:00</updated>
<entry>
<title>tools/write-ssh-key-fingerprints: do not display empty header/footer (#817)</title>
<updated>2021-03-25T21:18:41+00:00</updated>
<author>
<name>dermotbradley</name>
<email>dermot_bradley@yahoo.com</email>
</author>
<published>2021-03-25T21:18:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=13606a12054f4fcf1494ea3068db0640ae6cc3a3'/>
<id>urn:sha1:13606a12054f4fcf1494ea3068db0640ae6cc3a3</id>
<content type='text'>
When output of SSH host keys and/or SSH fingerprints are disabled for
all keys do not display headers and footers.

Prevent risk of message text being interpreted as "logger" option by
appending "--" to logger options.

Correct syslog output that was tagged with "ec2" regardless of DataSource
in use. Now use "cloud-init" tag instead.

Various "shellcheck" corrections.

Add testcase for disabled output of SSH host keys.</content>
</entry>
<entry>
<title>LICENSE: Allow dual licensing GPL-3 or Apache 2.0</title>
<updated>2016-12-22T22:04:28+00:00</updated>
<author>
<name>Jon Grimm</name>
<email>jon.grimm@canonical.com</email>
</author>
<published>2016-11-22T23:09:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=b2a9f33616c806ae6e052520a8589113308f567c'/>
<id>urn:sha1:b2a9f33616c806ae6e052520a8589113308f567c</id>
<content type='text'>
This has been a recurring ask and we had initially just made the change to
the cloud-init 2.0 codebase.  As the current thinking is we'll just
continue to enhance the current codebase, its desirable to relicense to
match what we'd intended as part of the 2.0 plan here.

- put a brief description of license in LICENSE file
- put full license versions in LICENSE-GPLv3 and LICENSE-Apache2.0
- simplify the per-file header to reference LICENSE
- tox: ignore H102 (Apache License Header check)

Add license header to files that ship.
Reformat headers, make sure everything has vi: at end of file.

Non-shipping files do not need the copyright header,
but at the moment tests/ have it.
</content>
</entry>
<entry>
<title>replace if..else based on presense of /etc/redhat-release with use of -s</title>
<updated>2012-12-04T15:04:14+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2012-12-04T15:04:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=75d991b2e807d8bf26a2b94791870b86c43a1c96'/>
<id>urn:sha1:75d991b2e807d8bf26a2b94791870b86c43a1c96</id>
<content type='text'>
instead of using '--stderr' on non-rhel based on the presense of
/etc/redhat-release, just use the short form '-s' everywhere.
</content>
</entry>
<entry>
<title>Check for running inside RHEL and adjust the logging options.</title>
<updated>2012-11-28T18:41:42+00:00</updated>
<author>
<name>Joshua Harlow</name>
<email>harlowja@yahoo-inc.com</email>
</author>
<published>2012-11-28T18:41:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=52a1884822ecb9474e12e6c16b62dbd0728a4a0e'/>
<id>urn:sha1:52a1884822ecb9474e12e6c16b62dbd0728a4a0e</id>
<content type='text'>
It seems like at least RHEL does not have the "--stderr" option
but instead only supports the short version "-s" so add a check 
that will switch from the long version to the short version when
RHEL is detected.

LP: #1083715</content>
</entry>
<entry>
<title>write-ssh-key-fingerprints: do not send HOST KEYS through logger</title>
<updated>2012-09-24T18:48:44+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2012-09-24T18:48:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=ad22d407085009dcd1c860185e29f21858cdd968'/>
<id>urn:sha1:ad22d407085009dcd1c860185e29f21858cdd968</id>
<content type='text'>
In the previous commit to htis file I had wrapped the writing of
'BEGIN SSH HOST KEY KEYS' to go through logger.

This would cause the keys to be prefixed with 'ec2:' which, previously they
were not.  That would break existing users *and* make it more difficult to
consume that data, which was explicitly added to be easy to consume.
</content>
</entry>
<entry>
<title>send stderr from write-ssh-key-fingerprints to stdout</title>
<updated>2012-09-24T18:40:41+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2012-09-24T18:40:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=0a4f91c84c096e0b0df2e5a1d42c38609ae7fa93'/>
<id>urn:sha1:0a4f91c84c096e0b0df2e5a1d42c38609ae7fa93</id>
<content type='text'>
This changes all output write-ssh-key-fingerprints to go to its
stdout by redirecting stderr to stdout. 

The reason for this is that cc_keys_to_console.py was swallowing stderr
and not replaying it to /dev/console.

Ideally, we'd have a way in 'util.subp' to do effectively the same thing
as we're doing here in the shell script.

LP: #1055688</content>
</entry>
<entry>
<title>output public ssh host keys to console on boot (LP: #893400)</title>
<updated>2011-12-20T05:13:07+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2011-12-20T05:13:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=59d4175c87b86dcee461ba4b67dba2b546d65728'/>
<id>urn:sha1:59d4175c87b86dcee461ba4b67dba2b546d65728</id>
<content type='text'>
Currently cloud-init writes something like this to console output:
  ec2: #############################################################
  ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
  ec2: 2048 78:ae:f3:91:04:6f:8d:ee:ef:e1:2d:72:83:6a:d0:82  root@h (RSA)
  ec2: 1024 d3:b6:32:64:22:d4:43:05:f9:25:b4:f3:65:4e:e2:51  root@h (DSA)
  ec2: -----END SSH HOST KEY FINGERPRINTS-----
  ec2: #############################################################

the key fingerprints are useful for humans to read, but not so useful
for machines, as you cannot populate a KnownHostsFile (~/.ssh/known_hosts)
from the data there.

This change adds output like:
  -----BEGIN SSH HOST KEY KEYS-----
  ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdH......STI= root@h
  ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDYRIQe6m......tWF3 root@h
  -----END SSH HOST KEY KEYS-----

Those lines can easily be grabbed and appended to a known_hosts file.
</content>
</entry>
<entry>
<title>Make the types of SSH keys to generate configurable</title>
<updated>2011-10-30T22:00:41+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2011-10-30T22:00:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=a2aa4805f018a9d8ff8baff7c2f6cb91e532c4d2'/>
<id>urn:sha1:a2aa4805f018a9d8ff8baff7c2f6cb91e532c4d2</id>
<content type='text'>
Notes:
 * This also makes cc_ssh.py *not* write ssh keys to the console.
   That means that if keys-to-console is configured off, nothing will
   write the keys to the console.
 * I removed Garret's use of xargs, replacing with a shell for loop
   in write-ssh-key-fingerprints.

taken from
git://pkgs.fedoraproject.org/cloud-init.git
commit 87f33190f43d2b26cced4597e7298835024466c2
Author: Garrett Holmstrom &lt;gholms@fedoraproject.org&gt;
Patch8: cloud-init-0.6.2-sshkeytypes.patch
</content>
</entry>
<entry>
<title>move writing of ssh key fingerprints to a separate tool</title>
<updated>2011-01-19T03:49:51+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2011-01-19T03:49:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=8fbafbddbfbdddcb0a3e087185e432973ac73baa'/>
<id>urn:sha1:8fbafbddbfbdddcb0a3e087185e432973ac73baa</id>
<content type='text'>
This will allow this code to be called more easily elsewhere.
I'm considering having the "all the way up" message contain fingerprints
so that they're more or less guaranteed to get to the console where
the user could see them.
</content>
</entry>
</feed>
