Thibault, Just for clarification, are you referring to the 0.5.1 RC that just came out approximately 12 hours ago (from this email)?
If so, that worked for me as instructed when starting with a new keychain and performing the import as instructed. If in fact for the prior, 0.5.0 release, I do remember grabbing a separate key that Tony, the RM, had elsewhere. --aldrin On Tue, Feb 23, 2016 at 6:04 AM, <[email protected]> wrote: > Hi, > > > > I’ve followed the procedure for checking signature of nifi 0.5.0 but the > key used to sign the release is a dev key (ID 3E91C23B) found on > https://dist.apache.org/repos/dist/dev/nifi/KEYS > <https://www.google.com/url?q=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fnifi%2FKEYS&sa=D&sntz=1&usg=AFQjCNEgvU4mEP40lThn9SjHdd0dV1u8FQ> > . > > Did I do something wrong ? > > > > Thanks, > > > > Thibault > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > >
