From: oford <oford@ev1.net>
To: "James Miller (office)" <jamtat@mailsnare.net>
Cc: linux-newbie <linux-newbie@vger.kernel.org>
Subject: Re: Freesco, old kernel lines, security
Date: 03 Jun 2003 03:54:02 -0500 [thread overview]
Message-ID: <1054630442.4746.13.camel@spider.hotmonkeyporn.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0306020858070.6480@vector>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
On Mon, 2003-06-02 at 09:08, James Miller (office) wrote:
> I understand that in the world of Linux network security, generally older
> = worser (more insecure). So, I see that Freesco, a small Linux
> gateway/router distro that seems to be actively maintained, is using a
> kernel from the 2.0.x line - 2.0.38 (I understand that the most
> recent 2.0.x kernel is 2.0.39). Is Freesco considered an insecure
> gateway/router distro because it uses this older kernel line, or can it be
> expected to provide adequate network security? What would be the risks
> involved in using such a distro? Would the security savants on this list
> recommend against using it?
>
> Thanks, James
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
I like routerlinux. And it appears to still be actively maintained.
http://www.routerlinux.com/
--
Owen Ford <oford@ev1.net>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-06-03 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 14:08 Freesco, old kernel lines, security James Miller (office)
2003-06-02 15:07 ` Ray Olszewski
2003-06-03 7:25 ` james niland
2003-06-03 8:54 ` oford [this message]
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=1054630442.4746.13.camel@spider.hotmonkeyporn.com \
--to=oford@ev1.net \
--cc=jamtat@mailsnare.net \
--cc=linux-newbie@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.