Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
During the creation of self-signed certificate using OpenSSL command line tool, i'm encountered with an error
First I created a private key
openssl genrsa -out MyKey1.key 2048
While creating a CSR i'm getting an error
openssl req -new -out MyCert1.req -key MyKey1.key -subj /CN=Description of the Server
Error is
problem creating object tsa-policy1=1.2.3.4.1
5364:error:08064066:object identifier routines:OBJ_create:pid exists:crypto\objects\obj_dat.c:689:
Is there something i'm missing here ?
Close the current cmd window and open new cmd window.
Continue from the second "req" step.
I had this same problem while creating a self signed certificate...
setting these two environment variables fixed it!
set RANDFILE=c:\demo\.rnd
set OPENSSL_CONF=C:\OpenSSL-Win32\bin\openssl.cfg
I found the solution in this blog post
I had the same issue when creating client certificate request on Windows platform. Run application as Administrator solves the problem.
In my situation, I changed the administrator password while I was working so CMD lost the privileges. I closed the current CMD window and opened again
Look into the openssl.cnf file for this section:
# Policies used by the TSA examples.
tsa_policy1 = 1.2.3.4.1
tsa_policy2 = 1.2.3.4.5.6
tsa_policy3 = 1.2.3.4.5.7
Comment or remove the tsa_policyX lines, save the configuration file and launch the command again.
Related
I've been using GPG with authentication subkeys for a while now, and I recently ran into a rather unhelpful error message. I'm writing this question "Q&A-style" to help others who might run into the same problem.
I use a set of GPG keys for GitHub stuff — both for commit signing and for authentication via SSH. I decided to upgrade the authentication subkey to the newer ED25519 elliptic curve standard, so I added a new ed25519 subkey with authentication capability and revoked the old RSA authentication subkey. I gpg --export-ssh-keyed the new subkey, then added it to both GitHub and a local ~/.ssh/id_gpg_gh.pub file, which is set as my identity file for GitHub via my SSH config.
At this point, though, SSH threw a Load key ".ssh/id_gpg_gh.pub": invalid format error when I tested my login ability. Connecting in verbose mode (ssh -T github.com -v) revealed that SSH was correctly advertising my new key and GitHub was accepting it, but that acceptance was immediately followed by the error message. It seemed that SSH was refusing to actually use my new subkey due to formatting issues.
The error message in this case turned out to be a bit misleading. There was no formatting error in my public key file, as it suggested. Instead, I'd forgotten to tell the GPG agent to use my new subkey, which I fixed by adding its keygrip to ~/.gnupg/sshcontrol.
Despite this being a simple fix, the error message was misleading enough that I anticipate others running into the same issue and being similarly confused. I hope this answer will be useful in such a case.
Also, in case anyone reading this needs a good reference for setting up GPG/SSH authentication in the first place: there are several guides available online, but this one from opensource.com is a good one to start with. This was also how I identified the setup step that I'd skipped, solving my issue.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I am trying to setup WSL for ubuntu 20.04 windows app store disabled in my org for downloads. Can I get offline build for appx file?
I am getting below error:
Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF0, Package could not be opened.
error 0x8007000D: Opening the package from location Ubuntu.appx failed.
NOTE: For additional information, look for [ActivityId] 61dcaa29-6a91-0005-bbef-dc61916ad701 in the Event Log or use
the command line Get-AppPackageLog -ActivityID 61dcaa29-6a91-0005-bbef-dc61916ad701
At line:1 char:1
Add-AppxPackage .\Ubuntu.appx
+ CategoryInfo : OpenError: (C:\Dev\Ubuntu.appx:String) [Add-AppxPackage], FileNotFoundException
+ FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand
There are several scenarios in which you may not be able (or want) to,
install WSL Linux distros via the Microsoft Store. Specifically, you
may be running a Windows Server or Long-Term Servicing (LTSC) desktop
OS SKU that doesn't support Microsoft Store, or your corporate network
policies and/or admins to not permit Microsoft Store usage in your
environment.
This link may help
Okay, I need some serious help. So I want to use some Google Play Services in my game that's not yet released. I made my game using the Unreal Engine. I followed this documentation to generate the keystore file, but I need the SHA1 fingerprint and I can't get it.
I tried following this website, but I keep getting this error:
keytool error: java.io.IOException: Keystore was tampered with, or password was incorrect
java.io.IOException: Keystore was tampered with, or password was incorrect
Does anyone know about this error, because I'm beginning to get pretty pissed off with this stupid key stuff.
Your Android keystore usually has a password (eg. production keystores), when you call keytool -list -v ...., there should have been a prompt that asks for the password of the keystore selected. If correct, it will give out the necessary information of that keystore (SHA-1, etc.). You can refer to this stackoverflow question
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
The problem is simple. When I type next command in elevated command prompt new user that can log in should be created:
net user UserName UserPass /ADD
After that command execute I should be able to start process and to log into machine as that user:
runas /user:UserName "cmd.exe"
After typing in password for user message I get is:
RUNAS ERROR: Unable to run - cmd.exe
299: Only part of a ReadProcessMemory or WriteProcessMemory request was completed.
But command is successful if I run it with /noprofile option. Also user created like this is not able to log on computer, log in fails with message:
User profile Service service failed the logon. User profile cannot be loaded.
OS is Windows 8.1 (original not pirate version) upgraded from Windows 8. I suspect that this is some Windows configuration error so it would be nice if one could point me in right direction.
The following link is very likely to direct you towards identifying any files that might be causing this error.
http://chentiangemalc.wordpress.com/2011/07/18/case-of-the-user-service-service-failed-the-logon/
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
So, I'm having a rather weird problem. I have a server, that when I try to SSH into, immediately closes the connection if I type in the correct password on the first attempt. However, if I purposefully enter a wrong password on the first attempt, and then enter a correct password at the second or third prompt, it successfully logs me into the computer. Similarly, when I try to use public key authentication, I get an immediate closed connection. If, however, I enter a wrong password for my key file, followed by another wrong password once it reverts to password authentication, I can successfully log in as long as I provide the correct password at the second or third prompt.
The machine is running Red Hat Enterprise Linux Server release 6.2 (Santiago), and is using LDAP for authentication. Any ideas on where to start debugging this one?