This resulted in an error when dehydrated attempted to write to $WELLKNOWN/$TOKEN_FILENAME on the local machine because it doesn't skip doing so when using a hook script. I could work around that by setting $WELLKNOWN to some directory that exists on the local machine, but that seems hackish.
If it helps, the code that needs to be disabled is...
This is using dehydrated e3ef43c816f73d443f32410862d9253d35cf3f99 (master as of 2023-01-16.)
I ended up going with other tools, so I submit this issue only so that it may be useful to someone putting work into dehydrated. If it is not, it may be closed without costing me anything.
Originally created by @sethwklein on GitHub (Mar 29, 2023).
There is a workflow that involves using a hook script to copy the http-01 challenge file to another machine via ssh.
I attempted to use this by adding the following to `hook.sh`:
```sh
printf '%s' "$TOKEN_VALUE" \
| ssh remote.example.com \
"cat > $WELLKNOWN/$TOKEN_FILENAME"
```
This resulted in an error when dehydrated attempted to write to `$WELLKNOWN/$TOKEN_FILENAME` on the local machine because it doesn't skip doing so when using a hook script. I could work around that by setting `$WELLKNOWN` to some directory that exists on the local machine, but that seems hackish.
If it helps, the code that needs to be disabled is...
```
printf '%s' "${keyauth}" > "${WELLKNOWN}/${challenge_tokens[${idx}]}"
chmod a+r "${WELLKNOWN}/${challenge_tokens[${idx}]}"
```
This is using dehydrated `e3ef43c816f73d443f32410862d9253d35cf3f99` (`master` as of 2023-01-16.)
I ended up going with other tools, so I submit this issue only so that it may be useful to someone putting work into dehydrated. If it is not, it may be closed without costing me anything.
@RinkAttendant6 commented on GitHub (Jun 9, 2023):
I ran into this issue as well (my hook script makes API call to deploy and clean challenge, rather than ssh) and it seems to be the same (or similar) as #314.
I could work around that by setting $WELLKNOWN to some directory that exists on the local machine, but that seems hackish.
I suppose it's a little hackish but you can just point it to /tmp or something.
@RinkAttendant6 commented on GitHub (Jun 9, 2023):
I ran into this issue as well (my hook script makes API call to deploy and clean challenge, rather than ssh) and it seems to be the same (or similar) as #314.
> I could work around that by setting $WELLKNOWN to some directory that exists on the local machine, but that seems hackish.
I suppose it's a little hackish but you can just point it to `/tmp` or something.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @sethwklein on GitHub (Mar 29, 2023).
There is a workflow that involves using a hook script to copy the http-01 challenge file to another machine via ssh.
I attempted to use this by adding the following to
hook.sh:This resulted in an error when dehydrated attempted to write to
$WELLKNOWN/$TOKEN_FILENAMEon the local machine because it doesn't skip doing so when using a hook script. I could work around that by setting$WELLKNOWNto some directory that exists on the local machine, but that seems hackish.If it helps, the code that needs to be disabled is...
This is using dehydrated
e3ef43c816f73d443f32410862d9253d35cf3f99(masteras of 2023-01-16.)I ended up going with other tools, so I submit this issue only so that it may be useful to someone putting work into dehydrated. If it is not, it may be closed without costing me anything.
@RinkAttendant6 commented on GitHub (Jun 9, 2023):
I ran into this issue as well (my hook script makes API call to deploy and clean challenge, rather than ssh) and it seems to be the same (or similar) as #314.
I suppose it's a little hackish but you can just point it to
/tmpor something.