Hello,
when compiling the kernel 2.4.18-pre7, I get the following messages:
md5sum: MD5 check failed for 'isac.c'
md5sum: MD5 check failed for 'isdnl1.c'
md5sum: MD5 check failed for 'isdnl2.c'
md5sum: MD5 check failed for 'isdnl3.c'
md5sum: MD5 check failed for 'tei.c'
md5sum: MD5 check failed for 'callc.c'
md5sum: MD5 check failed for 'cert.c'
md5sum: MD5 check failed for 'l3dss1.c'
md5sum: MD5 check failed for 'l3_1tr6.c'
md5sum: MD5 check failed for 'elsa.c'
md5sum: MD5 check failed for 'diva.c'
md5sum: MD5 check failed for 'sedlbauer.c'
md5sum: MD5 check failed for 'hfc_pci.c'
md5sum: can't open hfc_pci.
cert.c: In function `certification_check':
cert.c:50: warning: control reaches end of non-void function
In file included from /usr/src/linux/include/net/checksum.h:33,
from /usr/src/linux/include/net/tcp.h:30,
from slhc.c:75:
What does this mean? Is the ISDN driver corrupt?
Everything works as usual, but this messages make me worry about security!
Is this a known problem? Could someone explain it to me?
kernel messages when loading the modules:
ISDN subsystem Rev: 1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1/none/1.1.4.1 loaded
HiSax: Linux Driver for passive ISDN cards
HiSax: Version 3.5 (module)
HiSax: Layer1 Revision 1.1.4.1
HiSax: Layer2 Revision 1.1.4.1
HiSax: TeiMgr Revision 1.1.4.1
HiSax: Layer3 Revision 1.1.4.1
HiSax: LinkLayer Revision 1.1.4.1
HiSax: Total 1 card defined
HiSax: Card 1 Protocol EDSS1 Id=HiSax (0)
HiSax: AVM PCI driver Rev. 1.1.4.1
PCI: Found IRQ 15 for device 00:0a.0
AVM PCI: stat 0x2020a
AVM PCI: Class A Rev 2
HiSax: AVM Fritz!PCI config irq:15 base:0xA000
AVM PCI: ISAC version (0): 2086/2186 V1.1
AVM Fritz PnP/PCI: IRQ 15 count 0
AVM Fritz PnP/PCI: IRQ 15 count 5
HiSax: DSS1 Rev. 1.1.4.1
HiSax: 2 channels added
HiSax: MAX_WAITING_CALLS added
isdn: Verbose-Level is 0
HiSax: debugging flags card 1 set to 4
ippp, open, slot: 0, minor: 0, state: 0000
ippp_ccp: allocated reset data structure cef8b800
Thanks,
Felix
ps. please CC me, I'm not subscribed to this list.
Felix Triebel wrote:
>Hello,
>
>when compiling the kernel 2.4.18-pre7, I get the following messages:
>
>md5sum: MD5 check failed for 'isac.c'
>md5sum: MD5 check failed for 'isdnl1.c'
>
Don't worry, its something stiupid about certification and stuff.
Everything should be fine...
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
On Fri, 1 Feb 2002, David Woodhouse wrote:
> +<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
The HiSax driver, when used in conjunction with certain hardware (see
Documentation/isdn/HiSax.cert), has ...
Your proposal looks good, IMO.
--Kai