|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
Post mortem of a virus :)
Post 302257063 by sdsd on Tuesday 11th of November 2008 09:38:50 AM
11-11-2008
Hey, thanks a lot for the reply....could I get a confirmation about the Fedora part? One more thing....should I navigate into the root directory of the pen drive and then type mkfs.fat32 or can I do it from the root directory of the hard disk itself (I've got a feeling this is a stupid question, but I'm a unix newbie)
P.S: During this period of time, I took my pen-drive to a clean windows system, scanned it with Avast (and no virus was detected, probably coz I removed all the code from the exe file
and I formatted it in windows)
But a friend borrowed it and got it infected again....this time, there's a wcluf.pif file and an autorun.inf file in the pen drive. It doesn't look like a virus to me, but I'm gonna try removing the contents of these two files too (Bless this VI editor)
Meanwhile, I'm repeating the question for the third time...if anyone knows the answer, please reply: the virus files weren't getting deleted, probably coz it had root permissions or something. The ls -l command output which I posted above shows it. How can I delete those files?
P.S: During this period of time, I took my pen-drive to a clean windows system, scanned it with Avast (and no virus was detected, probably coz I removed all the code from the exe file
and I formatted it in windows)But a friend borrowed it and got it infected again....this time, there's a wcluf.pif file and an autorun.inf file in the pen drive. It doesn't look like a virus to me, but I'm gonna try removing the contents of these two files too
(Bless this VI editor)Meanwhile, I'm repeating the question for the third time...if anyone knows the answer, please reply: the virus files weren't getting deleted, probably coz it had root permissions or something. The ls -l command output which I posted above shows it. How can I delete those files?
|
|
9 More Discussions You Might Find Interesting
1. Cybersecurity
nice board, makes interesting reading! glad to know im not the only one to have problems!! :D :D
last week, our database started to crash (run on unix / solaris) for no apparant reason. the problem seems to be intermiant which lead us to believe it may be a hardware problem causing the... (2 Replies)
Discussion started by: mdma
2 Replies
2. UNIX for Dummies Questions & Answers
i tought you can;t get virus in unix ? i have some admins buddys that work in bsd all he time and they sayed you can;t get viurs in unix is that true? download.com is putting virux updates out for mac OS X ................ (7 Replies)
Discussion started by: amicrawler
7 Replies
3. UNIX for Dummies Questions & Answers
can linux get a virus on the boot sec from windows? becuse my buddys computer micro trend cmos virus keeps telling him that
there is a boot sec virus on my hdd is that possable or is the box
being dumb and looking at the linux boot as a virus? it was set up as a windows box not a linux... (4 Replies)
Discussion started by: amicrawler2000
4 Replies
4. UNIX for Dummies Questions & Answers
I am running Unix SCO and have discovered the worm virus. It is enabled through a BIOS connections, I am able to get around it using telnet, believe it or not.
- Can anyone recommend a virus scan software?
- Has anyone successfully used a virus scan software on unix without a problem?
... (2 Replies)
Discussion started by: ana_cr32
2 Replies
5. UNIX for Dummies Questions & Answers
why one normally hears tht virus has stuck windows and one does not hear that unix has been stuck by virus...wht make unix so powerfull tht virus does not stuck it. (9 Replies)
Discussion started by: taurian1234
9 Replies
6. Windows & DOS: Issues & Discussions
:confused: folder option is dissapiaring in tool menu
iam formatting c drive after removal of this virus
& also regedit is also not opening the messerge say's administrater disabled
with out formattiung how ican solve this problem i.e iwant to get folder options& regedit (2 Replies)
Discussion started by: seshumohan
2 Replies
7. UNIX Desktop Questions & Answers
How do i manage virus and melware in Unix ? (2 Replies)
Discussion started by: Suriano10
2 Replies
8. AIX
Hello All,
Critical AIX production box crashed/rebooted while our team is working on it and we need to generate a detailed report for that, below are few questions that need to be included in the report. (We are System Administration team and everyone in our team has root access via sudo as well... (3 Replies)
Discussion started by: lovesaikrishna
3 Replies
9. Windows & DOS: Issues & Discussions
Hi All,
My old laptop has Windows XP. I reinstalled only last month and installed AVG free anti-virus. It's like every month, I get some kind of spyware or virus issue. which anti-virus software you guys using?
Thanks. (8 Replies)
Discussion started by: samnyc
8 Replies
LEARN ABOUT V7
rp
RP(4) Kernel Interfaces Manual RP(4) NAME
rp - RP-11/RP03 moving-head disk DESCRIPTION
The files rp0 ... rp7 refer to sections of RP disk drive 0. The files rp8 ... rp15 refer to drive 1 etc. This allows a large disk to be broken up into more manageable pieces. The origin and size of the pseudo-disks on each drive are as follows: disk start length 0 0 81000 1 0 5000 2 5000 2000 3 7000 74000 4-7 unassigned Thus rp0 covers the whole drive, while rp1, rp2, rp3 can serve usefully as a root, swap, and mounted user file system respectively. The rp files access the disk via the system's normal buffering mechanism and may be read and written without regard to physical disk records. There is also a `raw' interface which provides for direct transmission between the disk and the user's read or write buffer. A single read or write call results in exactly one I/O operation and therefore raw I/O is considerably more efficient when many words are transmitted. The names of the raw RP files begin with rrp and end with a number which selects the same disk section as the corresponding rp file. In raw I/O the buffer must begin on a word boundary. FILES
/dev/rp?, /dev/rrp? SEE ALSO
hp(4) BUGS
In raw I/O read and write(2) truncate file offsets to 512-byte block boundaries, and write scribbles on the tail of incomplete blocks. Thus, in programs that are likely to access raw devices, read, write and lseek(2) should always deal in 512-byte multiples. RP(4)