From: Bridget Barbacke <pannie@frontiernet.net>
Subject: catching up with svlpro
Date: Wed, 9 Dec 1998 05:20:43 -0500 [thread overview]
Message-ID: <199812091020.FAA279742@node21.frontiernet.net> (raw)
just dl'ed all the archive files from the blinux list and reviewed em for svlpro
concerns.
i noted one message in particular about a security problem with svlpro granting
root priviledges.
Since, i released svlpro mainly for testing purposes to start and it moved along
quickly , i tried to indicate that the root permissions were necessary to make
sure that the com port could be accessed without failure.
I am aware of such a possibility and wouldnt suggest using it if your worried
bout someone trying to attack your system while your using it.
There is a simple way to remedy this and i will be sure to get on it as soon as
i catch up with all thats lacking in my abscence.
for now, please let me know via email to:
pannie@frontiernet.net
of any problmes, solutions, and recommendations for svlpro before i get into
the down and dirty task of updating things.
regards, Brett Barback (pannie@frontiernet.net)
Author of svlpro (screenvoice for linux.
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199812091020.FAA279742@node21.frontiernet.net \
--to=pannie@frontiernet.net \
/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).