Jump to content

Recommended Posts

Posted

'Sure we can I said', Ooops. Can anyone out there help me out with either:

 

a. Free self certificate creating software

b. A site which creates the for free.

 

We need them for secure (HTTPS) Outlook Web Access to work, and needs to be Windows based.

Posted

Linux with OpenSSL installed. Here's a how:

 

openssl req -new -newkey rsa:1024 -days 365 -nodes -x509 -keyout [url]www.example.com.pem[/url]  -out [url]www.example.com.pem[/url]

 

Enjoy. Just copy the pem file to your windows server when its cooked.

Posted
Linux with OpenSSL installed. Here's a how:

 

openssl req -new -newkey rsa:1024 -days 365 -nodes -x509 -keyout [url]www.example.com.pem[/url]  -out [url]www.example.com.pem[/url]

 

Enjoy. Just copy the pem file to your windows server when its cooked.

 

Can also be done on windows with openssl :p

 

openssl exe is in this apache package:

http://www.madhon.co.uk/modssl/modssl220_vc6.zip

Posted

You can use your own dc (which is also i presume the CA for your domain) to do this.

 

Have a look at http://www.isaserver.org for more info on how to do this. Its mostly to do with isa server but had some tutorials to create the certificate.

 

From what i can gather, you need to go into IIS manager and right click on the default website and click on properties.

 

Then go into the "Directory Security" tabe and under the "secure communications" section select the server certificate and follow the wizard.

 

Take a look at this -->http://www.isaserver.org/articles/2004pubowartm.html

 

 

HTH,

 

Ash.

Posted
You can use your own dc (which is also i presume the CA for your domain) to do this.

 

Have a look at http://www.isaserver.org for more info on how to do this. Its mostly to do with isa server but had some tutorials to create the certificate.

 

From what i can gather, you need to go into IIS manager and right click on the default website and click on properties.

 

Then go into the "Directory Security" tabe and under the "secure communications" section select the server certificate and follow the wizard.

 

Take a look at this -->http://www.isaserver.org/articles/2004pubowartm.html

 

 

HTH,

 

 

That creates a requst for a certificate. You mail that to a certificate provider and they create your cert from that file.

Ash.

Posted
If not by Ashok's method, then there should be another method within Server 2k3 to greate your own certificate as I've done it using my Small Business Server to get an SSL certificate for Outlook Web Access & Remote Web Workplace.
Posted
The IIS resource kit contains an application called SelfSSL, which I recently used to create a new self-signed certificate for an OWA installation whose certificate had expired. It worked for me.
  • 1 year later...
Posted
I need this to work for OWA externally. The selfSSL works great within the domain, but we need something for home users. The security warning in IE7 'looks' much more serious than it did in IE6, any idea how to get a 'proper' certificate? I know absolutely nothing about it - so n00b speak only please :D
Posted

We have a full blown PKI infrastructure here, so we can deploy our own CA + Client certs to our machines internally. Thus they trust the server certs implicitly.

 

Our external web access to internally run sites (eg, our VLE running Moodle) is done through a reverse proxy. The SSL cert the clients out on the internet see is from this proxy rather than from our internal web server. So it's not my problem.

 

Sadly CLEO haven't bothered to use a real wildcard cert from *.lancs.sch.uk though so the warning will currently popup.

 

You can see this for yourself, browse to our VLE.

 

https://vle.carrhill.lancs.sch.uk

Posted

I think if you've got a domain and this is only for staff, then make/use your own CA and get them to your CA cert at home- could have other uses down the line and [don't groan] it's yet another opportunity to try and educate your users about this stuff.

 

Can also be done on windows with openssl

 

I used to routinely build win32 openssl for making a CA and certs for Windows back in the 20th century when the US crackable-crypto export regulations were still a bit serious.

 

[Those regs banned export of strong data encryption but did allow for strong *authentication*. Early non-US Cert Server wouldn't let you have decent key lengths but if you made say a 2048 bit cert via openssl, IIS would happily use it... which was a good thing even though the subsequent SSL data encryption was weak]

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...