mir/libreoffice
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify the different kinds of signing certificates (stackoverflow.com)

Browse Source 
Change-Id: Ib0a7e74d394c3c5f7d2f3d7f5ba70bf6a714b604
This commit is contained in:
Tor Lillqvist
2013-02-02 12:38:13 +02:00
parent 71be8c531b
commit e6093cff47
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
configure.ac
View File

@@ -2720,9 +2720,13 @@ if test "$_os" = "Darwin"; then
AC_MSG_CHECKING([whether to do code signing]) AC_MSG_CHECKING([whether to do code signing])
if test \( -z "$enable_macosx_code_signing" -o "$enable_macosx_code_signing" = yes \) -a $MACOSX_SDK_VERSION -ge 1070; then if test \( -z "$enable_macosx_code_signing" -o "$enable_macosx_code_signing" = yes \) -a $MACOSX_SDK_VERSION -ge 1070; then
# By default use the first suitable certificate. Not sure if should be looking for the # By default use the first suitable certificate (?).
# 'Developer ID Application:' ones instead. The code signing stuff could be much better
# documented... # http://stackoverflow.com/questions/13196291/difference-between-mac-developer-and-3rd-party-mac-developer-application
# says that the "Mac Developer" certificate is useful just for self-testing. For distribution
# outside the Mac App Store, use the "Developer ID Application" one, and for distribution in
# the App Store, the "3rd Party Mac Developer" one.
identity=`security find-identity -p codesigning -v 2>/dev/null | grep 'Mac Developer:' | awk '{print $2}' |head -1` identity=`security find-identity -p codesigning -v 2>/dev/null | grep 'Mac Developer:' | awk '{print $2}' |head -1`
if test -n "$identity"; then if test -n "$identity"; then
MACOSX_CODESIGNING_IDENTITY=$identity MACOSX_CODESIGNING_IDENTITY=$identity