On Wed, Nov 10, 2010 at 10:39 AM, Thomas Bendler <thomas.bend...@cimt.de> wrote: > 2010/11/10 Richard Crowley <r...@rcrowley.org> >> >> [...] >> This works perfectly for PEM-formatted keys because they're ASCII, >> which is a subset of UTF-8. Binary keys are not (usually) valid UTF-8 >> and thus can't be crammed into a catalog without some encoding. > > And why don't you convert the key to a PEM key before putting it into > puppet? You can use OpenSSL to convert the binary key to a PEM key:
In my particular case because its unclear if ASCII encodings of trusted.gpg and trustdb.gpg are indeed possible. In the general case, even completely legitimate (and common) Latin-1 text files can cause Puppet problems because some Latin-1 bytes are not valid UTF-8. In my opinion, the content parameter of a file resource should be able to handle these cases. Richard -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
