[LAD] jack1 unsafe with accidentally (?) internal exported functions

[Paul Davis]

Although their export is a mistake, I really don't see this as of any
particular importance.

JACK is almost always a per-user system. JACK also allows clients to
scribble all over each other ports. The fact that someone can write an
application which does this is really not much of an issue compared to that.

On Mon, Mar 16, 2015 at 1:10 PM, Tito Latini <tito.01beta at gmail.com> wrote:

> Hi, some internal functions are globals and I think it is not what you want
> (jack2 seems ok).
>
> For example, a naive way to forbid the creation of other jack clients is:
>
> # tested with jack 0.124.1
> gcc -ljack private_club_mode.c
> ./a.out      # prints "JACK compiled with System V SHM support."
> echo $?      # 0
> jack_lsp     # no more clients please, segfault (jack_client_open_aux)
>
>
> /* private_club_mode.c */
> #include <jack/jack.h>
>
> int jack_register_server(const char *, int);
>
> int main() {
>         return jack_register_server("umpa", 0xDADA);
> }
>
> Tito
> _______________________________________________
> Linux-audio-dev mailing list
> Linux-audio-dev at lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxaudio.org/pipermail/linux-audio-dev/attachments/20150316/14036ffb/attachment.html>