Tuesday, October 5, 2010
Monday, October 4, 2010
All security test failed 100% solution! [BY 73rajsingh]
we know that
when come security test failed
solution
1. super sd auth or pmm auth than write good or modified pm ( must need pm 1 & 309)
or, 2. sd repair super sd auth or pmm auth than write good or modified pm ( must need pm 1 & 309)
yes! we have this solution
1. first backup rpl ( go > imei and security tab > imei rebuild > backup rpl)
2. erase old pm ( go > pm tab > erase )
3. must backup rpl before do this)Reset npc data ( go> imei and security tab> reset NPC data)(
4. Erase pm again (go > pm tab > erase )
5.Write rpl from backup ( go > imei and security tab > imei rebuild > restore imei)
6. go pm tab > super sd auth or pmm auth > than write good or modified pm ( must need pm 1 & 309)
7. erase pm again
8. Recover CERT ( go>imei and security tab> imei rebuild > recover cert)
9. give full factory reset
when come security test failed
solution
1. super sd auth or pmm auth than write good or modified pm ( must need pm 1 & 309)
or, 2. sd repair super sd auth or pmm auth than write good or modified pm ( must need pm 1 & 309)
yes! we have this solution
1. first backup rpl ( go > imei and security tab > imei rebuild > backup rpl)
2. erase old pm ( go > pm tab > erase )
3. must backup rpl before do this)Reset npc data ( go> imei and security tab> reset NPC data)(
4. Erase pm again (go > pm tab > erase )
5.Write rpl from backup ( go > imei and security tab > imei rebuild > restore imei)
6. go pm tab > super sd auth or pmm auth > than write good or modified pm ( must need pm 1 & 309)
7. erase pm again
8. Recover CERT ( go>imei and security tab> imei rebuild > recover cert)
9. give full factory reset
Friday, October 1, 2010
10 Fast and Free Security Enhancements
Before you spend a time on security, there are many precautions you can take that will protect you against the most common threats.
1. Check Windows Update and Office Update regularly (_http://office.microsoft.com/productupdates); have your Office CD ready. Windows Me, 2000, and XP users can configure automatic updates. Click on the Automatic Updates tab in the System control panel and choose the appropriate options.
2. Install a personal firewall. Both SyGate (_www.sygate.com) and ZoneAlarm (_www.zonelabs.com) offer free versions.
3. Install a free spyware blocker. Our Editors' Choice ("Spyware," April 22) was SpyBot Search & Destroy (_http://security.kolla.de). SpyBot is also paranoid and ruthless in hunting out tracking cookies.
4. Block pop-up spam messages in Windows NT, 2000, or XP by disabling the Windows Messenger service (this is unrelated to the instant messaging program). Open Control Panel | Administrative Tools | Services and you'll see Messenger. Right-click and go to Properties. Set Start-up Type to Disabled and press the Stop button. Bye-bye, spam pop-ups! Any good firewall will also stop them.
5. Use strong passwords and change them periodically. Passwords should have at least seven characters; use letters and numbers and have at least one symbol. A decent example would be f8izKro@l. This will make it much harder for anyone to gain access to your accounts.
6. If you're using Outlook or Outlook Express, use the current version or one with the Outlook Security Update installed. The update and current versions patch numerous vulnerabilities.
7. Buy antivirus software and keep it up to date. If you're not willing to pay, try Grisoft AVG Free Edition (Grisoft Inc., w*w.grisoft.com). And doublecheck your AV with the free, online-only scanners available at w*w.pandasoftware.com/activescan and _http://housecall.trendmicro.com.
8. If you have a wireless network, turn on the security features: Use MAC filtering, turn off SSID broadcast, and even use WEP with the biggest key you can get. For more, check out our wireless section or see the expanded coverage in Your Unwired World in our next issue.
9. Join a respectable e-mail security list, such as the one found at our own Security Supersite at _http://security.ziffdavis.com, so that you learn about emerging threats quickly and can take proper precautions.
10. Be skeptical of things on the Internet. Don't assume that e-mail "From:" a particular person is actually from that person until you have further reason to believe it's that person. Don't assume that an attachment is what it says it is. Don't give out your password to anyone, even if that person claims to be from "support."
1. Check Windows Update and Office Update regularly (_http://office.microsoft.com/productupdates); have your Office CD ready. Windows Me, 2000, and XP users can configure automatic updates. Click on the Automatic Updates tab in the System control panel and choose the appropriate options.
2. Install a personal firewall. Both SyGate (_www.sygate.com) and ZoneAlarm (_www.zonelabs.com) offer free versions.
3. Install a free spyware blocker. Our Editors' Choice ("Spyware," April 22) was SpyBot Search & Destroy (_http://security.kolla.de). SpyBot is also paranoid and ruthless in hunting out tracking cookies.
4. Block pop-up spam messages in Windows NT, 2000, or XP by disabling the Windows Messenger service (this is unrelated to the instant messaging program). Open Control Panel | Administrative Tools | Services and you'll see Messenger. Right-click and go to Properties. Set Start-up Type to Disabled and press the Stop button. Bye-bye, spam pop-ups! Any good firewall will also stop them.
5. Use strong passwords and change them periodically. Passwords should have at least seven characters; use letters and numbers and have at least one symbol. A decent example would be f8izKro@l. This will make it much harder for anyone to gain access to your accounts.
6. If you're using Outlook or Outlook Express, use the current version or one with the Outlook Security Update installed. The update and current versions patch numerous vulnerabilities.
7. Buy antivirus software and keep it up to date. If you're not willing to pay, try Grisoft AVG Free Edition (Grisoft Inc., w*w.grisoft.com). And doublecheck your AV with the free, online-only scanners available at w*w.pandasoftware.com/activescan and _http://housecall.trendmicro.com.
8. If you have a wireless network, turn on the security features: Use MAC filtering, turn off SSID broadcast, and even use WEP with the biggest key you can get. For more, check out our wireless section or see the expanded coverage in Your Unwired World in our next issue.
9. Join a respectable e-mail security list, such as the one found at our own Security Supersite at _http://security.ziffdavis.com, so that you learn about emerging threats quickly and can take proper precautions.
10. Be skeptical of things on the Internet. Don't assume that e-mail "From:" a particular person is actually from that person until you have further reason to believe it's that person. Don't assume that an attachment is what it says it is. Don't give out your password to anyone, even if that person claims to be from "support."
Remote Desktop Through Company Firewall [www.mobilerdx.com]
Dont wanna take any credit for this as i got this from another forum.
A lot of people I know love using the Windows Remote Desktop feature at work, however are prevented from connecting to their home computer because of the company firewall. This is because most corporate firewalls block port 3389 which Remote Desktop uses. Most just switch to VNC, however most find it slower than Remote Desktop.
This quick tutorial shows how (from a fire walled network that blocks port 3389) you can access your home computer using MS Remote Desktop.
*This tutorial assumes you have or know how to setup and dynamic DNS client if you need one
*Assumes you know how to setup port forwarding if you need to.
Because Remote Desktop is using port 3389 by default, it is not possible to go through a firewall. So you can use port 443. Because this port is always open on your companies firewall to allow https. (One would assume )
At your home PC:
1) Configure Your pc to allow Remote Connections in your System Properties (windows - Break) tab Remote. Check 'Allow users to connect remote to this computer.
2) (add users if needed)
3) According to
CODE
http://support.microsoft.com/default.aspx?scid=kb;en-us;306759]
In the registry change
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber to 443 (click Decimal radio button first)
*Configure your firewall to allow traffic through port 443 (If you need to)
*Configure your route to forward port 443 to your computer (If you need to)
If you have IIS running you have to change the port number of https. because it is already listening on this port.
C:\WINDOWS\system32\cscript.exe c:\inetpub\adminscripts\adsutil.vbs SET w3svc/1/
SecureBindings ":444:"
Or just disable IIS Service
For your PC at work:
According to
CODE
http://support.microsoft.com/default.aspx?scid=kb;en-us;304304
you can just type the port after the IP-Address of your home PC.
*Or if you have a Dynamic DNS Client such as No-IP or DynDNS you can type in that address.
Alternatively
You can add the following to the rdp file. (which you can get to click on Save As on the tab General of Remote Desktop Connection)
server port:i:443
Extra tip: to have access to your clients hard disk on your remote desktop, check Disk Drives on the tab Local Resources of Remote Desktop Connection
A lot of people I know love using the Windows Remote Desktop feature at work, however are prevented from connecting to their home computer because of the company firewall. This is because most corporate firewalls block port 3389 which Remote Desktop uses. Most just switch to VNC, however most find it slower than Remote Desktop.
This quick tutorial shows how (from a fire walled network that blocks port 3389) you can access your home computer using MS Remote Desktop.
*This tutorial assumes you have or know how to setup and dynamic DNS client if you need one
*Assumes you know how to setup port forwarding if you need to.
Because Remote Desktop is using port 3389 by default, it is not possible to go through a firewall. So you can use port 443. Because this port is always open on your companies firewall to allow https. (One would assume )
At your home PC:
1) Configure Your pc to allow Remote Connections in your System Properties (windows - Break) tab Remote. Check 'Allow users to connect remote to this computer.
2) (add users if needed)
3) According to
CODE
http://support.microsoft.com/default.aspx?scid=kb;en-us;306759]
In the registry change
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber to 443 (click Decimal radio button first)
*Configure your firewall to allow traffic through port 443 (If you need to)
*Configure your route to forward port 443 to your computer (If you need to)
If you have IIS running you have to change the port number of https. because it is already listening on this port.
C:\WINDOWS\system32\cscript.exe c:\inetpub\adminscripts\adsutil.vbs SET w3svc/1/
SecureBindings ":444:"
Or just disable IIS Service
For your PC at work:
According to
CODE
http://support.microsoft.com/default.aspx?scid=kb;en-us;304304
you can just type the port after the IP-Address of your home PC.
*Or if you have a Dynamic DNS Client such as No-IP or DynDNS you can type in that address.
Alternatively
You can add the following to the rdp file. (which you can get to click on Save As on the tab General of Remote Desktop Connection)
server port:i:443
Extra tip: to have access to your clients hard disk on your remote desktop, check Disk Drives on the tab Local Resources of Remote Desktop Connection