From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>,
cgit@lists.zx2c4.com, password-store@lists.zx2c4.com
Subject: [ANNOUNCE] git.zx2c4.com ssh host fingerprints changed
Date: Fri, 21 Jun 2019 11:53:31 +0200 [thread overview]
Message-ID: <CAHmME9pcw1Zx4dqKXB-Pt4jGOptjTqfELDF36LQV8+dxr1yOsA@mail.gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi contributors,
I've you push to git.zx2c4.com over ssh, you'll notice the ssh fingerprints
have changed. The valid new ones are:
SHA256:9os9asMrVeuWNlQmsmpA6bfcgFIwr5e0psYJYVBekUM
SHA256:frea6X2uzWJ3m0w5/qMKuXpbRgvvQIsFqotWCWkbR4M
SHA256:pDEtFepAZKaINDzfXLg/8F+4hf3tUvkz5C5j2i+NNwY
SHA256:5zPKp8sV2CnYDxBa9crqKXa2nJlPUyqW92SX7Xll7Ks
This message is signed with my usual GPG key.
Jason
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAl0MqQwACgkQSfxwEqXe
A67ssxAAu/TbRoQRfegcAf/ZdgPs6mI1aXKhwKUfnljqKzy5UgUq+UcT/iZHsZgL
gvnz0OwYaMsIMVdB+kWoCJwhbC1+Mrc+6rShbn9/kFVMVzEgE8Ut1dwvVM1ijRkj
q3BrriZwh3hwtpo8XAANursOUrOVoaY9UvpZ0187G5IB1n9mIbrtJkjQqjCF9/Tu
Vfx+khHdDe38onc7dFIPLFjhTiEQCxRwsOH53QNTyGjqCW9IjvYzhgfEOAo0KQHu
KnQpYWdhxeYohmEqGQxihPh3+8x+mbuk4+YS9Qd+Zbn+Yy9oC27TBtZwnzL0oHC/
cYlK51kkjEgsxtguXpVDm1xYnffMOkd5ECX7VYjqJE+V+cGBPhRqIu+D5lgI7tZE
dnfDotRUtXKjRIv04qYns7A2hQR8qh+PVG3Qcl5Tg6Jc3c02N1bm7JM5hfk09BDZ
lbAkvbIC3BsFfn+9ZIWF/7OqpJORxgGLToT9zjUagTC5PydiBO9RfybcUGQYHTiG
afiaexOlADKUn1u91wqq+VyX74JQ2tug11gWvLpc8ip/Bohqhx0Qb+jyGkpgOlrd
dxrd8WGNGIMKsEI7HISWBVh04MxxzH6i2ziiFS1y3dF4/olNu0zFJtaINIexHrS9
tGiwl2HM2fIXiabCmAhNEhhk4kqXZBkBLJU9DRAof/eVIp998AU=
=YEXK
-----END PGP SIGNATURE-----
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-06-21 9:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHmME9pcw1Zx4dqKXB-Pt4jGOptjTqfELDF36LQV8+dxr1yOsA@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=cgit@lists.zx2c4.com \
--cc=password-store@lists.zx2c4.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).