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 2 years ago.
Improve this question
My client's company internal CA provided a *.cer file.
I already installed this file in the our server using MMC but I also need to add the .crt and .key files to the apache configuration.
How can I get the .crt and .key file from the .cer file that the CA issued?
A .cer file is a certificate file. It contains a certificate either in DER format (binary) or PEM format (the same DER formatted binary, base 64 encoded, with header and footer). Usually there is no difference between .cer and .crt: they represent the same (X.509v3) certificate.
Generally you create the key pair, then a certificate request which you send to the CA. You get back a certificate for that particular key pair that you created and - hopefully - stored somewhere secure. If you didn't store the private key securely you're out of luck and you should start over again.
Related
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 have noticed while learning how to setup ssh that lots of stackoverflow posts referred to the file ssh config being inside of the folder ~/.ssh but when i look at the same folder in my macbook the files listed are:
created from my last ssh setup
someprivatekey
someprivatekey.pub
known_hosts
now when i inspect the folder cd /etc/ssh/ then i can see the file ssh_config there.
Is it a normal behavior or should ssh file "ssh_config" always be located in "~/.ssh" folder and I have presumably a wrong configuration?
(Sorry if the post sound very elementary, i am learning how to use ssh)
how to should i setup ssh and the "ssh_config" file correctly?
The file in /etc/ssh affects all users on the machine, while the one in ~/.ssh affects only you. You can find a complete list of the file locations at the end of the ssh manpage (which should be available at your computer by running man ssh).
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
we have two domains, A and B, where I'm looking to get DomainA to redirect all requests to DomainB. There is no server behind DomainA. I've followed this tutorial exactly as presented on Cloudflare:
https://community.cloudflare.com/t/redirecting-one-domain-to-another/81960
And it works just fine for non-https traffic. Attempting to go to https://domaina.com gives me NET::ERR_CERT_COMMON_NAME_INVALID while http://domaina.com redirects to https://domainb.com just fine.
My page rules reflect the tutorial - that is *domaina.com/* 301 redirects to https://domainb.com/$2
My SSL options in Cloudflare is set to "Full". The orange clouds are on as well for both # and www on DomainA which currently are A records. I've tried CNAME as well. Has anyone else run into this before? What might I be doing wrong?
Try setting your SSL option to "Flexible" instead. Since your domain A doesn't have SSL setup, "Full" wouldn't work as it requires SSL on the origin server as well.
Free Clouflare plan will give you "Free certificate".
The Free Certificate's Common Name is always pointed to sni.cloudflaressl.com.
You can't change the common name unless you order Advanced Certificate Manager for $10/month.
You can see Advanced Certificate Manager in SSL > Edge Certificates > Order Advanced Certificate:
Sample "Free Certificate":
The certificate's common name is set to sni.cloudflaressl.com but it is valid to all major OS and browser because the Subject Alternative Name (SAN) in the certificate contains your domain.
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 2 years ago.
Improve this question
I currently have access to a supercomputer cluster.
The problem starts when I enter.
When I try to perform the following command line ssh -i user # extension, I get the following error
Warning: Identity file user # extension not accessible: No such file or directory.
I have tried testing the public root key and if it recognizes it, instead when I run in /home/user, I get the error.
I've been trying some permission changes with the chmod command and I can't get a solution.
ssh -i is to reference a private ssh key.
So if you have a key pair named user.rsa/user, that might work.
But in your case, "user" is not the name of the key, but simply the remote user you want to open a secure shell with on the remote server
ssh user#remoteServer
You don't need -i, if you have a default id_rsa/id_rsa.pub key pair in your local ~/.ssh
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 6 years ago.
Improve this question
Follow up on the question that I asked here already.
I have Amazon AWS Instance running Windows 2013 server. I have used IIS 8 to generate CSR file. I have used that CSR file in godaddy.com for SSL certificates.
Go daddy gave me following files:
- somerandomhash.crt (2KB)
- gd_bundle-g2-g1.crt (5KB)
In my Sails.js (express.js) I have:
serverOptions : {
key: fs.readFileSync(my.key),
cert: fs.readFileSync(my.cert)
}
I have used http://www.selfsignedcertificate.com/ to create test certificate for my testing domain. That web site provided me with two files, key and cert that work just fine with (ip domain).
Now I need to used proper SSL and I have problems.
How do I update my configuration (serverOptions) to use files provided by godaddy? I do not see a key file anywhere.
IIS should've generated a key along with the CSR. http://www.entrust.net/knowledge-base/technote.cfm?tn=7905 Your SSL provider will not make a key for you, that'd be terribly insecure - you're the only one who's supposed to have a private key.
gd_bundle-g2-g1.crt is a certificate chain file, and should be added to serverOptions like so:
serverOptions : {
key: fs.readFileSync(my.key),
cert: fs.readFileSync(my.cert),
ca: fs.readFileSync(my.ca)
}
After lots of reading this is final solution:
I was getting the following error:
routines:PEM_read_bio:bad end line node.js
No matter what I do I always get that error. Other people who got same error, suggested to add extra enter on header and footer of the request. In my case it did not help. What helped me is Notepad++ and EoL conversion.
I guess you can do it with other editors, but I used Notepad++. Just edit-->EoL Conversion and make sure Windows is selected.
Hopefully it will save time for other people who experience the same problem.
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
I configured SSL in my nginx.conf. I'm getting a valid certificate on https://www.mydomain.com however, this shows a 404 as my website is at mydomain.com
Exploring, I see my site inside of available-sites which has a server block with a root and index but not listen block.
What is the difference between these two?
You can place your SSL configuration into either file. If you check the bottom of nginx.conf you will see
include /etc/nginx/sites-enabled/*;
Which simply includes the contents of all config files in sites-enabled into nginx.conf and continues parsing.