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

Installer Code Signing #1879

Closed
stefan-kolb opened this issue Aug 29, 2016 · 11 comments
Closed

Installer Code Signing #1879

stefan-kolb opened this issue Aug 29, 2016 · 11 comments
Assignees
Milestone

Comments

@stefan-kolb
Copy link
Member

No description provided.

@stefan-kolb
Copy link
Member Author

@koppor Any news?

@stefan-kolb
Copy link
Member Author

This certificate will only work for Windows? As we don't have an Apple code signing certificate?!

@stefan-kolb
Copy link
Member Author

@stefan-kolb stefan-kolb modified the milestones: v3.8, v3.7 Nov 7, 2016
@koppor
Copy link
Member

koppor commented Nov 15, 2016

Note that only one encryption key can be stored per time: https://docs.travis-ci.com/user/encrypting-files/#Encrypting-multiple-files

@stefan-kolb
Copy link
Member Author

stefan-kolb commented Nov 28, 2016

openssl aes-256-cbc -e -in jabref-2016.p12 -out jabref-2016.p12.enc -k $KEY

@stefan-kolb
Copy link
Member Author

@stefan-kolb
Copy link
Member Author

@koppor
Copy link
Member

koppor commented Nov 28, 2016

Thanks to @stefan-kolb, a test build is available at https://builds.jabref.org/cert/

@matthiasgeiger
Copy link
Member

Is working only partially...:

grafik

The UAC dialog shown after clicking "Trotzdem ausführen" looks good (except that only Oliver Kopp, Open Source Developer is mentioned but not directly JabRef 😕

@koppor
Copy link
Member

koppor commented Nov 28, 2016

Mentioning me instead of JabRef is the condition of the Certum Open Source Code Signing.

Quoting from their conditions, I received via Email:

OPEN SOURCE CODE SIGNING CERTIFICATES MAY BE ISSUED ONLY TO PRIVATE INDIVIDUALS !

When issuing a certificate the "Open Source Developer" term is automatically added to the "CN" (Common Name) field. This is a necessary condition to obtain a certificate.

@stefan-kolb
Copy link
Member Author

stefan-kolb commented Nov 28, 2016

Yeah, I don't see why this means it is only partially working. The name is intentional.
Don't know why it is recognized as threat tho...

stefan-kolb added a commit that referenced this issue Dec 2, 2016
* Typo

* Set certificate file paths

* Changelog
Siedlerchr added a commit that referenced this issue Dec 2, 2016
* upstream/master:
  Ignore failing test
  Replace usage of Threads and priorities with thread pool (#2304)
  Class variable declarations and method declarations are now separated by one line
  Disable joining of wrapped lines
  Installer Code Signing #1879 (#2320)
  Add bibtex key deviation check (#2328)
  Update mockito-core (2.2.21 -> 2.2.26) and wiremock (2.3.1 -> 2.4.1)
  Fix opening of preference dialog with Java 9 (#2329)
  Add longer explanation for ID-based entry generation. (#2330)
  Add DOI integrity check (#2327)
  New strings translated (#2325)
  Fix exporting via commandline in no gui mode (#2316)
  Cleanup EMACS code (#2317)
  Update mockito-core from 2.2.15 to 2.2.21
  Fix typo in comment
  Updated JabRef_tr.properties (#2315)

# Conflicts:
#	CHANGELOG.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants