|
|
|
10 things to know about IE7 Security |
|
Monday, October 01, 2007 |
 Internet Explorer 7 is designed to make browsing safer. Here's a quick rundown of some of the new security features, including Active X opt-in, the Phishing Filter, cross-domain security, enhanced privacy protection, and an international character alert. Some sensationalistic reports of a security flaw immediately followed Internet Explorer 7's final release, but the vulnerability turned out to be in Outlook Express rather than IE. In fact, Microsoft has put a great deal of effort into making IE7 more secure. Here are some of the new IE7 security features and what they can do for you. 1. Default protection from potentially dangerous Active X controls Active X controls that haven't been checked out and verified as safe no longer run automatically by default; instead they're automatically disabled by the Active X opt-in feature. 2. Per-zone control of Active X opt-in You can disable Active X opt-in on a per-zone basis. It's enabled by default on the Internet and restricted sites zones for better security and disabled on the intranet and trusted sites zones. 3. Site and zone locking for Active X controls Developers can now make their Active X controls more secure by restricting a control to run only on a particular site (site locking) or only in a specific security zone (zone locking). 4. Protection against phishing IE7 introduces the Phishing Filter, which helps protect users from being fooled into entering personal information or passwords that can be collected and used for identity theft. The Phishing Filter automatically checks the Web sites you visit against a list of known phishing sites and issues a warning if the site has been identified as a phishing site. If you prefer not to have sites checked automatically, you can check specific sites when you suspect they might be phishing sites. 5. Cross-domain security A tactic called cross-domain scripting is prevented by new IE7 security mechanisms that force scripts to run in their original security context even if they're redirected to a different security domain. 6. Locked down security zones Security zones in IE7 are locked down tighter than before, with higher default security settings, disabling of the intranet zone on non-domain computers, and an interface that makes it harder to select low or medium low security. 7. Better SSL/TLS notification and digital certificate info Users of IE7 can more easily determine whether a Web site is secured by SSL/TLS and get information on the digital certificates issued to the site. Sites with high assurance certificates cause the address bar to turn green. 8. Privacy protection features Three new registry keys, called feature control keys, prevent HTML from getting a user's personal information. In addition, you can easily clear out information you've entered in Web pages, as well as the browser cache (temporary internet files), history, cookies and other personal info, with a single click. 9. Address bars All browser windows in IE7 contain address bars, so it's harder for a malicious site to conceal its identity by hiding the URL of the site. 10. International character alert IE7 supports international characters, but to prevent spoofing that exploits the similarity of characters in different languages, the browser warns you that the characters are in another language when international character sets are used.Labels: Others |
posted by
ZonaNet
@
4:12 PM
 |
|
|
|
|
before and after |
|
Saturday, July 21, 2007 |
the last my job in photo shop workshop ^_^
before
after the colors of my job
thanks....ZonanetLabels: Others |
| posted by
ZonaNet
@
1:45 PM
|
|
|
|
|
alhandasa net logo |
|
Friday, July 20, 2007 |
hi all
all know alhandasa net forums
this is small job of my design
 is Like the original^_^ZonaNet...
Labels: Others |
| posted by
ZonaNet
@
2:39 PM
|
|
|
|
|
Running WPI |
|
Wednesday, June 27, 2007 |
It became apparent that WPI would be useful not only during a full unattended Windows XP installation but also as a stand-alone application to selectively install programs on a pre-configured machine. As a stand-alone app, it would need to start automatically when inserted into the CD-ROM drive. The problem, however, is that standard autorun functionality supports executable files only and not others such as .cmd or .hta.
Enter TARMA SOFTWARE RESEARCH, the creators of AutoRun, a freeware application that supports multiple file types. Placing Tarma's AutoRun executable at the root of the CD togther with a custom .inf file calls WPI when the CD is inserted: AUTORUN.INF:
AUTORUN.INF:
[autorun]open=autorun.exe -q2 -w -x wpi\WPI.hta
cleanup.exeicon=wpi.ico
AutoRun's versatility extends beyond simple .inf installs. For example, it can be called from the hard drive to run, in turn, the WPI .hta, batch files, and compiled AutoIt scripts. My hard drive install routine runs WPI and then performs a cleanup operation before allowing me to alter the machine name and workgroup information. Once uniquely named, the CD is ejected and the machine reboots. The routine is a tad convoluted, like so:
A WinRAR SFX called Run_WPI.exe is placed in the $OEM$ Startup directory and copied over to the hard drive during the OEM install with the following comment:
Path=%windir%\
TempSetup=RunWPI.exe
Silent=1Overwrite=1
Title=Extracting
files...
Run_WPI.exe holds the files AutoRun.exe, RunWPI.exe, and RunWPI.cmd. It is sparked upon first boot and fires up a compiled AutoIt script from the Temp directory called RunWPI.exe. RunWPI.exe hides completely a batch file that, together with Tarma's AutoRun, performs the actual install:
RunWPI.au3:
AutoItSetOption("TrayIconHide",
1)
AutoItSetOption("WinTitleMatchMode", 4)
BlockInput(1)
SplashTextOn("", "" & @CRLF & "Preparing
post-installation..." & @CRLF & "" & @CRLF & "Please wait..."
& @CRLF & "", 320, 90, -1, -1, 1, "Arial", 12,
12)
Sleep(3000)SplashOff()
Run("RunWPI.cmd", "", @SW_HIDE)
Exit
RunWPI.cmd:
@echo off
::Locate the CDROM drive if necessary,
where AUTORUN.INF exists at the root...FOR %%d IN (c: d: e: f: g: h: i: j: k: l:
m: n: o: p: q: r: s: t: u: v: w: x: y: z:) DO IF EXIST %%d\AUTORUN.INF SET
CDROM=%%d
::Run WPI...autorun.exe -q2 -w -x %cdrom%\wpi\WPI.hta
%cdrom%\cleanup.exe %cdrom%\rename.exe
%cdrom%\restart.exe
CLS
EXIT
The following files are placed at the root of the CD to perform post-WPI
operations:
A compiled Cleanup.au3 AutoIt
script:
AutoItSetOption("TrayIconHide",
1)
AutoItSetOption("WinTitleMatchMode", 4)
BlockInput(1)
Run(
@ScriptDir & "\cleanup.cmd", "", @SW_HIDE)
Exit
A corresponding Cleanup.cmd batch file:
@echo off
RD /S /Q "%systemdrive%\Drivers"
ECHO Y Del
"%systemdrive%\WINDOWS\*.bmp"
ECHO Del "%systemdrive%\*.log"
DEL
/F "%systemdrive%\Documents and Settings\All Users\Start
Menu\Programs\Startup\Run_WPI.exe"
@Rmdir %systemdrive%\TEMP /s/q
@mkdir
%systemdrive%\TEMP
@Rmdir %systemdrive%\WINDOWS\TEMP /s/q
@mkdir
%systemdrive%\WINDOWS\TEMP
CLS
EXIT
A compiled Rename.au3 AutoIt script:
AutoItSetOption("TrayIconHide",
1)
AutoItSetOption("WinTitleMatchMode",
4)
BlockInput(1)
Send("#r")
WinWaitActive
("Run")
Send("sysdm.cpl{Enter}")
WinWaitActive("System
Properties")
Send("{TAB 3}")
Send("{RIGHT
1}")
Send("!c")
Send("{BACKSPACE}")
BlockInput(0)
MsgBox(0, "Rename
PC", "Please rename this machine.")
WinWaitActive("Computer Name Changes",
"You must restart this
computer")
BlockInput(1)
Send("{ENTER}")
WinWaitActive("System
Properties")
Send("{ENTER}")
WinWaitActive("System Settings
Change")
Send("!n")
Exit
The author chose to call batch files from AutoIt scripts to hide their activity instead of using the "cmdow @ /HID" convention. Although useful, cmdow.exe nonetheless produces a command window momentarily, whereas AutoIt's "@SW_HIDE" parameter flag hides the window completely.Labels: Others |
| posted by
ZonaNet
@
1:57 PM
|
|
|
|
|
|
