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.

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

Installing OSATE from the update site gives a warning about unsigned content #530

Closed
lwrage opened this issue Jan 14, 2015 · 4 comments
Closed

Comments

@lwrage
Copy link
Contributor

@lwrage lwrage commented Jan 14, 2015

We should sign the plugins.
child of #1570

@lwrage
Copy link
Contributor Author

@lwrage lwrage commented Oct 5, 2018

Signing plugins came up again when creating the STIG checklist.

@lwrage lwrage reopened this Oct 5, 2018
@lwrage lwrage added core next and removed next labels Oct 5, 2018
@lwrage lwrage added this to the 2.4 milestone Oct 17, 2018
@lwrage lwrage added next and removed backlog labels Oct 29, 2018
@lwrage
Copy link
Contributor Author

@lwrage lwrage commented Dec 7, 2018

@osate osate deleted a comment from lwrage Dec 20, 2018
@osate osate deleted a comment from lwrage Dec 20, 2018
@lwrage lwrage removed this from the 2.4.0 milestone Jan 23, 2019
@lwrage
Copy link
Contributor Author

@lwrage lwrage commented Feb 12, 2019

Waiting for IT department to get a code signing certificate.

@lwrage lwrage added in progress and removed next labels Feb 14, 2019
@lwrage lwrage removed the in progress label Jul 9, 2019
@lwrage lwrage added this to the 2.6.1 milestone Nov 6, 2019
@lwrage lwrage removed this from the 2.6.1 milestone Nov 6, 2019
@lwrage lwrage added this to the 2.6.0 milestone Nov 6, 2019
@lwrage
Copy link
Contributor Author

@lwrage lwrage commented Nov 6, 2019

We now sign the plugins.

@lwrage lwrage removed the core label Nov 6, 2019
@lwrage lwrage closed this Nov 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant