From: ratheesh k <ratheesh.ksz@gmail.com>
To: Tarmo Kuuse <tarmo.kuuse@mail.ee>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: Firewall in ecos
Date: Fri, 04 Dec 2009 09:40:00 -0000 [thread overview]
Message-ID: <cfeab66d0912040140i20a53bb7md1990dfa5fcf1c5c@mail.gmail.com> (raw)
In-Reply-To: <hfah5p$n15$1@ger.gmane.org>
I have seen Many cable modems and Gateways (Routers ) running on ecos
. There should be some other mechanism ???
Thanks,
Ratheesh
On Fri, Dec 4, 2009 at 1:57 PM, Tarmo Kuuse <tarmo.kuuse@mail.ee> wrote:
> ratheesh k wrote:
>>
>> I am a newbie in ecos . I read that there is no netfilter support
>> implemented in ecos .Then How is security working in ecos ??
>
> This is a very interesting question and I really hope for some authoritative
> answers.
>
> The Open/FreeBSD TCP/IP stacks in eCos are hopelessly out of date (i.e.
> vulnerable). It's highly unlikely that servers and clients for Internet
> services have been audited or tested with security in mind. Encryption is
> not supported, although there is some unofficial port of OpenSSL - does that
> even work? Etc.
>
> I assume eCos to be usable only in trusted networks where security is not
> needed. Connecting an eCos device to any public network is not a good idea,
> unless this system is so unimportant that remotely crashing or breaking it
> does not cause any harm.
>
> --
> Kind regards,
> Tarmo Kuuse
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-12-04 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 6:25 [ECOS] " ratheesh k
2009-12-04 8:28 ` [ECOS] " Tarmo Kuuse
2009-12-04 9:40 ` ratheesh k [this message]
2009-12-04 11:49 ` Ross Younger
2009-12-04 15:21 ` Daniel Néri
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=cfeab66d0912040140i20a53bb7md1990dfa5fcf1c5c@mail.gmail.com \
--to=ratheesh.ksz@gmail.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=tarmo.kuuse@mail.ee \
/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).