n0-computer / n0-computer/dumbpipe
How to use fixed secret key and ticket?
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 782
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
The steps not work:
root@test:~# dumbpipe generate-ticket
using secret key 26ca41a6396c29d7b5e8f1c2ecac98bbbaada75fbe0a9cd96698c6511fa40b96
endpointadgws7h4vleht6snigdgoqt6kxsjvukptuoxdstpgpd3mo7fo6vsgaa
export secretkey="26ca41a6396c29d7b5e8f1c2ecac98bbbaada75fbe0a9cd96698c6511fa40b96"
export ticket="endpointadgws7h4vleht6snigdgoqt6kxsjvukptuoxdstpgpd3mo7fo6vsgaa"
echo "test" | dumbpipe listen
dumbpipe connect
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the shown dumbpipe generate-ticket, listen, and connect commands with the exported secretkey and ticket, then inspect the CLI help or entry points for these commands. Done means the fixed secret key and ticket workflow either succeeds as described or the correct invocation and failure cause are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100