Issue #407 has been updated by Samer -. I tried to approach this but I got stuck. I thought we should sign the packages with a generic key for Kune (like Ubuntu does) so I created a GPG RSA key for kune@op just for signing (not for encrypting). However, later the instructions say that, in order to do it automatically: "your packages will be automatically signed as long as the name and email address in your package’s changelog file are the same as that of the GPG key you created" As the changelog usually has vjrj's name and email, then I wonder that, to avoid complications and being able to do it automatically, we should sign the package with his key. * If we do, then I'd discard the created Kune key and wait till vjrj does it. * If we don't, then i'd continue working on this with the Kune key I created (uploading it to the key repository, signing, etc). ---------------------------------------- Defect #407: Sign deb package http://redmine.ourproject.org/issues/407#change-525 * Author: Samer - * Status: New * Priority: Normal * Assignee: * Category: Others * Target version: * Resolution: * Tags: ---------------------------------------- The deb package is distributed unsigned. The APT repository and the Debian packages should be signed. Ref: http://blog.mycrot.ch/2011/04/26/creating-your-own-signed-apt-repository-and... -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://redmine.ourproject.org/my/account