Version: 2.1.0-2
Hi,
Niels Thykier wrote (23 Jun 2016 21:30:52 GMT) :
> intrigeri:
>> syscall numbers are architecture dependent, so: what architecture did
>> you experience this on?
> amd64.
Thanks. So, that would be the keyctl syscall:
intrigeri:
> Control: tag -1 + moreinfo
>
> Hi Niels,
>
> [...]
>
> syscall numbers are architecture dependent, so: what architecture did
> you experience this on?
>
amd64.
> [...]
> Once I have this info I'll ping upstream about it, so the
> corresponding syscall is allowed (if that's safe)
Control: tag -1 + moreinfo
Hi Niels,
Niels Thykier wrote (07 Oct 2015 15:14:28 GMT) :
> Running polularity-contest with torsocks gives a warning:
> """
> torsocks /etc/cron.daily/popularity-contest --crond
> [Oct 07 17:11:53] WARNING torsocks[5038]: [syscall] Unsupported syscall
> number 250.
Control: tag -1 + upstream
Hi David,
Niels Thykier wrote (07 Oct 2015 15:14:28 GMT) :
> Running polularity-contest with torsocks gives a warning:
> """
> torsocks /etc/cron.daily/popularity-contest --crond
> [Oct 07 17:11:53] WARNING torsocks[5038]: [syscall] Unsupported syscall
> number 250.
Package: torsocks
Version: 2.1.0-1
Severity: normal
Running polularity-contest with torsocks gives a warning:
"""
torsocks /etc/cron.daily/popularity-contest --crond
[Oct 07 17:11:53] WARNING torsocks[5038]: [syscall] Unsupported syscall number
250. Denying the call (in tsocks_syscall() at
5 matches
Mail list logo