Security Basics
server security Jun 20 2012 05:27PM
Littlefield, Tyler (tyler tysdomain com) (3 replies)
Re: server security Jun 20 2012 11:44PM
Alex Dolan (dolan alex gmail com) (3 replies)
Re: server security Jun 21 2012 05:48PM
Tracy Reed (treed ultraviolet org)
Re: server security Jun 21 2012 04:34PM
Mike Hale (eyeronic design gmail com) (4 replies)
Re: server security Jun 22 2012 11:02AM
Rory Browne (rbmlist gmail com) (3 replies)
Re: server security Jun 22 2012 08:27PM
Tracy Reed (treed ultraviolet org)
RE: server security Jun 22 2012 06:09PM
Ron McKown (RMcKown apptio com) (1 replies)
RE: server security Jun 22 2012 08:09PM
Ward, Jon (Jon_Ward SYNTELINC COM) (1 replies)
RE: server security Jun 22 2012 09:30PM
Dave Kleiman (dave davekleiman com) (2 replies)
RE: server security Jun 26 2012 02:35PM
Tommy Thomas (webmaster ocaladesigns com)
Re: server security Jun 22 2012 09:54PM
Tracy Reed (treed ultraviolet org) (2 replies)
RE: server security Jun 22 2012 10:47PM
Dave Kleiman (dave davekleiman com)
Re: server security Jun 22 2012 10:31PM
Tracy Reed (treed ultraviolet org) (1 replies)
RE: server security Jun 22 2012 10:51PM
Dave Kleiman (dave davekleiman com) (2 replies)
Re: server security Jun 23 2012 12:48PM
Ansgar Wiechers (bugtraq planetcobalt net)
Re: server security Jun 22 2012 11:17PM
Rob (synja synfulvisions com)
Re: server security Jun 22 2012 02:51PM
Littlefield, Tyler (tyler tysdomain com)
Re: server security Jun 21 2012 04:47PM
Killian Faughnan (lists killianfaughnan com)
Re: server security Jun 21 2012 04:44PM
Littlefield, Tyler (tyler tysdomain com)
Re: server security Jun 21 2012 02:44PM
Jerome Athias (athiasjerome gmail com)
port knocking is better

Le 21/06/2012 18:34 VALR, Mike Hale a écrit :
> "Putting it on some other port reduces your risk"
> It doesn't really reduce your risk, since you're still as vulnerable
> as you were before.
>
> What it does is reduce your log entries. That can be worth the added
> administrative cost of changing standard ports, but it's not really a
> 'security' measure.
>
> On Wed, Jun 20, 2012 at 4:44 PM, Alex Dolan <dolan.alex (at) gmail (dot) com [email concealed]> wrote:
>> One tip I have is to set SSH to a port other than 22, I don't need to
>> tell anyone how devastating it is if someone did actually get access
>> to that service. Putting it on some other port reduces your risk
>>

------------------------------------------------------------------------

Securing Apache Web Server with thawte Digital Certificate
In this guide we examine the importance of Apache-SSL and who needs an SSL certificate. We look at how SSL works, how it benefits your company and how your customers can tell if a site is secure. You will find out how to test, purchase, install and use a thawte Digital Certificate on your Apache web server. Throughout, best practices for set-up are highlighted to help you ensure efficient ongoing management of your encryption keys and digital certificates.

http://www.dinclinx.com/Redirect.aspx?36;4175;25;1371;0;5;946;e13b6be442
f727d1
------------------------------------------------------------------------

[ reply ]
Re: server security Jun 21 2012 03:52PM
Rob (synja synfulvisions com)
Re: server security Jun 20 2012 06:58PM
Rowland Onobrauche (rowland onobrauche alphadex co uk)
Re: server security Jun 20 2012 06:13PM
Mike Hale (eyeronic design gmail com) (1 replies)
Re: server security Jun 20 2012 06:40PM
Gregory J Bessette schneider-electric com


 

Privacy Statement
Copyright 2010, SecurityFocus