1996-06-07 - Re: WWW servers.

Header Data

From: sameer@c2.org
To: unicorn@schloss.li (Black Unicorn)
Message Hash: f2c3e7956f2a7fb1402a81b776c68a09476baebc8566e2fc90e9a2441970b306
Message ID: <199606062121.OAA07502@niobe.c2.net>
Reply To: <Pine.SUN.3.91.960606161633.1329A-100000@polaris>
UTC Datetime: 1996-06-07 14:30:28 UTC
Raw Date: Fri, 7 Jun 1996 22:30:28 +0800

Raw message

From: sameer@c2.org
Date: Fri, 7 Jun 1996 22:30:28 +0800
To: unicorn@schloss.li (Black Unicorn)
Subject: Re: WWW servers.
In-Reply-To: <Pine.SUN.3.91.960606161633.1329A-100000@polaris>
Message-ID: <199606062121.OAA07502@niobe.c2.net>
MIME-Version: 1.0
Content-Type: text/plain


> 
> Does there currently exist a system which permits webservers to restrict 
> access to clients who have a given certification?

	Yup.

> 
> What is the current certification practice?

	Use either VeriSign, or build your own CA.

> 
> How easy is it to certify a given client?

	Rather easy, using XCert Sentry.

> 
> Are webserver certifications sufficently secure today?

	"sufficiently" by whose definition?

> 
> What are the best servers to use for secure web pages and certification 
> currently in the United States?

	=) Stronghold: The Apache-SSL-US, coupled with XCert
Sentry. What else?

-- 
Sameer Parekh					Voice:   510-601-9777x3
Community ConneXion, Inc.			FAX:     510-601-9734
The Internet Privacy Provider			Dialin:  510-658-6376
http://www.c2.net/ (or login as "guest")		sameer@c2.net





Thread