Why not just use the start-stop-daemon prog that comes with debian?
Using the --chuid and --chroot flags? I've used those to start MOHAA
servers with no issues? Anyone else know if this way is actually
secure?
thanks,
steve
On Mon, 2003-06-16 at 03:22, Mario Ohnewald wrote:
> Hello!
> I want
Why not just use the start-stop-daemon prog that comes with debian?
Using the --chuid and --chroot flags? I've used those to start MOHAA
servers with no issues? Anyone else know if this way is actually
secure?
thanks,
steve
On Mon, 2003-06-16 at 03:22, Mario Ohnewald wrote:
> Hello!
> I want
Also, there's Debian-curiosa.
And Ted, Your absolutely wrong, there are guidelings for this list and
for all the other debian lists.
You should go and read the follwing from the link below.
http://www.foldoc.org/foldoc/foldoc.cgi?query=spam
Which is linked directly from the Debian mailing list
Also, there's Debian-curiosa.
And Ted, Your absolutely wrong, there are guidelings for this list and
for all the other debian lists.
You should go and read the follwing from the link below.
http://www.foldoc.org/foldoc/foldoc.cgi?query=spam
Which is linked directly from the Debian mailing list
Since when did a bunch of Debian/Linux developers, maintainers, users
become Politicians? I must have missed that transitional period. If I
wanted to here this crap, I'd start watching the news!
--
0110001101100110110110110110 Steve Johnson: pubkeyID 0F737450
01100011011101101101100
Since when did a bunch of Debian/Linux developers, maintainers, users
become Politicians? I must have missed that transitional period. If I
wanted to here this crap, I'd start watching the news!
--
0110001101100110110110110110 Steve Johnson: pubkeyID 0F737450
01100011011101101101100
No, but I have noticed when i open an xterm, su to root and run
vi(vim-gtk), whenever I quit vi, i get this.
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Se
No, but I have noticed when i open an xterm, su to root and run
vi(vim-gtk), whenever I quit vi, i get this.
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Se
I just choose one good generic domain, ie: secure.mydomain.com, get that
signed, and put anything that's passing sensitive info(sign-ups, forms,
logins,etc) to that location. I've found it much better to send users
to another domain that has a signed cert. then to keep them in the
domain with an u
I just choose one good generic domain, ie: secure.mydomain.com, get that
signed, and put anything that's passing sensitive info(sign-ups, forms,
logins,etc) to that location. I've found it much better to send users
to another domain that has a signed cert. then to keep them in the
domain with an u
As far as I know there's not much to it, my dhcp server was very simple
to set up with very little security options. My only suggestion is just
make sure you have the latest version, and make sure you have the
security updates source in your sources.list file for your dists ie:
deb http://securit
As far as I know there's not much to it, my dhcp server was very simple
to set up with very little security options. My only suggestion is just
make sure you have the latest version, and make sure you have the
security updates source in your sources.list file for your dists ie:
deb http://securit
Hi,
I'm using wu-ftpd and set up /etc/wu-ftpd/ftpaccess to allow only one
user(using the deny-uid and allow-uid directives). I also added a
'restricted-uid myuser' flag. Everything is worknig fine, but I'm
confused. It's chrooting (or appears to) that user to it's home
directory just as I would
Hi,
I'm using wu-ftpd and set up /etc/wu-ftpd/ftpaccess to allow only one
user(using the deny-uid and allow-uid directives). I also added a
'restricted-uid myuser' flag. Everything is worknig fine, but I'm
confused. It's chrooting (or appears to) that user to it's home
directory just as I would
Hello,
i have an old cobalt cube on my network running a cutom 2.0.34 kernel,
that i'm finding is going to be really hard to upgrade, it's not running
debian, but everything else in here is :) so i'm only asking here
because i've read the docs and tried everywhere else for help.
anyway,
it has ip
Hello,
i have an old cobalt cube on my network running a cutom 2.0.34 kernel,
that i'm finding is going to be really hard to upgrade, it's not running
debian, but everything else in here is :) so i'm only asking here
because i've read the docs and tried everywhere else for help.
anyway,
it has i
anyone know of any good howtos on setting up a "log capture" box though
a serial cable or other means from a server?
anyone know of any good howtos on setting up a "log capture" box though
a serial cable or other means from a server?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> #include
>
> void example()
> {
> char a[10];
> char b[10];
> strcpy(a, "123456789");
> printf ("a: %s\n", a);
> b[20]='X';
> b[21]='Y';
> b[22]='Z';
> printf("a: %s\n", a);
> return;
> }
> main()
> {
> example();
> }
Ralf,
i ran this code
very interesting results, how? i woul
this may seem trivial but i've never really understood how a buffer
overflow happens and effects your system, i have some knowledge of
programming, but not much at low levels. like dealing direct with
memory or devices(other than using standard pointers and reading and
writing to devices thruough
> #include
>
> void example()
> {
> char a[10];
> char b[10];
> strcpy(a, "123456789");
> printf ("a: %s\n", a);
> b[20]='X';
> b[21]='Y';
> b[22]='Z';
> printf("a: %s\n", a);
> return;
> }
> main()
> {
> example();
> }
Ralf,
i ran this code
very interesting results, how? i wou
this may seem trivial but i've never really understood how a buffer
overflow happens and effects your system, i have some knowledge of
programming, but not much at low levels. like dealing direct with
memory or devices(other than using standard pointers and reading and
writing to devices thruoug
22 matches
Mail list logo
