Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Key check #18

Closed
WaaromZoMoeilijk opened this issue Jan 21, 2017 · 6 comments
Closed

Key check #18

WaaromZoMoeilijk opened this issue Jan 21, 2017 · 6 comments
Assignees
@WaaromZoMoeilijk
Labels
help wanted

Comments

@WaaromZoMoeilijk
Copy link
Collaborator 

gpg: directory `/root/.gnupg' created
gpg: new configuration file `/root/.gnupg/gpg.conf' created
gpg: WARNING: options in `/root/.gnupg/gpg.conf' are not yet active during this run
gpg: keyring `/root/.gnupg/secring.gpg' created
gpg: keyring `/root/.gnupg/pubring.gpg' created
gpg: requesting key A724937A from hkp server p80.pool.sks-keyservers.net
gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: key A724937A: public key "Nextcloud Security <[email protected]>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
gpg: Signature made Sun 15 Jan 2017 04:07:44 PM UTC using RSA key ID A724937A
gpg: Good signature from "Nextcloud Security <[email protected]>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 2880 6A87 8AE4 23A2 8372  792E D758 99B9 A724 937A
Package OK!

@enoch85
@WaaromZoMoeilijk WaaromZoMoeilijk added this to the 1.1 milestone Jan 21, 2017
@WaaromZoMoeilijk WaaromZoMoeilijk self-assigned this Jan 21, 2017
@enoch85
Copy link
Member

enoch85 commented Jan 22, 2017

Yes? It's working. :)

@WaaromZoMoeilijk
Copy link
Collaborator Author

Yeah it works but these messages shouldn't be seen in such a check, I assume, right?

gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.

@enoch85
Copy link
Member

enoch85 commented Jan 23, 2017

cc @LukasReschke

@WaaromZoMoeilijk WaaromZoMoeilijk modified the milestones: 1.2, 1.1 Jan 28, 2017
@WaaromZoMoeilijk
Copy link
Collaborator Author

@LukasReschke Any update please, issue still persist. (not really an issue but I don't think it should be there)

@WaaromZoMoeilijk WaaromZoMoeilijk removed this from the 1.2 milestone Feb 12, 2017
@enoch85
Copy link
Member

enoch85 commented May 17, 2017

This is fixed now in lib.sh there's a function.

@WaaromZoMoeilijk
Copy link
Collaborator Author

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@WaaromZoMoeilijk WaaromZoMoeilijk

Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@enoch85 @WaaromZoMoeilijk