If you use Blogger you may have noticed that by default, Blogger places space between gadgets appearing in your sidebar (or sidebars).
Removing the space between HTML/Javascript gadgets (such as AdSense ads) is easy - simply merge the HTML scripts together. For example, if you have an AdSense script and an image link (like in my sidebar), cut and paste the script from the second gadget, and add it to the bottom of the first gadget. Remove the second HTML gadget. Apply to blog, and test it out to ensure proper formatting. You can stack as many HTML gadgets together as you like.
Removing the space between non-HTML/Javascript gadgets (such as the Blog archive, hit counter, etc.) is a little trickier. However, this blog has posted an excellent guide. Given the complexity of this, I strongly suggest backing up your blog first - click the Settings tab in the Dashboard, and choose "Export Blog" to save a copy to your computer. If something goes horribly wrong, you can always restore it.
Monday, July 25, 2011
Monday, July 4, 2011
How to Detect and Remove TDL4 / TDL3 / TDSS / Alureon Rootkits
Experts are continuing to say scary things about TDL4 and its botnet, throwing around terms like "virtually indestructible". Whether this is true or not, clearly TDL4 is a highly sophisticated piece of crimeware that has top researchers very concerned.
If you think you may be infected, Kaspersky Labs has released a free tool for Windows users (all versions, 32 and 64-bit) called TDSSKiller which will detect and remove TDL4 rootkits / bootkits. It can be downloaded here.
TDSSKiller also detects other TDSS-family rootkits such as TDL2 / TDL3, and unknown rootkits by analyzing for:
If you have no luck with TDSSKiller, you may wish to try Norman TDSS Cleaner, Avast's aswMBR Tool, or HitMan Pro, which also claim to detect and remove TDL3, TDL4 and its variants.
If you think you may be infected, Kaspersky Labs has released a free tool for Windows users (all versions, 32 and 64-bit) called TDSSKiller which will detect and remove TDL4 rootkits / bootkits. It can be downloaded here.
TDSSKiller also detects other TDSS-family rootkits such as TDL2 / TDL3, and unknown rootkits by analyzing for:
- Hidden or Blocked services
- Hidden or Blocked files
- Forged files
- Rootkit.Win32.Backboot.gen (generic / unknown MBR infection)
If you have no luck with TDSSKiller, you may wish to try Norman TDSS Cleaner, Avast's aswMBR Tool, or HitMan Pro, which also claim to detect and remove TDL3, TDL4 and its variants.
Thursday, June 23, 2011
How to Create Custom / Separate Windows 7 Firewall Policies for Individual Users
How to Create Windows 7 Firewall Policies for Different Users:
For various reasons, you may wish to have an account with strict firewall policies (such as those detailed in this post), and another account with more relaxed policies.
In order to do this, both accounts must be Administrators.This may also work with Vista Firewall, unfortunately I don't currently have a Vista box to test it on. This will not work on Windows Vista.
1. Before doing anything, back up your current firewall policy. Run Windows Firewall with Advanced Security (type firewall in Run box).
2. In the right pane, click Export Policy. Save to c:\, as firewallstd.wfw.
3. Create the policies you wish to implement, and export as c:\firewallstrict.wfw.
4. Create this batch file, and save as c:\firewallstd.bat:
------------------------
netsh advfirewall import c:\firewallstd.wfw
pause
------------------------
5. Create this batch file, as save as c:\firewallstrict.bat:
------------------------
netsh advfirewall import c:\firewallstrict.wfw
pause
------------------------
6. Open Task Scheduler (type task in Run box).
7. Choose Create a Basic Task.
8. Name this rule as you see fit.
9. For task trigger, select When I Log on.
10. Choose Start a Program.
11. Choose the .BAT file you created earlier. The finishing dialog will appear. Before clicking Finish, tick "Open the Properties dialog for this task when I click Finish".
12. In the resulting window, select Run with Highest Privileges.
Once this is complete, log on to the other account and repeat steps 6 through 12, with the policies you desire for that account. You can remove the "pause" from the batch file if you prefer, but it is helpful to confirm that the policy has properly loaded upon logging in.
For various reasons, you may wish to have an account with strict firewall policies (such as those detailed in this post), and another account with more relaxed policies.
In order to do this, both accounts must be Administrators.
1. Before doing anything, back up your current firewall policy. Run Windows Firewall with Advanced Security (type firewall in Run box).
2. In the right pane, click Export Policy. Save to c:\, as firewallstd.wfw.
4. Create this batch file, and save as c:\firewallstd.bat:
------------------------
netsh advfirewall import c:\firewallstd.wfw
pause
------------------------
5. Create this batch file, as save as c:\firewallstrict.bat:
------------------------
netsh advfirewall import c:\firewallstrict.wfw
pause
------------------------
6. Open Task Scheduler (type task in Run box).
7. Choose Create a Basic Task.
8. Name this rule as you see fit.
9. For task trigger, select When I Log on.
10. Choose Start a Program.
11. Choose the .BAT file you created earlier. The finishing dialog will appear. Before clicking Finish, tick "Open the Properties dialog for this task when I click Finish".
12. In the resulting window, select Run with Highest Privileges.
Once this is complete, log on to the other account and repeat steps 6 through 12, with the policies you desire for that account. You can remove the "pause" from the batch file if you prefer, but it is helpful to confirm that the policy has properly loaded upon logging in.
Subscribe to:
Posts (Atom)