Re: Handling apt sources with ltsp-build-client

I understand that there are many problems with copying the sources,
but is there any problem with copying all the server keys?

Suppose there was a '--copy-apt-keys' parameter that would do
  apt-key exportall | chroot $ROOT apt-key add -

Where would that hurt? The sysadmin already trusts those keys on the
server, so if he uses that parameter to declare that he wants to also
trust them on the clients, what could go wrong?

Of course, the sysadmin would ONLY specify the mirrors he actually
wanted, not all the ones whose keys are in the apt keyring. E.g.:
  --extra-mirror "http://ppa.launchpad.net/stgraber/ppa/ubuntu"

The implementation is trivial, 5-6 lines in 001-apt-keys...

-Alkis


Στις 21-01-2010, ημέρα Πεμ, και ώρα 16:59 -0500, ο/η Adam J. Lincoln
έγραψε:
>     But this brought up another point: these PPAs are signed, and the
> client need to know about this via apt-key.  There is --apt-keys, but
> afaict this requires that the key be in a file, and that filename is
> given as the parameter.  This doesn't seem right to me - it ought to at
> least take the output of 'apt-key export', or even better, a key id.



------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net