DDoS-Protection – DoS/DDoS Attack Protection – Blog

I used XAMPP a couple of years and I had many problems with it. So, after searching on Google, I came across WAMP Server, a friendly web environment. I began working on it and since then I didn’t have any problems with it.

Recently, I wanted to create a browser game and host it on my computer. So, I began searching for a website that could offer me a stable DNS and found no-ip.com. After registering an account, I created a free subdomain on their website.

The next step was to set my router to create a link between the subdomain and my computer. At first, I set the router’s DHCP to offer me a static IP every time from Home > DHCP > Static DHCP. Then I created a link between the Internet and the local network by accessing Advanced > Virtual Server and setting the following options:

Private IP: 192.168.0.23 (the static IP that the router gives me)
Protocol type: TCP
Private port: 8088 (the port used by WAMP Server)
Public port: 80 (the port on which the subdomain runs; it’s usually 80)

After that, I made the connection with no-ip.com from Advanced > DDNS, so the router would change the DNS each time I turn on my computer.

Finally, I made the connection between WAMP Server and no-ip.com. I accessed WAMP Server > Apache > httpd.conf and modified the following lines:

Listen: 8088 (the port used by WAMP Server, it’s modification is optional)
ServerName: subdomain.no-ip.info

We restart the router, WAMP Server and our server is ready to use.

Beginning in privileged EXEC mode, follow these steps to enable port security: Command Purpose

Step 1 configure terminal Enter global configuration mode.

Step 2 interface interface Enter interface configuration mode for the port you want to secure.

Step 3 switchport port-security Enable basic port security on the interface.

Step 4 switchport port-security maximum max_addrsSet the maximum number of MAC addresses that is allowed on this interface.

Step 5 switchport port-security violation {shutdown | restrict | protect}Set the security violation mode for the interface.The default is shutdown.For mode, select one of these keywords:

     • shutdown—The interface is shut down immediately following

a security violation.

• restrict—A security violation sends a trap to the network

management station.

     • protect—When the port secure addresses reach the allowed

      limit on the port, all packets with unknown addresses are

dropped.

Step 6 end Return to privileged EXEC mode.

Step 7 show port security [interface interface-id | address] Verify the entry.

Disabling Port Security: no switchport port-security

Note: If the port link goes down, all the dynamically learned addresses are removed.

Source: here

Facand putina pauza si rasfoind internetul, am dat peste un tutorial video foarte interesant, unde combinand cateva tipuri de vulnerabilitati web, se obtin in cele din urma privilegiile userului root pe un server.
Platforma folosita este WordPress 3.0.1, proiectul fiind creeat pentru un concurs.

Chiar daca video-ul este in limba rusa, procedeul si detaliile sunt usor de inteles.

Sursa: denjacker @ RSTCenter.com

Folosind WordPress pe mai multe domenii, am observat in ultimul timp ca primeam din ce in ce mai multe comentarii de tip spam, chiar si cu pluginul Akismet.
Multi spammeri sau mai bine spus, scriptul care spameaza acceseaza fisierul wp-comments-post.php in mod direct, inainte de accesarea vreunui articol.

Putem opri in mare parte spamul in WordPress adaugand urmatorul cod in fisierul .htaccess din folder-ul /public_html/ ( pentru cei care folosesc cPanel ) sau httpdocs/ ( pentru Plesk ), care va bloca accesarea in mod direct a fisierului mai sus mentionat.

RewriteEngine On
RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{REQUEST_URI} .wp-comments-post\.php*
RewriteCond %{HTTP_REFERER} !.*siteultau.ro.* [OR]
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule (.*) ^http://%{REMOTE_ADDR}/$ [R=301,L]

Nota: Editati siteultau.ro cu numele site-ului vostru, fara “www”.

#!/bin/bash