• [ Kill the Process, Use Killbox if your Access Denied ]

[In Windows Vista Run As Administrator, After Execution System Will Restart]

• W32/Magania.BIHR Trojan
• %Windows\System32\dllcache\ahnsbsb.exe
• %Windows\System32\ahnxsds0.dll
• %Windows\System32\ahnfgss1.dll
• %Root of Windows installed Drive\vvnbry9s.bat
• %Root of Windows installed Drive\lot.exe
• W32/Magania.BHBT Trojan
• %Windows\System32\dllcache\cdaudio.sys
• %Windows\System32\kacsde.exe
• %Windows\System32\godert0.dll
• W32/Magania.AYOR Trojan
• %Windows\System32\kva8wr.exe
• %Windows\System32\bgotrtu0.dll
• %Windows\System32\uweyiwe0.dll
• %Windows\System32\ahnsbsb.exe
• %Windows\System32\ahnxsds0.dll
• %Windows\System32\ahnfgss0.dll
• %Root of Windows installed Drive\pmut.bat
• %Root of Windows installed Drive\lot.exe
• W32/Magania.BGMT Trojan
• %Documents and Settings\Default User\Local Settings\Temp\xvassdf.exe
• %Documents and Settings\Default User\Local Settings\Temp\4tddfwq0.dll
• %Windows\System32\dllcache\cdaudio.sys
• %Windows\System32\xvassdf.exe
• %Windows\System32\4tddfwq0.dll
• %Root of Windows installed Drive\3m2.exe
• %Root of Windows installed Drive\6fq.com
  [ No Exact Information about Files, search above related files in Program files Folder ]
  If you have any of these files in running process from task manger, end the process before removal.
  Note: if task manager is disabled, Download the following file, Click to Download - Enable Registry.reg[ Right Click - Save Target As/Linked Content As ]
  Open it with Regedit.exe [%system32\regedit.exe], then it Confirms Add to registry Yes or No, Confirm Yes, then click Ok.
  

Previous post: Widget Anatomy – Performance and battery life

This is part four of my Widget Anatomy series which which will explain the ins and outs of the Widget Framework that is shipping as part of Windows Mobile 6.5.  In this installment I will discuss the Widget Framework’s security model..

Inside the sandbox – The Widget Framework security model

It is true, Widgets are executed inside a sandbox, and because of this, there are bounded to a rather strict security policy but can be summarized as follows:

1. Widgets can’t read files from the device nor can access the registry directly.  A notable exception are all files that are part of the Widget package itself.
2. Cookies can be used as temporary storage but developers are encouraged to use the persistent storage API instead.   Cookies, browser history and local cache are  isolated per widget and completely separated from the browser.
3. Widgets can’t navigate their main frame to any URL with the exception of fragment inside itself.  You can use an iframe to open a web URL though.
4. Widgets can navigate to the following specific purpose URIs

URI	Description	Example
SMS:	Starts composing an SMS message addressed to the given phone number	sms:1111111111
mailto:	Starts composing a mail message using the specified parameters (Like destination, subject and body)	mailto:test@test.com?subject=Hello?body=From%20Here
callto:	Initiates a voice call to the given number	callto:1111111111
tel:	Initiates a voice call to the given number	tel:1111111111
http:, https:	Opens the specified URI using the default browser.	http://www.microsoft.com

Widgets and the Marketplace

Windows Mobile 6.5 restricts distribution of Widgets to trusted sources only.  This means consumers will only be able to install widgets from the Marketplace and, on some cases, Mobile Operator stores directly.  This restriction was implemented because we don’t currently support digital signature verification for widget files which prevents users from being able to verify the origins and authenticity of any given widget.  This might seem a little restrictive but I believe it provides the right balance between security and flexibility, specially if you consider that there are ways to allow enthusiasts and developers to install widgets from non-trusted sources, as long as they acknowledge and understand the risks of doing so.  Use your best judgment :).

Other important security considerations

• The local persistent storage is unencrypted, use caution when storing information that should be protected in clear text.
• The widget ID is sent to the server as part of the user agent string if you would like to use it on your server for any reason.
• Widget files are stored unencrypted on the device file system so anyone with device access can potentially read them.
• Cross domain data access is allowed, this is super important for widgets since they can be used to mash up data from multiple sources.

That’s it for now, feel free to comment about any other security related questions that were not covered.

Next post: Widget Anatomy – Touch and D-Pad inputs, oh joy!

To Unix systems, a filesystem is a device (such as a partition) that is formatted to store files. Filesystems can be found on hard drives, floppies, CD-ROMs, USB drives, or other storage media that permit random access.

The exact format and means by which the files are stored are not important; the system provides a common interface for all filesystem types that it recognizes. By default, almost all modern distributions of Linux use a journaling filesystem. When the kernel interacts with a journalling filesystem, writes to disk are first written to a log or journal before they are written to disk. This slows down writes to the filesystem, but reduces the risk of data corruption in the event of a power outage. It also speeds up reboots after a system unexpectedly loses power.

Most current Linux distributions default to the Third Extended (ext3) Filesystem. The ext3 filesystem was developed primarily for Linux and supports 256-character filenames and 4-terabyte maximum filesystem size. This ext3 filesystem is essentially a Second Extended (ext2) filesystem with an added journal. Since it is in all other ways identical to the ext2 system, it is both forward- and backward-compatible with ext2—all ext2 utilities work with ext3 filesystems.

Although not covered in this edition of Linux in a Nutshell, Linux supports other open source journaling filesystems including: IBM’s Journaled Filesystem (JFS), SGI’s Extensible Filesystem (XFS), and the Naming System Venture’s Reiser Filesystem (ReiserFS). In some situations these can be faster than ext3. Some Linux distributions use these alternative filesystems by default. Other common filesystems include the FAT and VFAT filesystems, which allow files on partitions and floppies of Microsoft Windows systems to be accessed under Linux, and the ISO 9660 filesystem used by CD-ROMs.



Common Command about Managing Filesystems

debugfs Debug ext2 filesystem.
dosfsck Check and repair a DOS or VFAT filesystem.
dump Back up data from a filesystem.
dumpe2fs Print information about superblock and blocks group.
e2fsck Check and repair an ext2 filesystem.
e2image Store disaster-recovery data for an ext2 filesystem.
e2label Label an ext2 filesystem.
edquota Edit filesystem quotas with vim.
fdformat Format floppy disk.
fsck Another name for e2fsck.
fsck.ext2 Check and repair an ext2 filesystem.
mke2fs Make a new ext2 filesystem.
mkfs Make a new filesystem.
mkfs.ext2 Another name for mke2fs.
mkfs.ext3 Yet another name for mke2fs.
mklost+found Make lost+found directory.
mkraid Set up a RAID device.
mkswap Designate swapspace.
mount Mount a filesystem.
quotacheck Audit stored quota information.
quotaon Enforce quotas.
quotaoff Do not enforce quotas.
quotastats Display kernel quota statistics.
rdev Describe or change values for root filesystem.
repquota Display quota summary.
resize2fs Enlarge or shrink an ext2 filesystem.
restore Restore data from a dump to a filesystem.
rootflags List or set flags to use in mounting root filesystem.
setquota Edit filesystem quotas.
showmount List exported directories on a remote host.
swapoff Cease using device for swapping.
swapon Begin using device for swapping.
sync Write filesystem buffers to disk.
tune2fs Manage an ext2 filesystem.
umount Unmount a filesystem.
warnquota Mail disk usage warnings to users.


Source of Information : OReilly Linux in a Nutshell 6th Edition

In case you missed it, Maximum PC recently released one of the most comprehensive how-to article on building your own Windows Home Server that we have ever seen. The article is generating a lot of buzz, and you can check it out online here or head down to your local bookstore and peruse the 10-page, full-color spreads. The article walks through all the key features of Windows Home Server – including automatic backups, file sharing, remote access, media streaming throughout the home, and hard drive expandability. And according to Maximum PC: “More than just a stripped-down version of Windows Server 2003, WHS has numerous features that make it ideal for small home networks.” This is a fact we have been proudly touting for some time. You can check out more information on Windows Home Server for SOHO on our Web page, which features information for small businesses, including case studies and video interviews with some of our customers.

The second part of Maximum PC’s review walks you step-by-step – including handy photos to illustrate the process – on how to build your own server. If you don’t want to do it yourself, check out the reviews at the end of the HP MediaSmart LX195 and the Acer EasyStore H340 – great products from our partners. You can also read about some of the cool add-ins developed by our Windows Home Server community that extend the functionality of your Windows Home Server, including Advanced Admin Consol, Disk Management, Web Folders 4 Windows Home Server, Photosync, and My Movies, just to name a few. There have been so add-ins built for Windows Home Server by our passionate community of technical enthusiasts that we’ve almost lost count! I believe we’re at more than 100 add-ins and counting. Find out more about add-ins here – they will help simplify your family's digital lifestyle and enhance the functionality of your Windows Home Server.

You don’t have to build your own Windows Home Server to enjoy Maximum PC’s article. It’s chock full of all the great features, benefits, and tips for getting the most out of your Windows Home Server. You don’t want to miss this one! 

- Dave Berkowitz, Senior Product Manager, Core Infrastructure Marketing, Microsoft

It can be frustrating to get a shiny new technology gadget and then realize that it will be another couple of days until you can actually start using it due to confusion and long installation times. Happily, this is not the case with Windows Home Server – it is quite the opposite. Windows Home Server has an uncomplicated, self-explanatory installation process that will have you up and running with minimum time and effort.

According to a Cnet review, an advantage of Windows Home Server is the, “straightforward hardware and software setup.” The Windows Home Server team and our hardware partners have continued to make improvements to the installation and setup of the home server. Many consumers, including blogger Steve Smith, make it clear that there is no need for you to be computer savvy to set up and install Windows Home Server as it only takes 3 simple steps:

1. Plug it in
2. Turn it on
3. Install the software on your computer

The software will take you through a quick set-up wizard, and then the installation is complete! You can even follow along with a series of screen shots of the Windows Home Server installation process, or read a "How To" to make sure that you are on the right track.

*Screen shot of the Windows Home Server Connector during installation

You can see for yourself how impressed Windows Home Server owner, Steve Smith, was with his HP MediaSmart. His first reaction to his new Home Server after un-boxing it was, “Wow, this thing is small!”

*HP MediaSmart’s size compared to a Blackberry Pearl phone

In Steve's blog, he then goes on to describe how fast the installation was and ends by showing a final screen shot of the Windows Home Server console, only 40 minutes after opening the box! If you prefer videos, Ian Dixon walks through an HP MediaSmart Server installation here.

For those who are not intimidated by computer installations and would consider building their own home server, Norman Chan has produced a terrific article in October’s Maximum PC on this topic. This step-by-step guide will you take you through the process of building your own home server. Click here to check out the online version.

If you still on the fence about building your own home server or installing a preconfigured system, you can now feel confident that others have already successfully gone down the path.

To learn more about Windows Home Server, please visit our Web page at: http://www.microsoft.com/windows/products/winfamily/windowshomeserver/default.mspx

-Nicole