From: David Woodhouse <dwmw2@infradead.org>
To: Felix Triebel <ernte23@gmx.de>, rgooch@atnf.csiro.au
Cc: linux-isdn@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ISDN security ???
Date: Fri, 01 Feb 2002 10:15:56 +0000 [thread overview]
Message-ID: <4278.1012558556@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.42.0202011012590.804-100000@mob.wid>
In-Reply-To: <Pine.LNX.4.42.0202011012590.804-100000@mob.wid>
Can anyone clarify the last paragraph?
--- index.html.orig Fri Feb 1 09:51:46 2002
+++ index.html Fri Feb 1 10:11:43 2002
@@ -1073,6 +1073,10 @@
<A HREF="#s8-9">Why do I get unresolved symbols with __bad_ in the name?</A>
</LI>
+<LI>
+<A HREF="#s8-10">Why do I get warnings about md5sum checks failing in the ISDN code?</A>
+</LI>
+
</OL>
<H4>
@@ -5182,6 +5186,34 @@
</LI>
</UL>
+</LI>
+
+<LI>
+<A NAME="s8-10"></A><B>Why do I get warnings about md5sum checks failing in the ISDN code?</B>
+<UL>
+
+<LI>
+<FONT COLOR="#0000FF">(DW)</FONT> These are harmless, and you can
+probably ignore them.
+<BR>
+In many countries, any equipment which is connected to the public
+telephone networks must be tested and approved to ensure it behaves
+correctly. This requirement also extends to the software used to
+implement the ISDN protocols with passive ISDN cards.
+<BR>
+The HiSax driver has passed these tests and been approved, but any
+modifications to the source mean that the approval process must be
+repeated. The md5sum checks are therefore present to indicate the
+current approval status of the HiSax driver. An md5sum failure does
+not mean that your kernel download is corrupted; merely that someone
+has changed the source code since the last time it was certified and
+the md5sums of the approved files updated.
+<BR>
+It's rumoured that the requirement for certification of ISDN software
+is being relaxed in many countries, so this approval process is
+unnecessary. You should check for yourself the status of such rules in
+your country. Certainly, I've never heard of anyone actually getting
+prosecuted or otherwise reprimanded for using a modified Linux ISDN stack.
</LI>
</OL>
--
dwmw2
next prev parent reply other threads:[~2002-02-01 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 9:16 ISDN security ??? Felix Triebel
2002-02-01 9:44 ` Martin Dalecki
2002-02-01 10:15 ` David Woodhouse [this message]
2002-02-01 21:02 ` Kai Germaschewski
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=4278.1012558556@redhat.com \
--to=dwmw2@infradead.org \
--cc=ernte23@gmx.de \
--cc=linux-isdn@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@atnf.csiro.au \
/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.