Re:Some Ways to avoid such things!
on
Linux Virus Alert
·
· Score: 1
All I was doing was posting some possible methods that could be used to defeat these viri for anyone interested, I never suggested that you or anyone else should actually use them, As for you personally it would give me great amusement if all your files are corrupted and data lost. If You actually use Linux, maybe nows a good time to move back to windows (its easier to catch viri there), or just get a clue(I am willing to provide one on a suitable clue by four). Or maybe you have some better (and easier) method of preventing the problems mentioned? and the point of this story
or are you just a lame troll? (o.k. maybe that rhetoric you did post as an A.C.) go troll elsewhere your not wanted here
1) Have a seperate binary directory for anything you don't trust ie/usr/local/bin2 that is writable by your user account ( and added to user path but obviously not root path!). If installing from a standard configure script pass --prefix=/usr/local/bin2 to the configure script.
If only a Makefile is has to be edited
2) Use either aide or tripwire to inspect changes to your file system (They keep snapshots of defined parts of the filesystem with various algorithms so any changes to binarys are noticed ie if/bin/ls was trojaned you would notice on next update of the aide database) see aide
3) use a chrooted environment for anything suspicious (not always very pratical though and inconvenient)
4) Reading through source and Makefiles might be considered but its not very realistic, though be suspicious of assembly code in source files (thankfully this virus is just a binary thing with the prominence of source)
I am sure the rest of the slashdot audience can think up many more methods but there's some I came up with.
I assume that how this could actually be applied, would be specifically to work out more about what function of the P53 protein actually prevents cancer and what function leads to the aging process and attempt to synthesise a protein only with the first function, (maybe different parts of the p51 protein bind to different active sites), To create a cancer prevention drug. Of course if you could do this you might also be able to use genetic engineering to prevent an organism from producing p53 and instead make it synthesise the subsititute protein and as such maybe live longer.
All thats lacking for linux printing is the knowledge of whats avaliable, check out
linuxprinting.org
As a summary if you use Redhat use printtool, suse have there own setup in yast, Mandrake probably have something too, for debian or most other distributions use aps though as with most setups you need ghostscript(for postscript conversion) and a printer spooler such as lpd or lprng. Never used it but CUPS is supposed to be easy to use and of course you could just buy a postscript printer. I don't see why this commercial program is needed, use whats out there and free as in beer and speech!
"Quick pass the L.A.R.T. I've found another one!"
2) Use either aide or tripwire to inspect changes to your file system (They keep snapshots of defined parts of the filesystem with various algorithms so any changes to binarys are noticed ie if /bin/ls was trojaned you would notice on next update of the aide database) see aide
3) use a chrooted environment for anything suspicious (not always very pratical though and inconvenient)
4) Reading through source and Makefiles might be considered but its not very realistic, though be suspicious of assembly code in source files (thankfully this virus is just a binary thing with the prominence of source)
I am sure the rest of the slashdot audience can think up many more methods but there's some I came up with.
I assume that how this could actually be applied, would be specifically to work out more about what function of the P53 protein actually prevents cancer and what function leads to the aging process and attempt to synthesise a protein only with the first function, (maybe different parts of the p51 protein bind to different active sites), To create a cancer prevention drug. Of course if you could do this you might also be able to use genetic engineering to prevent an organism from producing p53 and instead make it synthesise the subsititute protein and as such maybe live longer.
All thats lacking for linux printing is the knowledge of whats avaliable, check out linuxprinting.org As a summary if you use Redhat use printtool, suse have there own setup in yast, Mandrake probably have something too, for debian or most other distributions use aps though as with most setups you need ghostscript(for postscript conversion) and a printer spooler such as lpd or lprng. Never used it but CUPS is supposed to be easy to use and of course you could just buy a postscript printer. I don't see why this commercial program is needed, use whats out there and free as in beer and speech!