ssl - Getting (58) unable to use client certificate (no key found or wrong pass phrase?) from curl -

-

i'm attempting make test calls third-party api requires client cert. generated new cert using command openssl:

req -new -newkey rsa:2048 -nodes -out mycsr.csr -keyout mykey.key

i sent them csr, , sent me mycert.crt. concatenated cert , key together:

cat mycert.crt mykey.key > mycertandkey.pem

finally, added mycert.crt ca-certificates folder , ca-certificates.conf , ran "update-ca-certificates --fresh".

now, i'm trying make curl call bash using following command:

curl -x --cert mycertandkey.pem -h 'accept-encoding: gzip,deflate' -h 'content-type: application/json' https://api.url.com

i've tried:

curl -x --cert mycertandkey.pem --cacert mycert.crt -h 'accept-encoding: gzip,deflate' -h 'content-type: application/json' https://api.url.com

and:

curl -x --cert mycertandkey.pem --cacert mycert.crt --key mykey.key -h 'accept-encoding: gzip,deflate' -h 'content-type: application/json' https://api.url.com

and every other combination can think of. error "curl: (58) unable use client certificate (no key found or wrong pass phrase?)". key doesn't have passphrase. of cert/key files have 777 permissions.

i haven't worked certs in past , feel i've missed something, since seem have 1 cert. cert other company sent me cacert or client cert? did concatenate private key wrong cert?

i've found lot of piecemeal information online, if knows of tutorial on subject, i'd appreciate well.

adding pass phrase private key solved problem.

i used following command add passphrase:

ssh-keygen -p -f mykey.key

before run command successfully, needed change permissions on key file. 777 not restrictive enough, , ssh-keygen not touch it. changing permissions 600 fixed that.

chmod 600 mykey.key

after adding passphrase, recreated .pem file. can make curl calls using command:

curl -x --cert mycertandkey.pem:mypassphrase -h 'accept-encoding: gzip,deflate' -h 'content-type: application/json' https://api.url.com

Comments

Post a Comment

Popular posts from this blog

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co
Read more

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall
Read more

java - Cannot secure connection using TLS -

-
i'm trying establish secure socket connection between java client applet (built jdk 1.7.0_75-b13) , vc++ server application. as test vehicle, used vc++ client/server sample found in msdn forums, modified use schannel , able establish socket using cipher suite tls_rsa_with_aes_128_cbc_sha. works of tls 1.0/1.1/1.2. when try opening socket java applet same server application, connection rejected server reporting following: tls 1.0 acceptsecuritycontext failed: 0x80090327 tls 1.1 acceptsecuritycontext failed: 0x80090331 tls 1.2 acceptsecuritycontext failed: 0x80090331 this java code used create socket: debugprint("setting secure connection"); sslsocketfactory sslsocketfactory = (sslsocketfactory) sslsocketfactory.getdefault(); sslsocket sslsocket = (sslsocket) sslsocketfactory.createsocket("127.0.0.1", socketnumber); debugprint("starting handshake"); sslsocket.settcpnodelay(true); sslsocket.setsolinger(false, 0); sslsocket.s
Read more