Home page logo

basics logo Security Basics mailing list archives

Re: wildcard SSL, is this a bad thing?
From: "kalgecin () gmail com" <kalgecin () gmail com>
Date: Mon, 20 Apr 2009 22:04:19 +0300

could be bad if the attacker is on the same intranet. for example, a
local employee connects and registers a name such as att.company.com.
your certs use *.company.com. the attacker will be in possition to exploit.

On 4/17/09, robsonde () gmail com <robsonde () gmail com> wrote:
do wildcard SSL cert's have a bigger security risk?

we are building 4 new servers for our internal intranet staff directory.
we will have a c-name for each server.

this way we can point any c-name at any server for DR and maintance outages.

the old system was to have an SSL cert for each server.

problem is that if we re-point a c-name we will get a SSL cert mis-match.

my plan is to make each server use a wildcard SSL cert of
I know my solution will solve the problem but is it a security risk?
is this a bad thing?

what security risks am I opening up?


This list is sponsored by: InfoSec Institute

Find the source of cybercrime! Almost every crime today involves a computer
or mobile device. Learn how to become a Computer Forensics Examiner in
InfoSec Institute's hands-on Computer Forensics Course. Up to three industry
recognized certs available, online computer forensics training available.


Sent from Gmail for mobile | mobile.google.com


This list is sponsored by: InfoSec Institute

Learn all of the latest penetration testing techniques in InfoSec Institute's Ethical Hacking class. 
Totally hands-on course with evening Capture The Flag (CTF) exercises, Certified Ethical Hacker and Certified 
Penetration Tester exams, taught by an expert with years of real pen testing experience.


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]