FYI, the rules aren't -j safe:
clean: clean-patched unpatch
The testsuite isn't run during build; that would definitely be welcome; I could run it with ./configure && make && cd tests && scripts/run_tests simple/*.sh here.
There's a new upstream available.
So overall, I don't mind too much if there's a commitment from the Ubuntu Server team to take care of it, but the fact that this is a custom C daemon running *as root* and processing its own packet types from the network do ring the alarm bells.
Is there any plan to limit traffic to the local network at least?
In any case, I think I'll have to ask Ubuntu Security to take a look here.
FYI, the rules aren't -j safe:
clean: clean-patched unpatch
The testsuite isn't run during build; that would definitely be welcome; I could run it with ./configure && make && cd tests && scripts/run_tests simple/*.sh here.
There's a new upstream available.
So overall, I don't mind too much if there's a commitment from the Ubuntu Server team to take care of it, but the fact that this is a custom C daemon running *as root* and processing its own packet types from the network do ring the alarm bells.
Is there any plan to limit traffic to the local network at least?
In any case, I think I'll have to ask Ubuntu Security to take a look here.