Re: RCP open! Yikes! What to do?
Ansgar Wiechers <[email protected]> Thu, 19 Sep 2013 21:34:42 +0200
| Newsgroups | gmane.comp.security.basics |
|---|---|
| Message-ID | <[email protected]> |
On 2013-09-19 Justin Bowen wrote: > If you are certain you don't need RPC access (which many don't), > simply drop a windows firewall (or a replacement you might have in > place) entry in to block it. Port 139 Port 139 is the NetBIOS session service. The RPC port mapper is listening on port 135/tcp, the actual RPC connections are established on ports between 1025 and 5000 (49152 and 65535 on Vista and above). See MSKB article 832017 [1] for an overview of the port requirements for Windows. Like I said: do not mess with it unless you have a clear understanding of what it does (and how it works). RPC is required for many kinds of remote management. [1] http://support.microsoft.com/kb/832017 Regards Ansgar Wiechers -- "All vulnerabilities deserve a public fear period prior to patches becoming available." --Jason Coombs on Bugtraq ------------------------------------------------------------------------ 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;e13b6be442f727d1 ------------------------------------------------------------------------