Hot on the heels of the CNN Alerts: my custom alert email spam comes a new variant: msnbc.com: BREAKING NEWS spam.

The emails follow the same format as the CNN spam, with the link to the supposed featured story going to an unrelated third-party website which attempts to attack the users PC.

Read more on SecurityWatch.

• 0 comments »

From SWSOFT's Knowledgebase, here's a step by step information in enabling firewall in a Virtuozzo for Linux VE. (Virtual Environment)

First of all you should define which iptables modules are available for VEs.

Edit /etc/sysconfig/iptables-config and /etc/sysconfig/vz on the hardware node. Add modules you need into IPTABLES_MODULES= and IPTABLES= lines correspondingly. Please note that all iptables modules in /etc/sysconfig/vz file in IPTABLES parameter should be listed in one single line, no linebreaks are allowed in this parameter.

For example, typical firewall configuration requires the following modules:

ipt_REJECT ipt_tos ipt_TOS ipt_LOG ip_conntrack ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_state iptable_nat ip_nat_ftp

The changes will be applied after you load all required modules and restart Virtuozzo service (all VEs will be restarted):

# service vz stop
# service iptables restart
# service vz start

Modules you defined will be available for all VEs. However, you can also define a list of iptables modules for each VE using --iptables option of vzctl utility, e.g.:

# vzctl set 101 --iptables ipt_REJECT --iptables ipt_tos --iptables ipt_TOS --iptables ipt_LOG --iptables ip_conntrack --iptables ipt_limit --iptables ipt_multiport --iptables iptable_filter --iptables iptable_mangle --iptables ipt_TCPMSS --iptables ipt_tcpmss --iptables ipt_ttl --iptables ipt_length --iptables ipt_state --iptables iptable_nat --iptables ip_nat_ftp --save


You will probably need to increase the barrier of numiptent parameter in /proc/user_beancounters using vzctl utility. This parameter limits amount of iptables rules which VE owner is allowed to create. For example, this is how you allow to enter 400 iptables rules on VE 101:

# vzctl set 101 --numiptent 400 --save

• 0 comments »

I'd like to start sharing you really useful problems and fixes from a linux wordpress blogger. Here's one:

Problem:

While logging into Plesk control panel, you may get the following error:
“Access for administrator from address xx.xx.xx.xx is restricted in accordance with IP Access restriction policy currently applied.”


Resolution:

This means Plesk IP access policy was configured in such a way that Plesk cannot be accessed from the current IP. To enable Plesk CP access one needs to login to Plesk Control Panel locally and change IP access policy.

It can be done the following way:

Server > Acess (under the section Administrator information) > Remove necessary IP address/subnet/network

If localhost is also blocked, the Plesk database records regarding access policy need to be corrected.

To retrieve the current policy and restricted/allowed IPs the following commands can be used:

#mysql -uadmin -p`cat /etc/psa/.psa.shadow` -P8306 psa
mysql> select * from cp_access;mysql> select * from misc where param=’access_policy’;
To clear the access policy settings remove all the records from the “cp_access” table and set policy to “allow”:
mysql> delete * from cp_access;mysql> update misc set val=”allow” where param=’access_policy’;

Test and you should be able to login now.

Source: mohammednv

• 0 comments »

Problem:

Cannot access or ping a Virtuozzo VPS. Status in the Virtual Management console shows that the VPS is up and running.

Solution:

After minutes of figuring out why the VE stopped responding, we finally pointed out the culprit. For some reason, the Windows Firewall Service is started automatically! One rule for a Windows VPS is that the firewall should not be running. I know it sounds too risky for the servers not to have a firewall started. But we gotta follow the "VE rules".

Here's how we did it:

Since we cannot access the virtual machine, we used the VZMC to do the needed changes.

1. Login to VZMC.

2. Look for the VPS options. ( Virtual Private Server)

3. Right click the problematic server then hit Manage Virtual Server.

4. Scroll down until you see the Services option.

5. Look for the Windows Firewall service then disable it.

That's it. You know have a working VE again.

• 0 comments »