When an SEO professional tells you that he or she will secure incoming links for you, ask them to tell you specifically how they will do so. The correct answer is that they will target specific, pre-existing and established websites to gain an incoming link from them to you (in most cases without having to link back to them). If a professional tells you that they will build you hundreds or thousands of pages across different domains that will link to your website, do NOT work with them as this will severely cripple your website.
After the collapse of Napster, with places like donkax and the one and only original html suprnova, a brand new era of file sharing was upon mankind. Switch from the regular p2p networks to bittorrent seemed somewhere along the lines of changing a beat up dodge for a shiny new ferrari (blond included). Lightning fast and error free transfers of premium content, which previously took ages to receive and distribute now flowed like the precious spice throughout the filesharing galaxy. Luckily emperors were too busy to notice, while they were raping those poor few pioneers behind “napster like” p2p networks and and dump ftp “owners”, that a whole lot besides regular file sharing in its traditional sense, was going on. Spiraling out of control a brand new fully blown culture of file sharing was finding its ways into every other way of society. It was no longer something only a few chose to participate in, the event truly took a firm place, in average persons life, somewhere between the toaster and tv.
When writing about social engineering it’s probably appropriate to start with a quote from the most famous of social engineers; “Hackers are going to go after the weakest link in the security chain, which is always the people. You can have the best security in the world, but if I can convince one person in the company to give me sensitive information, your security budget has been wasted.” - Kevin Mitnick (2007).
Social engineering is the named coined to the approach of manipulating a social situation in order to gain information on a specific target which is done on a covert level (i.e. the target does not know the real reasons for the request of the information). This information is then used to gain further sensitive information.
Linux allows you to set limits on the amount of system resources that users and groups can use. This is also very handy if bugs in programs accidentally use up too much resources, slow down the machine, or even render the system unusable. I've seen systems where incorrect settings have allowed programs to use up too much resources which made the server unresponsible for new connections or local logins (e.g. a program uses up all file handles on the system). This could become a security issue if someone is allowed to use up all resources and causes a denial of service attack. Depending on your environment you may want to review resource limits for user accounts and groups.
In the field of IT systems security, concept of” port knocking” is relatively new. However with the passage of time, it is getting popular day by day among system and security administrators.
Port knocking is a method of externally opening ports on a firewall by generating a connection attempt on a set of pre-specified closed ports. Once a correct sequence of connection attempts is received, the firewall rules are dynamically modified to allow the host which sent the connection attempts to connect over specified port (s).
Malicious SSH login attempts have been appearing in some administrators' logs for several years. This article revisits the use of honeypots to analyze malicious SSH login attempts and see what can be learned about this activity. The article then offers recommendations on how to secure one's system against these attacks.
This tutorial shows you how to use netfilter to set up a powerful Linux stateful firewall. All you need is an existing Linux system that's currently using a Linux 2.4.x or 2.6.x kernel. A laptop, workstation, router or server with at a Linux 2.4.x or 2.6.x kernel will do. You should be reasonably familiar with standard network terminology like IP addresses, source and destination port numbers, TCP, UDP and ICMP, etc. By the end of the tutorial, you'll understand how Linux stateful firewalls are put together and you'll have several example configurations to use in your own projects.
Defining our goal
In this tutorial, we're going to put together a Linux stateful firewall. Our firewall is going to run on a Linux laptop, workstation, server, or router; its primary goal is to allow only certain types of network traffic to pass through. To increase security, we're going to configure the firewall to drop or reject traffic that we're not interested in, as well as traffic that could pose a security threat.
Before we start designing a firewall, we need to do two things. First, we need to make sure
that the "iptables" command is available. As root, type "iptables" and see if it exists. If it
doesn't, then we'll need to get it installed first. Here's how: head over to
http://netfilter.samba.org and grab the most recent version of iptables.tar.gz
Once installed, you should have an "iptables" command available for use, as well as the handy iptables man page ("man iptables"). Great; now all we need is to make sure that we have the necessary functionality built into the kernel. This tutorial assumes that you compile your own kernels. Head over to /usr/src/linux, and type "make menuconfig" or "make xconfig"; we're going to enable some kernel network functionality.
