Patchwork: Can not use torsocks

[nicohansi]

At the moment it is not possible to use torsocks to torify patchwork.
It throws two warnings

1522081336 WARNING torsocks[18395]: [syscall] Unsupported syscall number 293. Denying the call (in tsocks_syscall() at syscall.c:488)
1522081336 WARNING torsocks[18395]: [syscall] Unsupported syscall number 292. Denying the call (in tsocks_syscall() at syscall.c:488)

This might have something to do with this issue. But I have no idea.

[phaer]

I don't use patchwork yet, but I imagine that SSB needs to listen for inbiund connections and torsocks denies such for anything but localhost only. If so, I guess it would need deeper integration with tor than torsocks is able to provide, such as an onion service.

[HostFat]

I also hope to see this also :)

It will give a safer place to people that are afraid of impact on their real life, as it is in some regimes.

[cryptix]

with sbot@12 and above you should be able to configure a unix-socket for client applications, which shouldn't be touched by tsocks. you need this in your connections.incomming list of .ssb/config:

"unix": [{ "scope":"device", "transform":"noauth" }],

an ssb-client then uses a remote like this: unix:/path/tomy/ssb/socket~noauth or this in patchbay).

but this is all pretty new, please test this more! not having net in connections.outging should stop sbot from using it and only having onion should have it use the socket on localhost:9050 to make connections.

[mmckegg]

@cryptix so is this possible now?

Does something need to be added to patchwork, or is it a documentation issue?

[cryptix]

so is this possible now?

I don't use tsocks myself so I can't verify or test this myself but I believe the pieces are all there.

Sadly we don't have any active windows devs to figure this out which made patchbay remove unix sock by default: https://github.com/ssbc/patchbay/pull/264

So yes, I'd rather document a workaround for this than change the default connection type.

[stale[bot]]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

[linas]

I couldn't figure out how to make https://github.com/ssbc/patchwork/issues/753#issuecomment-429852552 actually work.

[linas]

Oh hah. Pays to read the actual bug report. Unsupported syscall number 293 is being tracked in in gitlab, https://gitlab.torproject.org/tpo/core/torsocks/-/issues/30658 from which I quote:

$ egrep '^(293|332|292)' arch/x86/entry/syscalls/syscall_64.tbl
292     common  dup3                    __x64_sys_dup3
293     common  pipe2                   __x64_sys_pipe2
332     common  statx                   __x64_sys_statx

so I can't imagine switching to unix-domain socks will fix this; I think that electron is making these syscalls before patchwork or patchbay start up. Patchbay never gets to the splash screen. So this does not smell like a patchwork issue to me, it smells like a torsocks issue.