Re: What the Hell has happened to this group???

On Sun, 19 Apr 2009 08:01:19 -0700 (PDT), MooseFET <kensmith@xxxxxxxxx>
wrote:

On Apr 17, 8:15 pm, FatBytestard
<FatBytest...@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
On Fri, 17 Apr 2009 09:37:36 -0700 (PDT), orion.osi...@xxxxxxxxxx wrote:
On Apr 17, 3:09 am, MooseFET <kensm...@xxxxxxxxx> wrote:
On Apr 16, 2:45 pm, orion.osi...@xxxxxxxxxx wrote:

On Apr 16, 10:09 pm, Rich Grise <r...@xxxxxxxxxxx> wrote:

On Wed, 15 Apr 2009 12:22:31 -0700, John Larkin wrote:
On Wed, 15 Apr 2009 11:51:48 -0700 (PDT), orion.osi...@xxxxxxxxxx

And download the first file on the list. Burn it as an image to a
blank CD, and boot from it. You can check out THE most user friendly
and up to date Linux distro around for free, without installing it if
you so wish. Forget Windows, Forget Gates and forget M$.

I have no use for and no interest in operating systems for PCs. What
matters to me, as an engineer, is engineering applications.

As long as your 'Doze system isn't plugged directly into the internet,
I see no problem. If you _need_ internet connectivity for your Eng. apps,
then hire a Linux geek to put a proper firewall in your gateway box.

I use Linux for all my internet stuff, but when I need to use 'Doze,
(Windows 2000 Professional, FWIW), I disconnect.

Cheers!
Rich

You tell 'm, Rich! BTW, here's another important tip: never run Linux
as Root whilst connected to the internet. You'll likely as not end up
with a rootkit installed and never know about it...

I have run a Puppy linux CD as root for days and days without anything
getting in.

If you're running from a live CD you're not going to get anything,
anyway. It's read-only media and presumably doesn't mount your HDD!

 There is still a root environment to "attack", dip***.

Well I'll be gobsmacked! FatBytestard got something right.

Puppy Linux has a complete writable file system. The parts you write
remain in RAM but there really is a file system that can be written.


Not only that (of course it would have to be in RAM), but note how all
Live distros have the root password as an unknown, and one that can only
be changed locally, so they boot as root as a rule, as it were. When the
user changes that password, he can then go into the GUI as root if he so
desires and get things done in x. Not the safest way to do things, but
easier than sudo unless you want to go 'round editing rights files and
other less than monkey user proof labors.


The same vulnerability IS there, however, as ANY file volumes that
happen to be on the system, though not written to by the distro as a rule
at boot time, CAN be mounted, made read-write active, and have files
deleted on them or added to them, so the asswipe that was saying you
cannot be attacked in such a setting, is an utter idiot.
.