Named pipe stager error

[prol000]

Describe the bug There's an error when trying to setup a stager listener having a named pipe pivot. If I understand correctly, this should generate a payload which when executed will allow a beacon to communicate back to the sliver server via a named pipe. Given the RPC error retrieved, I'm having second thoughts. Please correct me if I'm wrong.

To Reproduce Steps to reproduce the behavior (ip addresses are redacted:

1. get a session over a beacon and run a named pipe pivot: pivots named-pipe --bind foobar --allow-all
2. get the ip address and create a new profile with a named pipe: profiles new beacon --wg REDACTED-SLIVER-SERVER-IP:443 --format shellcode --named-pipe REDACTED-BEACON-IP/pipe/foobar shellcode-wg-np
3. start a stage listener over tcp: stage-listener -u tcp://REDACTED-SLIVER-SERVER-IP:8081 -p shellcode-wg-np [*] No builds found for profile shellcode-wg-np, generating a new one [!] Error generating implant [!] rpc error: code = Unknown desc = exit status 1

Expected behavior Create a stage listener which serves a payload that can connect back to the sliver server via a named-pipe

Desktop (please complete the following information):

• OS: Kali Linux
• Version: [] Client v1.5.42 - 85b0e870d05ec47184958dbcb871ddee2eb9e3df - linux/amd64 Compiled at 2024-02-28 19:46:53 +0000 UTC Compiled with go version go1.20.7 linux/amd64 [] Server v1.5.42 - 85b0e870d05ec47184958dbcb871ddee2eb9e3df - linux/amd64 Compiled at 2024-02-28 19:46:53 +0000 UTC

[rkervella]

Can you check$HOME/.sliver/logs/sliver.log for a more verbose error message?