On Saturday 25 September 2004 12:26 am, Geoff Nordli wrote:
> [EMAIL PROTECTED] wrote:
> > On Friday 24 September 2004 06:34 pm, Geoff Nordli wrote:
> >> My understanding is if you have specific domains that you would like
> >> resolved then you have to populate the /etc/dnscache/root/servers/
> >>
[EMAIL PROTECTED] wrote:
> On Friday 24 September 2004 06:34 pm, Geoff Nordli wrote:
>> My understanding is if you have specific domains that you would like
>> resolved then you have to populate the /etc/dnscache/root/servers/
>> directory with the name of domains and the servers that are able to
>
On Friday 24 September 2004 05:59 pm, Tom Eastep wrote:
> In my 35 years in this business, I've come to learn that all
> System/Programming projects are easy in the opinion of people who are
> not responsible for delivering them.
You've done a mind boggling job with Shorewall and Seawall
througho
On Friday 24 September 2004 06:34 pm, Geoff Nordli wrote:
> My understanding is if you have specific domains that you would like
> resolved then you have to populate the /etc/dnscache/root/servers/
> directory with the name of domains and the servers that are able to resolve
> those domains. Tinyd
[EMAIL PROTECTED] wrote:
> Geoff,
> Ok, I got into my router to figure this out.
> You are attempting to configure these options in the wrong place.
> Dnscache is configured out of the "/etc/dnscache/env/" directory.
> If you use the "lrcfg" menu, select 3. for packages, then "dnscache".
> The firs
Geoff,
Ok, I got into my router to figure this out.
You are attempting to configure these options in the wrong place.
Dnscache is configured out of the "/etc/dnscache/env/" directory.
If you use the "lrcfg" menu, select 3. for packages, then "dnscache".
The first two option are likely to be the one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lynn Avants wrote:
| On Thursday 23 September 2004 04:47 am, James Neave wrote:
|
|>You know, I was just thinking that while I was reading this.
|>A configuration wizard for windows would be very handy. Something to
|>automate initial configuration and
On Fri, Sep 24, 2004 at 09:38:57AM -0700, Geoff Nordli wrote:
> >
> >> Just to add some more information. I created an additional file in
> >> the same folder that somehow was successfully backed up, but I have
> >> no clue where it is kept. I tried doing a tarball listing of the
> >> etc, root,
Hi Geoff,
Just tried on my Bering U 2.2 with
/var/lib/lrpkg> more dnscache.exclude.list
etc/dnscache/log/supervise
etc/dnscache/supervise
etc/dnscache/root/ip/*
/var/lib/lrpkg> more dnscache.list
usr/bin/dnscache
etc/dnscache
etc/init.d/dnscache
var/lib/lrpkg/dnscache.*
etc/dnscache/root/servers
[EMAIL PROTECTED] wrote:
> On Thursday 23 September 2004 11:23 pm, Geoff Nordli wrote:
>
>> Just to add some more information. I created an additional file in
>> the same folder that somehow was successfully backed up, but I have
>> no clue where it is kept. I tried doing a tarball listing of th
On Thu, 2004-09-23 at 02:47, James Neave wrote:
> You know, I was just thinking that while I was reading this.
> A configuration wizard for windows would be very handy. Something to
> automate initial configuration and even updating, puts the correct LRPs
> on, adds your network card modules to the
On Friday 24 September 2004 09:11 am, B. wrote:
[...]
> Now the question: Is this
> dialogue crypted?
I doubt it, check with the developers to ez-ipupdate to get
the answer to this question. To be honest, any publically
available webserver is a major point of compromise that
is not necessarily pr
On Thursday 23 September 2004 04:47 am, James Neave wrote:
> You know, I was just thinking that while I was reading this.
> A configuration wizard for windows would be very handy. Something to
> automate initial configuration and even updating, puts the correct LRPs
> on, adds your network card mod
On Thursday 23 September 2004 11:23 pm, Geoff Nordli wrote:
> Just to add some more information. I created an additional file in the
> same folder that somehow was successfully backed up, but I have no clue
> where it is kept. I tried doing a tarball listing of the etc, root,
> dnscache, tinydns
Hej all,
this is a true challenge:
We built up a server/router environment for a good friend and configured
apache on the server being connected through the Bering-Box working with
dyndns. We use ezipupdate for actualizing the name service.
Now our friend found a 'hacker' who tries to attack our
> >Any ideas how to make installation/configuration easier?
>
> Firewall users are not so likely to be Linux users. Most Linux
distros
> come with installable/installed firewalls, and workstations can be
made
> fairly secure in themselves. A LEAF installation tool should either
run
> with whateve
Christian
At 09:33 23.09.2004 +0200, Christian HOSTELET wrote:
>Hello the list,
>
>Coming back on this topic after some feedback from KP
>
>A simpler approach regarding Tools is to keep 'dropbear.lrp'
>instead of loading 'sshd.lrp' and 'sftp.lrp' on the Bering box.
>This is a lighter solution
17 matches
Mail list logo
