d6/1cf3c030af05bca4ffe70ef04de294df73c027

   1 Return-Path: <cworth@cworth.org>\r
   2 X-Original-To: notmuch@notmuchmail.org\r
   3 Delivered-To: notmuch@notmuchmail.org\r
   4 Received: from yoom.home.cworth.org (unknown [10.0.0.1])\r
   5  (Authenticated sender: cworth)\r
   6  by arlo.cworth.org (Postfix) with ESMTPSA id 24D6D6DE1A0D\r
   7  for <notmuch@notmuchmail.org>; Fri,  3 Apr 2015 16:38:38 -0700 (PDT)\r
   8 Received: by yoom.home.cworth.org (Postfix, from userid 1000)\r
   9  id 1214FC40068; Fri,  3 Apr 2015 16:38:38 -0700 (PDT)\r
  10 From: Carl Worth <cworth@cworth.org>\r
  11 To: notmuch@notmuchmail.org\r
  12 Subject: Re: Website and mailing list are hopefully back now\r
  13 In-Reply-To: <87mw2o4x77.fsf@yoom.home.cworth.org>\r
  14 References: <87mw2o4x77.fsf@yoom.home.cworth.org>\r
  15 User-Agent: Notmuch/0.18.2 (http://notmuchmail.org) Emacs/23.4.1\r
  16  (x86_64-pc-linux-gnu)\r
  17 Date: Fri, 03 Apr 2015 16:38:37 -0700\r
  18 Message-ID: <87ego04waq.fsf@yoom.home.cworth.org>\r
  19 MIME-Version: 1.0\r
  20 Content-Type: multipart/signed; boundary="=-=-=";\r
  21  micalg=pgp-sha512; protocol="application/pgp-signature"\r
  22 X-BeenThere: notmuch@notmuchmail.org\r
  23 X-Mailman-Version: 2.1.18\r
  24 Precedence: list\r
  25 List-Id: "Use and development of the notmuch mail system."\r
  26  <notmuch.notmuchmail.org>\r
  27 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
  28  <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
  29 List-Archive: <http://notmuchmail.org/pipermail/notmuch/>\r
  30 List-Post: <mailto:notmuch@notmuchmail.org>\r
  31 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
  32 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
  33  <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
  34 X-List-Received-Date: Fri, 03 Apr 2015 23:38:38 -0000\r
  35 \r
  36 --=-=-=\r
  37 \r
  38 On Fri, Apr 03 2015, Carl Worth wrote:\r
  39 > The notmuchmail.org server experienced a catastrophic failure a few days\r
  40 > ago. I gave up on getting access to that server anymore, and have\r
  41 > instead brought things back up on a separate server that I had\r
  42 > available, (and to which I have actual, physical access this time).\r
  43 \r
  44 Oh, and by the way, when you use ssh to the new server from an account\r
  45 that had connected to the old server, you'll likely get the scary\r
  46 warning that the ssh host key has changed.\r
  47 \r
  48 Here is the fingerprint of the RSA key that you should expect to get:\r
  49 \r
  50         1f:64:19:21:50:8f:1a:72:bc:69:45:8c:25:c5:71:7a\r
  51 \r
  52 With that fingerprint, you can assume that the key change isn't due to a\r
  53 man-in-the-middle attack and follow the instructions on removing the\r
  54 old key.\r
  55 \r
  56 -Carl\r
  57 \r
  58 --=-=-=\r
  59 Content-Type: application/pgp-signature\r
  60 \r
  61 -----BEGIN PGP SIGNATURE-----\r
  62 Version: GnuPG v1\r
  63 \r
  64 iQIcBAEBCgAGBQJVHyR9AAoJEGACM7qeVNxhQs8QAIjnOdAsWhGjGSmADnOiwqQp\r
  65 982XMcc1XT5vInMPUaRWZL+LMecTDTeX+Ybx1Rb5iW2/h5xwtvHJnUe2QY4Y5/rm\r
  66 YffuT1+Q/5tL53LOBOrI4/2d2oI86m7/ZjTZi20ERw59JsimgeWfb8NQfeC6ceNQ\r
  67 BF8KjIu6fgLjsbrLKJYQW7xFXUo+7Z1HrLrK1MwfZC8VqHTNikYLcsV78noFX303\r
  68 hedKNyaqURfghRV+42S6P+qfWphTbjeFVS91mIukA+YDJNfyZ++KMq6fhZ/OLi5Z\r
  69 MhnDIJw+gMYcb7pgOlz6ND83o1ydMulwFWTanvgMqBAiV25u4FBZlBSdJMT3577R\r
  70 dmE4GZYH0xXSGvmGRGPNEjJmog4VuiCf4OlOBg13x6cD357L+EbF5023GK+dPM/T\r
  71 v7rNAaf1Xloidg59+JC09gHpOm5htBYzP4Zp+2F6zl/AB8JkY4GXBchjg21s22h3\r
  72 h1eFCtjCnvbcGCCbLnCQWws05t0wU3ukZSIRgYkV3z7OLWlehHldSmER37OBoFhY\r
  73 aZh+XpzJZok6XXpiOowAKOH9x7Ls7A79w22U23urW2qNk4kq2NaKQ30ZEd7BYBTz\r
  74 SnknJAi4KSujLBwQmHSOZJjAtnFf2bwUn8yS4RVNCwo6uC/vEPm2sKsk0AvxEuBM\r
  75 z1Urf1RIpHy1phBhn6PV\r
  76 =r2Bl\r
  77 -----END PGP SIGNATURE-----\r
  78 --=-=-=--\r