signing

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

生来就可爱ヽ(ⅴ<●) 提交于 2019-12-06 20:19: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

ClickOnce and mageUI adding custom file folder problems

爷,独闯天下 提交于 2019-12-06 13:50:07
问题 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

Xcode Error signing Failed to create provisioning profile and No profiles for 'com.photo.appwall' were found

自作多情 提交于 2019-12-06 13:12:58
I am having issues signing my application. Failed to create provisioning profile. No profiles for 'com.photo.appwall' were found. The error message seems self explanatory: you need to register your test device on the Apple's developer portal. Log in Apple's Developer portal Click Certificates, IDs & Profiles Click Devices | All Click the + button and add your device UDID Xcode should be able to do this for you if you plug your device with your computer then select it in menu: (Xcode 8) Window | Devices (Xcode 9) Window | Devices and Simulators 来源: https://stackoverflow.com/questions/45906399

KeystoneJS signin

只谈情不闲聊 提交于 2019-12-06 06:51:21
I am creating a keystone project and I need to provide allow or not allow users to access using the keystone signin. However, I found that keystoneJS sends a form data with email, password and csrf. This csrf is given to the user when he access to the login page. Nevertheless, what I need to do is to comunicate externally to login the user, by using an API. How can I generate the _csrf? Is there another way then generate two requests? Thanks @Sericaia, you didn't include any code or specifics on how you intend to implement your login page, so my answer will be a little vague. Keystone has an

Signed exe becomes unsigned after adding project output in setup package using visual studio 2008

守給你的承諾、 提交于 2019-12-06 05:51:38
I have created a msi setup package using visual studio 2008. I have added a project's output (exe project), which is signed at post build, to the setup package. The project is signed at the output directory (bin\Release). but when install the setup package, the exe found unsigned at the installed location. Why is the signing becomes invalid ? When i add it as a file it is signed. But when i add it as Project Output to the setup project it becomes unsigned. (I'm doing signing process at post build) I think it's something like the Primary Output files being used from the obj folder, not the

Signing PDF with a certificate in a certificate store

馋奶兔 提交于 2019-12-06 03:55:57
I want to sign a PDF with a certificate in a certificate store. I am using iTextSharp and iSafePDF for singing PDFs, it works OK when I sign using a certificate stored as .p12 file. But I don't know how to use the library for signing with certificates obtained from a certificate store. I have an instance of System.Security.Cryptography.X509Certificate2, but the library uses a different object representation and I was not able to make it work. Can someone help? OK, here is exactly what I was trying to find, the accompanying text is in Czech, but there is not much of it and the code that works

Where to keep p12 file securely on App Engine?

筅森魡賤 提交于 2019-12-06 03:36:12
问题 On App Engine, I need a p12 file to create signed URLs: https://developers.google.com/storage/docs/accesscontrol#Signing-Strings Google does not describe what are best practices about keeping this file. Can I use the WEB-INF directory to store the file? It would then be part of the source code and kept together with the password to open it. What are best practices here? Or other approaches? -- What about performance? Is it efficient to load the file over and over again? Does App Engine

Using SecKeyRawSign on the iPhone

為{幸葍}努か 提交于 2019-12-06 03:23:04
问题 I'm trying to sign some data using SecKeyRawSign but I keep getting a -4 errSecUnimplemented. That seems strange since the documentation states that it is available in iPhone OS2.0 and later. Has anyone been able to use this function? If so, are there any tricks involved? ~Nate 回答1: If you're having this problem, most likely it is because the private key you generated isn't actually being saved into the keychain. I figured this out when stopping and restarting the application and signing the

Google+ signin button [class='g-signin']

不问归期 提交于 2019-12-06 02:55:43
问题 I am trying to make a google+ siginin button for my site. I went through this link https://developers.google.com/+/web/signin/#button_attributes and tried to make it working but now my styling is all messed up. I am not able to mess around with the [class='g-sinin'] in CSS. This is my code: <section class='login_G' > <span class='g-signin' data-callback='signinCallback' data-scope='https://www.googleapis.com/auth/plus.login'></span> </section> This is my css: .login_G { cursor: pointer;

Change signing key, keep packagename

最后都变了- 提交于 2019-12-06 02:17:26
问题 I cant seem to find the answer to this: Is it possible to change signing-key but still use the same packagename? So that the people who bought my app can "re-download" the app with the new key, from the same Google Play page. The background to this is that I want to extend my signing key to more then 25 years I have set now. Maybe this is enough but I dont want to be put in a situation where the key expires. If this is not possible, could I remove my current Google Play app and create a new