On Sat, 29 Jun 2002, Richard Amerman wrote:
All logging should idealy be done off site using a syslog deamon.
Agreed.
The most important thing is not to have a breach and second to fix
weaknesses. In this situation flushing the memory IS the best
solution to insure this, though it is
From: Jeff Newmiller [mailto:[EMAIL PROTECTED]]
Sent: Sat 6/29/2002 11:37 PM
Absolutely disagree. Rebooting is a waste of time. If there is a way in,
rebooting does nothing to prevent repetition. If there is not, rebooting
Heylo, I've asked this before, but it still doesn't work.
I'm using the most basic configuration of dachstein 1680KB floppy, with
minimal changed. How and what should i change so that i can run an ftp
server on a machine with ip address: 192.168.1.200 with a port of 80. also
i need an
Hi
Jeff Newmiller wrote the following at 08:37 30.06.2002:
On Sat, 29 Jun 2002, Richard Amerman wrote:
All logging should idealy be done off site using a syslog deamon.
Agreed.
The most important thing is not to have a breach and second to fix
weaknesses. In this situation flushing the
Hi Mike,
I followed the threads on hardware-wp. The last
information I read was that you have to do some
SMD soldering to get the write protection feature.
I think that this is not well suited for many
people as you need some soldering experience to
do this.
The last information i got from
On Sun, 2002-06-30 at 05:07, Manfred Schuler wrote:
I followed the threads on hardware-wp. The last
information I read was that you have to do some
SMD soldering to get the write protection feature.
I think that this is not well suited for many
people as you need some soldering experience to
On Sun, 2002-06-30 at 03:50, Erich Titl wrote:
Agreed, but now we have to see how we can stop such a skillful attacker.
How can we protect the RAM disks from someone determined enough to upload
and execut code bytewise. Anyone can fingerprint the IP stack and scan our
system for loopholes.
On 30 Jun 2002, Mike Noyes wrote:
On Sun, 2002-06-30 at 05:07, Manfred Schuler wrote:
[...]
Also I am a little bit astonished as all people
on the list agree that any additional level of
protection is an improvement. But in the discussion
about software-wp people argument as if it
I am attempting to run a Dachstein image on a system
that will eventually not have a keyboard and monitor.
I'm actually having great fun with it this weekend,
but there is one thing I can't seem to resolve without
help.
Following the Howto's and FAQ's, I run into a problem
almost immediately.
Hi again everyone,
I'm wondering what is the function of partitioning harddisk
to become small 20 M msdos based, when my bering still read
the 6 M of /dev/root?
Filesystem 1k-blocks Used Available Use%
Mounted on
/dev/root 6144 606084 99% /
I can't
Bering just uses the hard disk as a booting source. The actual OS is run in
Ramdisk, meaning you share part of your system's memory as a virtual disk.
The 6MB refers to the size of your ramdisk. In syslinux.cfg after
initrd=initrd.lrp add syst_size=10M. 10M being 10MBytes is just what I
have
Stewart:
Heya. Unfortunately, you've chosen a difficult application
to start with: FTP is notoriously difficult to get working behind
a NAT'ing firewall. Here's a PDF which explains why:
ftp://ftp.echogent.com/docs/FTP_and_Firewalls.pdf
As you can see, active FTP requires more
I fail to see any benefit to using software write-protect when hardware
write protect is convenient, easy and fool proof.
Simply move the write protect tab into the protect position and its
done. The only way to unprotect it is to physically move the tab back
to the writable position. That
Hi Frank,
if you can live with the space constraint of a floppy disk
this is the perfect solution and you should use it.
But if for any reason you cannot use a floppy or any other
hardware protected medium, software write-protect is the
next to best solution.
[EMAIL PROTECTED] schrieb:
I
Jerry,
With the limited info available, my best guess would be that you do not
have a kernel with Serial Port support compiled in. Check the Dachstein ftp
site for a kernel with serial port support.
If this is not the problem please follow the guidelines for providing us
info
How about if you modify tinylogin to email [EMAIL PROTECTED]
everytime the box is logged into???
--
~Lynn Avants
aka Guitarlynn
guitarlynn at users.sourceforge.net
http://leaf.sourceforge.net
If linux isn't the answer, you've probably got the wrong question!
Thanks for the assistance Steve. I misunderstood the
directions, and thought that you could use the serial
module w/o compiling it in.
I did what you said, downloaded the normal kernal
which has serial support and that took care of my
problem.
Nice to be able to finish a weekend project while
I would love to use Snort but feared that it was too big. Is it reasonable?
An that thought has any one worked with alternitive floppy drives like 2MB drives or
LS?
Richard Amerman
-Original Message-
From: Mike Noyes [mailto:[EMAIL PROTECTED]]
Sent: Sun 6/30/2002 7:07 AM
To:
On Sun, 2002-06-30 at 20:37, Richard Amerman wrote:
I would love to use Snort but feared that it was too big. Is it reasonable?
Richard,
David packaged a version back in Dec. of last year.
snort.lrp 17-Dec-2001 06:48 176k
http://leaf-project.org/devel/ddouthitt/packages/snort.lrp
Hello, i'm considering installing a hard drive into my LRP box running
dachstein, however, is there a way to COMPLETELY switch the hard drive off
after LRP is loaded into the RAM? I haven't installed the hard drive yet
because i don't want the noise. Is there a way?
Thankyou,
20 matches
Mail list logo
