owner 424909 ! thanks Hey, as the upstream author I don't see any problem. The server part running on the pc is written in python and licences GPLv2 - no problem there. The j2me part has to be build by me, as there is now free wtk out there. And even if there would be one - depending on the interest in lbrc I might get a certificate to sign the builds of lbrc, so a user can allow it's java sandbox to always allow bluetooth access (without the signature the user can only allow it for the run of lbrc). And this certificate can't be provided to debian. You/the maintainer can also split the client part into an non-free part (although I would consider my GPLv2ed client as free as in free-speech) and a free part - the have the server part Recommend the non-free part, as I understand a free packages can't Depend on a non-free package. The main argument Patrick mentioned were security considerations. These are not valid, as the server part can be modified without problems. The client part can only cause security problems on the phone. IF this would happen, it would be a serious flaw in the j2me implementation of the phone, as each java programm is contained inside a sandbox and can only access files+bluetooth when the user enables it to do so. So: Someone breaking in through lbrc into a phone would primarily expose a bug in the j2me engine. Greetings Matthias -- So long and thanks for all the fish!
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil