netdev - Re: [PATCH 0/5] isdn: deprecate non-mISDN drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <D5B4825C-88DE-4011-8C2C-141214486861@holtmann.org>
Date:   Wed, 24 Apr 2019 16:30:49 +0200
From:   Marcel Holtmann <marcel@...tmann.org>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Greg KH <gregkh@...uxfoundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        "David S. Miller" <davem@...emloft.net>,
        Karsten Keil <isdn@...ux-pingi.de>,
        Networking <netdev@...r.kernel.org>,
        isdn4linux@...tserv.isdn4linux.de, Paul Bolle <pebolle@...cali.nl>,
        Holger Schurig <holgerschurig@...glemail.com>,
        Tilman Schmidt <tilman@...p.cc>,
        Al Viro <viro@...iv.linux.org.uk>,
        gigaset307x-common@...ts.sourceforge.net,
        Johan Hedberg <johan.hedberg@...il.com>,
        Bluez mailing list <linux-bluetooth@...r.kernel.org>
Subject: Re: [PATCH 0/5] isdn: deprecate non-mISDN drivers

Hi Arnd,

>>>>> When isdn4linux came up in the context of another patch series, I
>>>>> remembered that we had discussed removing it a while ago.
>> 
>> NAK.
>> 
>> I do not care about isdn4linux, but this is a purely CAPI based driver. So removing (or moving to staging)
>> CAPI support seems rather premature.
>> 
>> Maybe someone would have started talking to us before trying to move this into staging. It is a
>> maintained driver. That it is rather simple and hasn’t seen patches in a long time, doesn’t mean
>> it is not maintained and staging material. I see no reason to tell any user to enable staging tree
>> to get CMTP support.
> 
> I can definitely leave out the last patch from the series if we know
> that there are
> still users on CMTP. I searched around for a bit but could not find
> any indication
> what this is still used for, if anything.

I would prefer if we leave CAPI support and with that CMTP mainstream and not move that to staging. For isdn4linux, I have no objections to move that to staging since mISDN was suppose to replace it anyway.

> What I found were a couple of references of the driver no longer working
> about 10 years ago:
> 
> https://wiki.ubuntuusers.de/Archiv/Bluetooth/BlueFritz%21/
> https://www.opensuse-forum.de/thread/2776-erledigt-suse-11-2-und-bluefritz/
> 
> Is anyone using cmtp for voice or fax services? The use cases from before 2009
> that I could find were usually dial-up networking, but that seems pointless now
> if the only way to get an ISDN connection is to have it routed over
> the internet.

I still have the hardware and last time I checked it worked just fine. However you need to set up a proper pairing with the hardware. However that has nothing to do with CMTP since that is just a CAPI message transport protocol.

You can use it for voice and fax service as long as you have the right codecs in place. At the end of the day CAPI is an API for ISDN. And CMTP just being a transport, all ISDN services are possible given the right software / application.

Regards

Marcel