HiddenService not set up in torrc file because of sed expression error
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- shell
- Domain
- devops, infrastructure
Research direction
Start with Scripts/LinodeStandUp.sh around lines 214-225 and reproduce the sed command against /etc/tor/torrc, checking /standup.err for the reported expression error. Update the HiddenServiceDir entry so the setup completes and the HiddenService lines are added to torrc without the sed error.
Written by the indexing model from the issue text.
Description
I tried installing the standup script following your directions. I noticed that the HiddenService lines were not added to my /etc/tor/torrc. Then, I saw this error in /standup.err:
standup@localhost:~$ grep ^sed /standup.err
sed: -e expression #1, char 253: unknown option to `s'
I was able to reproduce the error by running the code https://github.com/BlockchainCommons/Bitcoin-Standup-Scripts/blob/master/Scripts/LinodeStandUp.sh#L214-L225:
standup@localhost:~$ sed -i -e 's/## address y:z./## address y:z.\
\
HiddenServiceDir \/var\/lib\/tor\/standup\/\
HiddenServiceVersion 3\
HiddenServicePort 18332 127.0.0.1:18332\
HiddenServicePort 18443 127.0.0.1:18443\
HiddenServicePort 8332 127.0.0.1:8332\
\
HiddenServiceDir \/var/\lib/\tor/\cypherpunkpay\
HiddenServiceVersion 3\
HiddenServicePort 8081 127.0.0.1:8081\
/g' /etc/tor/torrc
sed: -e expression #1, char 253: unknown option to `s'
I think the problem is this line that doesn't properly escape the directory forward slashes. It needs changed to:
HiddenServiceDir \/var\/lib\/tor\/cypherpunkpay\
- Dominant language
- Shell
- Stars
- 57
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from BlockchainCommons/Bitcoin-Standup-Scripts
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
BlockchainCommons/Bitcoin-Standup-Scripts#33 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
BlockchainCommons/Bitcoin-Standup-Scripts#32 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
BlockchainCommons/Bitcoin-Standup-Scripts#24 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
All issues in BlockchainCommons/Bitcoin-Standup-Scripts
Similar issues
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·
-
area: compat bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
zenhub-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenLiberty/ci.docker#747 ·