I am trying to execute the following command in command prompt .
keytool -exportcert -alias androiddebugkey -keystore "<path-to-users-directory>\.android\debug.keystore" | openssl sha1 -binary | openssl base64
But the command prompt windows reports:
'openssl' is not recognized as internal or external command.
What ca I do to execute this command in command prompt window?
The error you saw means there's no such program in your %PATH% (external command) and it's also not a built-in shell command (internal command).
Install OpenSSL on your machine. You will also need to check that its installed location is in your %PATH%. By default it probably won't be. As an example, suppose OpenSSL is installed at c:\OpenSSL-Win32. The openssl binary is probably located at c:\OpenSSL-Win32\bin\openssl.exe. So you path needs to include c:\OpenSSL-Win32\bin.
Sometimes OpenSSL cannot find its configuration file on Windows. For that, see OpenSSL and error in reading openssl.conf file.
Another option is to use the full path in the command:
keytool -exportcert -alias androiddebugkey -keystore "<path-to-users-directory>\.android\debug.keystore" | ^
c:\OpenSSL-Win32\bin\openssl.exe sha1 -binary | c:\OpenSSL-Win32\bin\openssl.exe base64
However, this still suffers the OpenSSL configuration file problem detailed at OpenSSL and error in reading openssl.conf file.
install openssl for windows from the following link .
https://code.google.com/p/openssl-for-windows/downloads/detail?name=openssl-0.9.8k_WIN32.zip
Just you need to Add OpenSSL bin path (ex: C:\Program Files\OpenSSL-Win64\bin) to the PATH system variable as shown below:
Go to: https://code.google.com/archive/p/openssl-for-windows/downloads
Extract file
open bin/openssl.exe
Install openssl on your Windows machine.
Related
When ever I try to generate Sha1 key, I get this error.
Please note after fresh macOS BgSur installation, I only added flutter to path, installed xcode, android-studio and vscode.
code I use
keytool -list -v \
-alias androiddebugkey -keystore ~/.android/debug.keystore
Error I get
/.android/debug.keystore
java.lang.Exception: Keystore file does not exist:
/Users/nuaiman/.android/debug.keystore
at sun.security.tools.keytool.Main.doCommands(Main.java:777)
at sun.security.tools.keytool.Main.run(Main.java:375)
at sun.security.tools.keytool.Main.main(Main.java:368)
I am trying to install go tools in my WSL
command :
go get -v golang.org/x/tools/gopls
Error :
go get: module golang.org/x/tools/gopls: Get "https://proxy.golang.org/golang.org/x/tools/gopls/#v/list": x509: certificate signed by unknown authority
Error Msg : x509: certificate signed by unknown authority
Check first if this is similar to golang/go issue 45569, and check the ouput of
openssl s_client -showcerts -connect proxy.golang.org:443 </dev/null | openssl x509 -text -noout
In that issue, behind a corporate network, disabling NetScope was needed.
This is probably because in a clean WSL with only golang installed.
Try install ca-certificates, it may solve the issue.
I am in an EC2 instance trying to set up a notebook server to allow me to create an ipython notebook locally that runs on the EC2 instance. (Following these instructions).
When I try to create a self signed certificate using this command:
openssl req -x509 -nodes -days 365 -newkey rsa:1024 -keyout mycert.pem -out mycert.pem
I get the following message:
WARNING: can't open config file: /opt/anaconda1anaconda2anaconda3/ssl/openssl.cnf
Unable to load config info from /opt/anaconda1anaconda2anaconda3/ssl/openssl.cnf
I used the same process in a previous EC2 instance and it worked fine. Any ideas?
Turns out this was a known bug with Anaconda. Details here: https://github.com/ContinuumIO/anaconda-issues/issues/228
Quick fix is to enter on the command line:
conda update openssl
Did you check your permissions for said config file?
ls -la /opt/anaconda1anaconda2anaconda3/ssl/
If you don't have read permissions, you need to add them
sudo chmod +r /opt/anaconda1anaconda2anaconda3/ssl/openssl.cnf
Or simply try running the same command as root by preceding it with sudo
I want to install self-signed certificate for IE, Firefox and Chrome in Windows (XP and 7).
I need to install certificate for several systems, So I planed to create .bat file that install certificate for browsers. I got following command while googled
certutil -addstore -f -enterprise -user root root_ca.cer
But it only for IE. Is there any option for Chrome and Firefox.
Bit of an old post but thought I would throw in my two cents anyway. You are right, that command in a batch script will install the certificate root_ca.cer into the trusted CA store. I would modify the line to be:
certutil -addstore -f -enterprise -user root "%~dp0root_ca.cer"
This way the shell will expand %~dp0 to the path of the executing script so you can run it across a network from a UNC path and it will still work.
In answer to your other question, Chrome will (as of writing this post) read from the windows certificate store so there is no need to do anything special; just restart chrome after running the script and it should be sweet.
As for Mozilla check out this post for a script to do that. Simples!
I need to install my self-signed certificate in my clients machine and follwed the steps in this link.
But in the command in this document shows certmgr.exe -add good.cer -c -s -r localMachine TrustedPublisher where as the document in WDK "WinDDK/7600.16385.1/src/general/build/driversigning/selfsign_readme.htm#_Toc138233166" has the same command named as "trustedpublisher".
certmgr.exe -add certfilename.cer -s -r localMachine trustedpublisher
Which one is correct among this? Where the certificate will be installed? Also,
I can only find folder named "Trusted Publisher" in my Pc.
So where should I install the certificate apart from "Root"?
Please guide me..
Since TrustedPUblisher in this case is a certificate store, and not a command line parameter, and Microsoft Windows is not case sensitive for this kind of thing, either case should work.
For a self-signed certificate, you should most likely add the certificate to both Root and TrustedPublisher.