There are 18 posts filed in Windows (this is page 2 of 2).
If you have a certificate file and private key and need to move that to a Windows server you can easily create a pfx file that can be imported on the Windows server.
Here’s how:
openssl pkcs12 -export -in {cer_filename}.cer -inkey {key_filename}.key -out {pfx_filename}.pfx
You will be asked to provide a password. You’ll need to use this password when you import the certificate on the Windows server.
Sometimes you may have a MAC address but need to figure out the IP address. If you have access to a computer on the same network you may be able to look it up using the arp command (works on both Windows and Linux):
arp -a
SSL v2 is weak and outdated protocol. All modern browsers and applications support SSL v3 and that’s why you should disable SSL v2 where possible.
Using this command you can check if SSL v2 is enabled:
openssl s_client -connect www.example.org:443 -ssl2
SSL v2 is weak and outdated protocol. All modern browsers support SSL v3 and it’s enabled by default on Windows 2008 (IIS 7 / IIS 7.5). To make sure all clients are using SSL v3 we must disable SSL v2. This is required for PCI compliance. Continue reading
This is a quick guide on how to migrate all sites from IIS 6 to IIS 7. You can probably use the same commands to move sites from one IIS 7 to another.
Everything will be migrated, including application pools, virtual directories, SSL certficiates etc.
1. Download and install Web Deployment Tool on both source and destination servers: http://www.iis.net/download/webdeploy Continue reading
When uploading files greater than 28.6 MB (30000000 Bytes) with ASP.NET on IIS 7.5 using SWFUpload I’m getting this error:
There has been an I/O Error: Error #2038
1. Download and install Windows SDK
2. Open command prompt as Administrator and cd to this directory: C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin
2. Create a root certificate
makecert -pe -n "CN=Test Root Authority" -ss my -sr LocalMachine -a sha1 -sky signature -r "c:\Test Root Authority.cer"
3. Create the new certificate and sign it with the newly generated self-signed root certificate
makecert -pe -n "CN=yourdomain.com" -ss my -sr LocalMachine -a sha1 -sky exchange -eku 1.3.6.1.5.5.7.3.1 -in "Test Root Authority" -is my -ir LocalMachine -sp "Microsoft RSA Schannel Cryptographic Provider" -sy 12 c:\yourdomain.cer
Today when adding a secure binding to one of my sites in IIS 7, I got this error:
One or more intermediate certificates in the certificate chain are missing. To resolve this issue, make sure that all of the intermediate certificates are installed. For more information, see http://support.microsoft.com/kb/954755.