gmail.com>
<20120328142411.GL4154@???>
<CAAiW_GnLUFRhGUeyjpXRsT8ki=PNHEi09Bp6Omto0X3ie58SgQ@???>
<CAAiW_GmdpdKevCUX93HVo0GxGPGbAWExJbEVv-2cRbMRtWRq=A@???>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-ripemd160;
protocol="application/pgp-signature"; boundary="YIwHDYD8sUXtBKvt"
Content-Disposition: inline
In-Reply-To: <CAAiW_GmdpdKevCUX93HVo0GxGPGbAWExJbEVv-2cRbMRtWRq=A@???>
OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc
X-URL: http://strugglers.net/wiki/User:Andy
User-Agent: Mutt/1.5.18 (2008-05-17)
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Fri,
30 Mar 2012 02:26:02 +0000
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: andy@???
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
spamd2.lon.bitfolk.com
X-Spam-Level:
X-Spam-ASN:
X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS shortcircuit=no
autolearn=disabled version=3.3.1
X-Spam-Report: * -0.0 NO_RELAYS Informational: message was not relayed via SMTP
X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:14:11 +0000)
X-SA-Exim-Scanned: Yes (on mail.bitfolk.com)
Subject: Re: [bitfolk] Enabling Monkeysphere
X-BeenThere: users@???
X-Mailman-Version: 2.1.11
Precedence: list
List-Id: Users of BitFolk hosting <users.lists.bitfolk.com>
List-Unsubscribe: <https://lists.bitfolk.com/mailman/options/users>,
<mailto:users-request@lists.bitfolk.com?subject=unsubscribe>
List-Archive: <http://lists.bitfolk.com/lurker/list/users.html>
List-Post: <mailto:users@lists.bitfolk.com>
List-Help: <mailto:users-request@lists.bitfolk.com?subject=help>
List-Subscribe: <https://lists.bitfolk.com/mailman/listinfo/users>,
<mailto:users-request@lists.bitfolk.com?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 02:26:04 -0000
--YIwHDYD8sUXtBKvt
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi Murray,
On Thu, Mar 29, 2012 at 04:16:02PM +0100, Murray Crane wrote:
> Is there any further guidance on how to get my
> *.console.bitfolk.comcert/key so I can include that in all the fun
> (other than the wiki)?
If we're talking about:
https://tools.bitfolk.com/wiki/Verifying_BitFolk%27s_SSH_fingerprints
then you'll see the problem of console host vs. real host. The
article states that BitFolk is not going to publish the keys for
every console.bitfolk.com hostname, but then incorrectly goes on to
state that you could publish them yourself.
You obviously can't publish them yourself because
whatever.console.bitfolk.com is actually just a CNAME for some VPS
host that you have no admin access to, and admin access would be
required to do the:
# monkeysphere-host import-key blah..
I will correct the article.
What I would suggest, if you want to be able to verify the console
host using Monkeysphere, is that you do it in a two stage process.
For example, if your account name were "ruminant", you could find
your VPS host like so:
$ host ruminant.console.bitfolk.com
ruminant.console.bitfolk.com is an alias for console.president.bitfolk.=
com.
console.president.bitfolk.com is an alias for president.bitfolk.com.
president.bitfolk.com has address 85.119.80.16
president.bitfolk.com has IPv6 address 2001:ba8:0:1f1::6
You could then:
$ ssh ruminant@???
