[Infrastructures] isconf v4 problem

[Ryan Nowakowski]

--YiEDa0DAkWCtVeE4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Sep 15, 2006 at 11:11:32PM -0700, Steve Traugott wrote:
> I'm thinking of replacing the UDP broadcasts with an ssh-based mesh --
> this would require that people manage ssh keys, authorized_keys, and a
> local isconf user in /etc/password on each machine.  This is instead
> of the TCP mesh I haven't had time to write; in the latter, people
> would have had to manage PGP keys and/or HMAC secrets anyway -- in
> retrospect, ssh is probably simpler and better understood both
> operationally and security-wise. =20

SSH is definitely the way to go.  I've been struggling with rolling my
own inter-node communication mechanism and I have ended up back at SSH.

--YiEDa0DAkWCtVeE4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFFEbfq6ZA8+1/wXqMRArJRAJwKU+AZzltPc90Kcg2ZCysp/38J/wCfQ4Y3
UUxY3FtL8asu62W8fliZJoU=
=75tv
-----END PGP SIGNATURE-----

--YiEDa0DAkWCtVeE4--