Sponsored Content
Full Discussion: DDoS and brute force attack
Special Forums Cybersecurity DDoS and brute force attack Post 302885990 by cjcox on Wednesday 29th of January 2014 10:26:31 AM
Old 01-29-2014
DDoS is simply a way to overload services. So, to protect, you use some kind of QoS or application based limiter that slows things down when heavy traffic seems present. In some cases you may be able to figure out the DDoS and limit things specifically.

Brute force attacks are often times focused on services where a username/password are involved. Again, you'll have to craft a response to this specifically. So, if you see so many failed attempts from a source, you could issue a command to your firewall to add a rule to block that source (perhaps just temporarily). As an example of a tool to help with this, look at: 302 Found
 

7 More Discussions You Might Find Interesting

1. Cybersecurity

what is the better way to protect my server from DDos Attack

heloo today i have DDos Attack in my server what is the better way to secure my server from DDos Attack i use CentOS 4&5 i try every firewall and talk to softlayer - iweb i've Tried every possible solutions but I can not find a solution to the problems Give Me The best way plzz (4 Replies)
Discussion started by: a7medo
4 Replies

2. UNIX for Advanced & Expert Users

Apache brute force attack

Hi, I'm trying find out if there is a way to stop a brute force attack on a Webmail site. I'm trying to setup a webmail access, but I would like to prevent too many invalid logins from the same IP. I've looked into Snort, but I was wondering if there was an application level firewall that can... (1 Reply)
Discussion started by: nitin
1 Replies

3. UNIX for Advanced & Expert Users

Brute force SMTP attack right now *help*

Im currently experiancing a brute force attack on my server Nov 26 15:27:04 ws096 saslauthd: do_auth : auth failure: Nov 26 15:27:13 ws096 saslauthd: do_auth : auth failure: Nov 26 15:27:22 ws096 saslauthd: do_auth : auth failure: Nov 26 15:27:29 ws096... (4 Replies)
Discussion started by: mcraul
4 Replies

4. Cybersecurity

DDoS Simulation Tools

are there any popular DDoS simulation tools to test my own infrastructure? Anyone tried to setup all these in AWS EC2? (1 Reply)
Discussion started by: boriskong
1 Replies

5. Shell Programming and Scripting

Expect script that simulates a SSH brute force attack

I want to test the effectiveness of sshguard on some of my systems so I'm trying to write a script that simulates a brute force attack by sending a bunch of different username and password combinations to the servers being tested. So far I have this: #!/usr/local/bin/expect set timeout 3... (5 Replies)
Discussion started by: ph0enix
5 Replies

6. Emergency UNIX and Linux Support

DDOS attack please help!

Dear community, my site was recently attacjed by DDOS technique and goes down in a few minutes. My site runs under Debian/Apache2/Mysql. I identified the IPs who attack me and block it through iptable firewall from debian. Something like: iptables -D INPUT -s xxx.xxx.xxx.xxx -j DROP This... (7 Replies)
Discussion started by: Lord Spectre
7 Replies

7. UNIX for Advanced & Expert Users

Anti ddos shell script, is it useful?

Hi guys, just need a opinion from you. I found anti ddos script from github Script What is your opinion about it? Is it usefull? Do you have some similar? I want to protect my servers on all levels, why not in the servers via script. I assume I must fix this script to be useful for me, but... (1 Reply)
Discussion started by: tomislav91
1 Replies
PARSE_URL(3)								 1							      PARSE_URL(3)

parse_url - Parse a URL and return its components

SYNOPSIS
mixed parse_url (string $url, [int $component = -1]) DESCRIPTION
This function parses a URL and returns an associative array containing any of the various components of the URL that are present. This function is not meant to validate the given URL, it only breaks it up into the above listed parts. Partial URLs are also accepted, parse_url(3) tries its best to parse them correctly. PARAMETERS
o $url - The URL to parse. Invalid characters are replaced by _. o $component - Specify one of PHP_URL_SCHEME, PHP_URL_HOST, PHP_URL_PORT, PHP_URL_USER, PHP_URL_PASS, PHP_URL_PATH, PHP_URL_QUERY or PHP_URL_FRAGMENT to retrieve just a specific URL component as a string (except when PHP_URL_PORT is given, in which case the return value will be an integer). RETURN VALUES
On seriously malformed URLs, parse_url(3) may return FALSE. If the $component parameter is omitted, an associative array is returned. At least one element will be present within the array. Potential keys within this array are: o$scheme - e.g. http o$host o$port o$user o$pass o$path o$query - after the question mark ? o$fragment - after the hashmark # If the $component parameter is specified, parse_url(3) returns a string (or an integer, in the case of PHP_URL_PORT) instead of an array. If the requested component doesn't exist within the given URL, NULL will be returned. CHANGELOG
+--------+---------------------------------------------------+ |Version | | | | | | | Description | | | | +--------+---------------------------------------------------+ | 5.4.7 | | | | | | | Fixed host recognition when scheme is omitted | | | and a leading component separator is present. | | | | | 5.3.3 | | | | | | | Removed the E_WARNING that was emitted when URL | | | parsing failed. | | | | | 5.1.2 | | | | | | | Added the $component parameter. | | | | +--------+---------------------------------------------------+ EXAMPLES
Example #1 A parse_url(3) example <?php $url = 'http://username:password@hostname:9090/path?arg=value#anchor'; var_dump(parse_url($url)); var_dump(parse_url($url, PHP_URL_SCHEME)); var_dump(parse_url($url, PHP_URL_USER)); var_dump(parse_url($url, PHP_URL_PASS)); var_dump(parse_url($url, PHP_URL_HOST)); var_dump(parse_url($url, PHP_URL_PORT)); var_dump(parse_url($url, PHP_URL_PATH)); var_dump(parse_url($url, PHP_URL_QUERY)); var_dump(parse_url($url, PHP_URL_FRAGMENT)); ?> The above example will output: array(8) { ["scheme"]=> string(4) "http" ["host"]=> string(8) "hostname" ["port"]=> int(9090) ["user"]=> string(8) "username" ["pass"]=> string(8) "password" ["path"]=> string(5) "/path" ["query"]=> string(9) "arg=value" ["fragment"]=> string(6) "anchor" } string(4) "http" string(8) "username" string(8) "password" string(8) "hostname" int(9090) string(5) "/path" string(9) "arg=value" string(6) "anchor" Example #2 A parse_url(3) example with missing scheme <?php $url = '//www.example.com/path?googleguy=googley'; // Prior to 5.4.7 this would show the path as "//www.example.com/path" var_dump(parse_url($url)); ?> The above example will output: array(3) { ["host"]=> string(15) "www.example.com" ["path"]=> string(5) "/path" ["query"]=> string(17) "googleguy=googley" } NOTES
Note This function doesn't work with relative URLs. Note This function is intended specifically for the purpose of parsing URLs and not URIs. However, to comply with PHP's backwards com- patibility requirements it makes an exception for the file:// scheme where triple slashes (file:///...) are allowed. For any other scheme this is invalid. SEE ALSO
pathinfo(3), parse_str(3), http_build_query(3), http_build_url(3), dirname(3), basename(3), RFC 3986. PHP Documentation Group PARSE_URL(3)
All times are GMT -4. The time now is 04:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy