-
Is there an option to have unoserver bind to a unix domain socket instead of a network interface? Might not make much practical difference in terms of security or performance but my preference is to u…
-
crc and his components should not bind any ports.
It is a major security issue. Some security solutions deny it. Large corporation might be worried by that.
Current usage:
* Hyperkit and libvirt…
-
```
Reading about local IPC on Windows leads me to idea that Named Pipes is not the
transport should be used where Unix Domain sockets are on Unix. Other, most
probably faster, should be.
ALPC and U…
-
Named pipes is a great way to communicate on Windows, but provides issues when wanting to forward/reroute or even debug on Windows. Tools like Thunder/Postman do not support the use of Named Pipes.
-
Validate
- Unix domain socket
- Named pipes (only windows?)
Note for containers:
Containers need to share sock files via volumes
-
Split from https://github.com/mvdan/sh/issues/513, since this one can be reproduced by @theclapp on his Mac machine.
It doesn't seem to be the same issue that we're seeing with pseudo-TTYs on CI, w…
mvdan updated
2 years ago
-
For local, interprocess comms, that do not go outside the machine, it would be nice to have a named pipes transport that can be used. Named pipes is supported with .net standard 2.0, so it could be do…
-
TCP sockets on localhost run the risk that untrusted code running on the same machine (under a different user) could connect to the system. Windows named pipes or Unix domain sockets should be used i…
-
I keep getting the following error when the servers.yml for svr02 and svr03. Any way to fix this?
TASK [mssql : Add MSSQL admin] *******************************************************************…
-
```
Reading about local IPC on Windows leads me to idea that Named Pipes is not the
transport should be used where Unix Domain sockets are on Unix. Other, most
probably faster, should be.
ALPC and U…