Windows virus on Mac?
in [Anti-Virus]
|
Prev: immunet
Next: LOCKERZ INVITE
From: FromTheRafters on 25 Jan 2010 10:26 "Mr. Strat" <rag(a)nospam.techline.com> wrote in message news:250120100537526908%rag(a)nospam.techline.com... > In article <hjincv$97l$1(a)news.eternal-september.org>, FromTheRafters > <erratic(a)nomail.afraid.org> wrote: > >> http://www.sophos.com/security/analyses/viruses-and-spyware/osxleapa.html > > OK...the standard qualifiers...no OS X viruses so long as there is no > physical access, special rights, or PEBCAK. There is nothing standard about limiting the definition of virus just to suit your argument. It is a virus for the Mac - and runs on OS-X http://www.sophos.com/pressoffice/news/articles/2006/02/macosxleap.html There is nothing about that Mac OS that excludes the possibility or viruses. http://www.macforensicslab.com/ProductsAndServices/index.php?main_page=document_general_info&products_id=174
From: David W. Hodgins on 25 Jan 2010 13:58 On Mon, 25 Jan 2010 03:35:28 -0500, Gavin <invalid(a)nomail.com> wrote: > Her file TUD.EXE can't be deleted from the recycle bin of her Mac. I > thought the reason for not being able to delete the file is because > TUD.EXE is actually running. Linux (and I assume osx) doesn't lock a directory entry, just because a copy of the executable happens to be running. Deleting a file (aka unlink) just removes the directory entry. The inode used by the file will remain in use (by that file), until all programs that have the file open, are closed, at which time the space will be available for reuse. A common example where this matters, shows up when a log file is filling the disk, due to some program generating an error message in a loop. Deleting the log file does not free up the disk space, until the syslog daemon is stopped/restarted. Not being able to delete the file would be caused by either file ownership, or file permissions. Most likely, the file is marked as read only. I expect right clicking on the file, in the file manager, and then selecting properties would allow the write permission for the user to be turned on. Regards, Dave Hodgins -- Change nomail.afraid.org to ody.ca to reply by email. (nomail.afraid.org has been set up specifically for use in usenet. Feel free to use it yourself.)
From: John Gentile on 25 Jan 2010 19:11 On 2010-01-25 03:35:28 -0500, Gavin <invalid(a)nomail.com> said: > On 00:10 24 Jan 2010, FromTheRafters wrote: > >> "Gavin" <invalid(a)nomail.com> wrote in message >> news:Xns9D09E7D7EC3685D4AM2(a)160.sjc.astraweb.com... >>> >>> A friend says her Mac has a file (called TUD.EXE) in the recycle bin >>> which can't be deleted. >>> >>> An online virus scan says it's a Win32 virus. How can a Win32 file >>> run on her Mac? >> >> >> It can't, but that doesn't mean it can't *be* on a Mac. > > Her file TUD.EXE can't be deleted from the recycle bin of her Mac. I > thought the reason for not being able to delete the file is because > TUD.EXE is actually running. > > What other reasons should she look at? > > It would be nice to get something to delete the file, but it is said the > virus (on Windows) infects lots of other files. This means deleting it > may not solve the problem at all. > > What checks or tests should my friend do? Gavin, here is a help page from Apple. Basically, the first thing to do is check to see if the file is locked. You can see that from the Get Info. Move the file to the desktop, right click or control click and select Get Info. In the dialog box at the bottom it will show a lock - open is not locked, closed is locked. You should be able to click off the check box to unlock it. If this is the reason, then you should be able to empty the trash. Another option is to hold down the Option key while emptying the trash. Here is the link: http://support.apple.com/kb/HT1526 -- John Gentile Newsletter editor Rhode Island Apple Group
From: Mr. Strat on 25 Jan 2010 21:28 In article <hjkd7p$d7a$1(a)news.eternal-september.org>, FromTheRafters <erratic(a)nomail.afraid.org> wrote: > There is nothing standard about limiting the definition of virus just to > suit your argument. > > It is a virus for the Mac - and runs on OS-X The point is...OS X cannot become infected without "help." Can't say that about Windows.
From: Dustin Cook on 25 Jan 2010 22:41
"Mr. Strat" <rag(a)nospam.techline.com> wrote in news:250120101828125524%rag(a)nospam.techline.com: > In article <hjkd7p$d7a$1(a)news.eternal-september.org>, FromTheRafters > <erratic(a)nomail.afraid.org> wrote: > >> There is nothing standard about limiting the definition of virus just >> to suit your argument. >> >> It is a virus for the Mac - and runs on OS-X > > The point is...OS X cannot become infected without "help." Can't say > that about Windows. > Truth be told, Windows requires help as well. A virus doesn't magically execute itself. In almost ALL infection cases, the user can rightfully be blamed. -- "Is there anything in Guul Draz that doesn't suck the life out of you?" - Tarsa, Sea Gate sell-sword. |