From: "Cody" <churst35@verizon.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Printer/scanner suggestions.
Date: Fri, 05 Oct 2007 15:22:07 -0400 [thread overview]
Message-ID: <00c001c80785$05609680$7201a8c0@emachine> (raw)
In-Reply-To: <47067580.5090703@clearwire.net>
I use the Cannon LIDE35 flat bed scanner and works right out of the box with
xsane. didn't have to do a thing.
$80
----- Original Message -----
From: "Gaijin" <gaijin@clearwire.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Friday, October 05, 2007 1:33 PM
Subject: OT: Printer/scanner suggestions.
> "Doug Sutherland" <doug&proficio,ca> speculated:
>
> > It should not be possible for files to be inaccessible by root.
> > It is possible that you now have a rootkit installed.
>
> Yeah, definitely a root-kit with filenames like "input.history" and
> "catalog.events". chattr didn't work. I think most of the commands
> have been compromised. The little bastage didn't re-write the ls
> command very well, though. The files appear if you do an 'ls -a .*' to
> display just the dot-files. Then a few dot and non-dot-files
> appear...to normal and root users. It's a pretty neat hackk. I really
> only had sendmail and fetchmail semi-configured, and a bunch of
> symlinks to docs and HOWTO's. Oh, and commenting out half of
> rc.profile. <grins> I'm not losing very much.
>
> > > Don't leave ports open!
> > Don't run services that you don't need.
> > Create some detterants so they go somewhere else instead.
>
> Had all that, except for the deterants. The firewall's closed, and
> I'm only running sendmail. I have other services installed but
> disabled, as they're not even configured yet. I was planning on
> activating the whole shebang with a runlevel change. It's barely above
> runlevel 1 at present. It's really no big deal. Helps me learn the
> system.
> I was wondering though. Do you know if it's possible to require
> that both the executable and indestructible bits be set so a program
> can run? I was thinking of password protecting the chattr command, or
> re-writing it so that it could only be executed from localhost, and
> locking everything down. You'd have a catch-22 scenario, if you
> removed one of the bits from chattr, though. You couldn't change any
> binaries or libraries remotely without access to chattr, nor upload
> anything that can be made executable without chattr. <grins> I guess
> admins who need full remote access won't like it, though. Nor would
> anyone using a package manager, or needing to do any programming. I
> guess there would have to be some kind of security toggle that only a
> working chattr could disable.
> Myself, I'd prefer laughing my hairy butt off at some jerk trying
> to upload a virus or root-kit that he can't even run.
>
> Michael
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.488 / Virus Database: 269.14.1/1050 - Release Date: 10/4/2007
> 5:03 PM
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
OT: " Gaijin
` Cody [this message]
-- strict thread matches above, loose matches on Subject: below --
Gaijin
` Doug Sutherland
` Janina Sajka
` Gaijin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00c001c80785$05609680$7201a8c0@emachine' \
--to=churst35@verizon.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).