public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Am i in danger?
Date: Mon, 22 Sep 2003 02:20:47 -0600	[thread overview]
Message-ID: <000401c380e2$6f680c80$6500a8c0@merlin> (raw)
In-Reply-To: <000501c380d2$d09ddd00$0100007f@carolina.rr.com>

Well, when ever you set up any kind of machine so that it accepts incoming
connecting you are taking risks that someone will gain unauthorized access.
As it stands the ftp server that shipps with your version of slackware does
not allow root access by default, but you may want to patch your ssh server
since there is currently an exploit that allows one to gain root access to
your box. As for sencitive data leaking out, I'd recommend either not
allowing any incoming connections or employing encryption on that data in
case someone gets a hold of it.
--
Joseph C. Lininger
jbahm@pcdesk.net
----- Original Message ----- 
From: "Chris" <chris@mailvision.ath.cx>
To: <speakup@braille.uwo.ca>
Sent: Monday, September 22, 2003 12:29 AM
Subject: Am i in danger?


> Well, I know that some servers on Slackware are started literally as soon
as
> installation is complete, like, sendmail being one of them...  I have set
a
> mount point as /win which points to my windows fat32 drive at which I can
> see the entire drive from there...  There is a hell of a lot of sinsitive
> info on that drive...  On my router, I do have port 21 ftp opoened, as
under
> Windows, I do run an ftp server, which I have very cautiously configured
so
> that well... 1... the whole world can't see my drive, and on top of that,
I
> basicly only allow access to my Adventures in Odyssey collection, as well
as
> my music collection which is now just over 4gb.  I guess to get to my
point
> of this mail:  Because of me having port 21 opened for windows,and because
> of the fact that right now root has access to every file and every
directory
> on /win which is on /dev/hda1 I'm wondering if that opens my hda drive for
> being jeopardized of someone hacking in through port 21 and seeing my
drive
> and even possibly retreiving inappropriate data for them to be seeing...
> now granted, my theory is that in order for that to happen, the user would
> have to have the modification set to 6 on the whole directory thus, giving
> them total access, but, here's the thing:  see:  like i said, the person
who
> helped me get everything up and going, forgot to put the mount point in my
> fstab file, so the only user right now that can even cd into /win
regardless
> is root and that's literally it...  So, I'm just wondering if that is
going
> to open a security hole, and if so, how can I improve my security and
> prevent a molicious attack, or even worse, spreading of nonpublic data.
>
> Thank you for your time, efforts, and help...
>
>
> Chris.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



  reply	other threads:[~ UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Chris
 ` Joseph C. Lininger [this message]
 ` Gregory Nowak

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='000401c380e2$6f680c80$6500a8c0@merlin' \
    --to=jbahm@pcdesk.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).