View Single Post
Old 02-09-2013, 02:04 AM   #351
DuckieTigger
Wizard
DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.DuckieTigger ought to be getting tired of karma fortunes by now.
 
DuckieTigger's Avatar
 
Posts: 1,137
Karma: 23467218
Join Date: Dec 2011
Device: Kindle Paperwhite
Quote:
Originally Posted by twobob View Post
sigs might need rebundling as asc.

Feedback appreciated.
Since you asked for feedback. The .sig files for the signature works just fine. To get a fully green result I did certify your public key in my keyring. So now you are trusted. The .gpg files you bundled into it suffer from the same thing they had in the previous verions of KUAL - gpg claims they are encrypted something, but they cannot be decrypted with your public key (no data). Only those 2 .sig files are needed to verify that both .azw files are made by you (or rather approved by you). Since the signatures are not very big, rebundling them, and only them as .asc would be nicer than .sig. Only difference between sig and asc is binary file (.sig) versus ascii text file (.asc).



Hope that helps.
DuckieTigger is offline   Reply With Quote