signing

Signed URL for google bucket does not match signature provided

喜欢而已 提交于 2019-12-06 01:36:07
I'm having an hard time working with google storage. So I'm trying to make a signed url , already have the client id (which is an email) and private key (as described here ) so: STEP 1: construct the string function googleBuildConfigurationString($method, $expiration, $file, array $options = []) { $allowedMethods = ['GET', 'HEAD', 'PUT', 'DELETE']; // initialize $method = strtoupper($method); $contentType = $options['Content_Type']; $contentMd5 = $options['Content_MD5'] ? base64_encode($options['Content_MD5']) : ''; $headers = $options['Canonicalized_Extension_Headers'] ? $options[

Mac app direct distribution: “Your account does not have permission to create Mac App Direct Distribution certificates”

纵饮孤独 提交于 2019-12-05 21:13:24
问题 I want to distribute my mac application outside the App Store (as file downloadable from our servers), but every attempt to export archive from Xcode with option "Export a Developer ID-signed Application" ends with a "Permission failure": Your account does not have permission to create Mac App Direct Distribution certificates I've downloaded and added all certificates to my keychain (system). I'm using an Organization Apple Developer account, so is it possible to use this type of account to

Authenticode or other code signing for Mac and Linux

此生再无相见时 提交于 2019-12-05 20:10:07
Is there anything similar to Authenticode for Mac and Linux? If yes, could anyone point to a sample snippet, preferably in C, on how to check that the signature match? Thank you EDIT: There is one possible answer to the Mac part in here but I don't know whether this can be done in plain C. The standard way of authenticating code running on a Linux system is to validate the binaries once while installing the package rather than every time they are run. The package (e.g. RPM) contains a cryptographic signature that must match the contents of the files or the installer will refuse to install.

How to verify that timestamping is done correctly for signed code

微笑、不失礼 提交于 2019-12-05 15:34:02
问题 I have just got my code signing certificate from StartSSL and am trying to sign our installer. The signing process goes well and I get an installer exe that Windows no longer complains about being from unknown publisher. This is great! However I tried to make sure that the timestamping also works as advertised so I moved my PC date to 2012, after my code signing certificate expiration date. This supposedly should not make any difference but when I run the same installer exe I now get the same

gradle assembleRelease uses wrong key/certificate

孤街醉人 提交于 2019-12-05 14:09:36
I have a gradle-based android project and trying to generate a release apk. However, it seems that somehow gradle is picking up the wrong key/cert. This is what I have in build.gradle: signingConfigs { release { storeFile file("mykey.jks") storePassword "mypass" keyAlias "mykey.key" keyPassword "mypass" } } buildTypes { release { debuggable false jniDebugBuild false runProguard true proguardFile getDefaultProguardFile('proguard-android.txt') signingConfig signingConfigs.release } } And after running gradlew assembleRelease and taking out META-INF/CERT.RSA from inside the .apk I run the

Xcode 8.3.2 signing errors

冷暖自知 提交于 2019-12-05 07:33:37
I have Xcode 8.3.2 on Sierra. I am trying to build an Enterprise .ipa (have Enterprise membership). I am having issues signing my app. Specifically in Xcode I have the following under General\Signing: Automatically manage signing is enabled Team: "My Team (Enterprise)" Provisioning Profile: Xcode Managed Profile Signing Certificate: iOS Developer Status Failed to create provisioning profile "com.myapp" cannot be registered to your development team. Change your bundle identifier to a unique string to try again. No profiles for 'com.myapp' were found. Xcode couldn't find a provisioning profile

Unable to open keystore in AndroidStudio - “Redundant length bytes found”

*爱你&永不变心* 提交于 2019-12-05 02:31:05
I am unable to open my existing keystore file in Android Studio or use the jarsigner from the command line. In both cases the error message is: java.security.cert.CertificateException: Unable to initialize, java.io.IOException: DerInputStream.getLength(): Redundant length bytes found See screenshot: Apparently this was an issue that should be fixed with JDK8_131 but does not work for me. (We are all using OSX) I also get the same error on travis. (See "Update" section below.) I found another SO question ( Signing android app throws IOException: Redundant length bytes found ) where they

Which files should be digitally signed

人走茶凉 提交于 2019-12-05 02:16:51
问题 I am wondering what files should be digitally signed? I'm not talking about strong naming assemblies, but about digitally signing files so that it is possible to determine if they have been tampered with. I read the following post. The author states that all installer files should be signed as well as the main program executable - that sounds reasonable, but what about other files and applications? I know that ClickOnce applications have their manifest signed, not sure about the installer

ClickOnce and mageUI adding custom file folder problems

匆匆过客 提交于 2019-12-04 19:37:41
What I do: Publishing .Net 3.5 application via VS, or msbuild (whatever), and now I need to insert to the published application separate directory (Modules - not added as a reference to the project - our project architecture does not allow this). So I'm copying the folder to published location then runs mageUI.exe select the application manifest and then the problems starts. As I press the populate button it's adding also hidden directory? So I remove the directory, after I want to save the manifest file I get the "Warning MSB3110: Assembly 'NAME.Shell.application.deploy' has mismatched

Why signed android apk is not running on emulator

瘦欲@ 提交于 2019-12-04 14:33:10
问题 I have made a signed apk of an android project. Whenever my client try to run it on the emulator, he faces the following error message: D:\Android\android-sdk- windows\tools>adb install -r abc.apk 500 KB/s (6940708 bytes in 13.534s) pkg: /data/local/tmp/abc.apk Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES] What is the resolution? 回答1: In my case it was because I signed it on a machine running JDK 7. Downgrading to JDK 6 fixed the problem. Thanks java.lang.SecurityException when install apk