WTF *Nix

Just another *nix Blog

Archive for the ‘firewall’ Category

I’m starting to see a trend here, seems their MW on MyCrackedSpace (MySpace) is running way smoother than it is on Crackbook… (Facebook)

The trend can be found here in what I’m talking about in the times for a Scheduled Maintenance on both:

30 minutes for MySpace

3 hours for Facebook

This goes to show you, this is a bit out of whack on FB for FB has been having some serious @#$ked up issues with the Developer API, I just fixed an app for a client of mine last week to counter Facebook’s developer HAVOC. (freaking’ nightmare)

Long story short, it seems FB is putting down some pressure on all the larger apps out there for security and privacy issues. Let’s just hope and pray that Zynga can pull out of this one, because they are facing lots of obstacles here which seems to be broken on the FB side of things…

Also we all know that Zynga’s servers responses are slow, which is one thing on Zynga’s end, which I can understand when you grow so fast and no more room to grow on… You scurry and make mistakes as you are scurrying… WITHOUT Q&A and a proper testing team in place, you will encounter bugs galore!!!

All the power to Zynga on trying to fix their issues, my hats off to them once they do! So I take back for the remarks against Zynga on this issue they are facing. It’s more than you can even write in “Layman Terms.”

So WTF get’r done!!!!

Share and Enjoy:
  • Google Bookmarks
  • MySpace
  • Facebook
  • StumbleUpon
  • Print
  • email
  • Digg

Rootkits – ewwwwww

Dec-14-2009 By WTF *Nix

If you’re concerned about security on your computer network, there’s a new word to add to your vocabulary – rootkit. A rootkit is a set of utilities installed on your computer whose purpose is to hide what other programs are doing. They’ve been around for a few years, but they didn’t really hit the security spotlight until November 2005. That was when researchers discovered that some CDs from Sony were installing a rootkit on user computers as part of their DRM (Digital Rights Management) software. The purpose of the rootkit was to prevent the DRM software from being detected and uninstalled – but there was an unintended side effect. The rootkit  opened a security hole on those computers that couldn’t be detected by standard security software, and left them vulnerable to attacks by malicious software and hackers.
That’s bad news for users and IT professionals who depend on virus  and spyware detection programs to alert them to an invader on their networks. Generally, when you’re computer is infected by spyware  or malware , it can be detected by monitoring your computer activity. You can check the running processes and find programs that shouldn’t be loaded. You can run a virus or spyware scanner to find registry keys and files that fit certain patterns. You can monitor activity coming in over a network.
A rootkit makes all of those defenses worthless by hiding the keys, files, processes and communications from your computer operating system. What your computer can’t see, it can’t report and you can’t fix. The methods used to hide the files and processes vary and are getting more and more sophisticated. Most do it by ‘hooking’ into a process that Windows expects to find running, either by replacing the process files, or by adding itself into them.
With the rootkit in place, the hacker has a virtual backdoor into your system. He can read your keystrokes, record passwords, gather information from your network and change your data and files. A hacker with access to your system through a rootkit can reinstall hacking programs, access your accounts and your users’ accounts and wreak general havoc. It’s the ultimate Trojan backdoor.
Once a rootkit is installed, it’s virtually impossible to detect and remove. When a virus detection or spyware program runs, they don’t see the rootkit processes – they see the process that’s cloaking it. Some may alter their own files with the details and stats associated with the files that they’re replacing so that operating systems don’t notice a difference. A sysadmin who is an expert in network security may be able to detect it by running system checks from an uninfected machine, but most agree that once a rootkit has been installed, the only way to be sure you’ve removed it is to wipe the drive clean and install the operating system.
Because rootkits don’t install themselves, you can block them by blocking attempts to penetrate your network. One way to effectuate this is to install a spyware or malware protection program to help prevent rootkits from being installed at the server level or on individual desktops. The key is to practice excellent network security at all times so that you block the programs that install rootkits.
Article Provided By: http://spyware-removal.thrcomputer.com

If you’re concerned about security on your computer network, there’s a new word to add to your vocabulary – rootkit. A rootkit is a set of utilities installed on your computer whose purpose is to hide what other programs are doing. They’ve been around for a few years, but they didn’t really hit the security spotlight until November 2005. That was when researchers discovered that some CDs from Sony were installing a rootkit on user computers as part of their DRM software. The purpose of the rootkit was to prevent the DRM software from being detected and uninstalled – but there was an unintended side effect. The rootkit opened a security hole on those computers that couldn’t be detected by standard security software, and left them vulnerable to attacks by malicious software and hackers.

That’s bad news for users and IT professionals who depend on virus and spyware detection programs to alert them to an invader on their networks. Generally, when you’re computer is infected by spyware or malware , it can be detected by monitoring your computer activity. You can check the running processes and find programs that shouldn’t be loaded. You can run a virus or spyware scanner to find registry keys and files that fit certain patterns. You can monitor activity coming in over a network.

A rootkit makes all of those defenses worthless by hiding the keys, files, processes and communications from your computer operating system. What your computer can’t see, it can’t report and you can’t fix. The methods used to hide the files and processes vary and are getting more and more sophisticated. Most do it by ‘hooking’ into a process that Windows expects to find running, either by replacing the process files, or by adding itself into them.

With the rootkit in place, the hacker has a virtual backdoor into your system. He can read your keystrokes, record passwords, gather information from your network and change your data and files. A hacker with access to your system through a rootkit can reinstall hacking programs, access your accounts and your users’ accounts and wreak general havoc. It’s the ultimate Trojan backdoor.

Once a rootkit is installed, it’s virtually impossible to detect and remove. When a virus detection or spyware program runs, they don’t see the rootkit processes – they see the process that’s cloaking it. Some may alter their own files with the details and stats associated with the files that they’re replacing so that operating systems don’t notice a difference. A sysadmin who is an expert in network security may be able to detect it by running system checks from an uninfected machine, but most agree that once a rootkit has been installed, the only way to be sure you’ve removed it is to wipe the drive clean and install the operating system.

Because rootkits don’t install themselves, you can block them by blocking attempts to penetrate your network. One way to effectuate this is to install a spyware or malware protection program to help prevent rootkits from being installed at the server level or on individual desktops. The key is to practice excellent network security at all times so that you block the programs that install rootkits.

Share and Enjoy:
  • Google Bookmarks
  • MySpace
  • Facebook
  • StumbleUpon
  • Print
  • email
  • Digg

Bahhhh Web Servers and Firewalls…

Dec-10-2009 By WTF *Nix

Going to break these down into parts for each of you to understand if you are new in this area… I know for a fact there are some gurus out there that may read this and say something along the lines… “What a waste of time…” Well this this isn’t for you ole Mighty Gurus :P

So lets start with…

Web and FTP Servers

Every network that has an internet connection is at risk of being compromised. While there are several steps that you can take to secure your LAN, the only real solution is to close your LAN to incoming traffic, and restrict outgoing traffic.

However some services such as web or FTP servers require incoming connections. If you require these services you will need to consider whether it is essential that these servers are part of the LAN, or whether they can be placed in a physically separate network known as a DMZ (demilitarized zone). Ideally all servers in the DMZ will be stand alone servers, with unique logons and passwords for each server. If you require a backup server for machines within the DMZ then you should acquire a dedicated machine and golden rule is to keep the backup solution separate from the LAN backup solution.

The DMZ will come directly off the firewall, which means that there are two routes in and out of the DMZ, traffic to and from the internet, and traffic to and from the LAN. Traffic between the DMZ and your LAN would be treated totally separately to traffic between your DMZ and the Internet. Incoming traffic from the internet would be routed directly to your DMZ.

Then if any hacker were to compromise a machine within the DMZ, then the only network they would have access to would be the DMZ. The hacker would have little or no access to the LAN. It would also be the case that any virus infection or other security compromise within the LAN would not be able to migrate to the DMZ.

In order for the DMZ to be effective, you will have to keep the traffic between the LAN and the DMZ to a minimum. In the majority of cases, the only traffic required between the LAN and the DMZ is FTP. If you do not have physical access to the servers, you will also need some sort of remote management protocol such as terminal services (SSH, RDC and etc..) or VNC.

Database servers

If your web servers require access to a database server, then you will need to consider where to place your database. The most secure place to locate a database server is to create yet another physically separate network called the “secure zone,” and to place the database server there!!! Not in the UNSECURED ZONE!

The “secure zone” is also a physically separate network connected directly to the firewall. The Secure zone is by definition the most secure place on the network. The only access to or from the secure zone would be the database connection from the DMZ (and LAN if required).

Exceptions to the rule

The dilemma faced by network engineers (monkeys) is where to put the email server. It requires SMTP connection to the internet, yet it also requires domain access from the LAN. If you where to place this server in the DMZ, the domain traffic would compromise the integrity of the DMZ, making it simply an extension of the LAN.  My opinion, the only place you can put an email server is on the LAN and allow SMTP traffic into this server. However I would recommend against allowing any form of HTTP access into this server. If your users require access to their mail from outside the network, it would be far more secure to look at some form of VPN solution. (a brief on why using the VPN solution, is to have the firewall handle the VPN connections. LAN based VPN servers allow the VPN traffic onto the network before it is authenticated, which is NEVER a good practice.)

I know this doesn’t cover EVERYTHING under the sun for security on web servers, however this is just a “brief” overview on why to secure and what to place where in my own experiences…  So get secured and if you have any questions, you know this blog is WIDE-OPEN for you to post up to seek help, and surely I don’t know EVERYTHING yet… I’ll damn sure try to find the answer for you regardless. =)

WTF get’r done!!!

Share and Enjoy:
  • Google Bookmarks
  • MySpace
  • Facebook
  • StumbleUpon
  • Print
  • email
  • Digg