-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated test phase tutorial #48
base: main
Are you sure you want to change the base?
Conversation
|
||
```bash | ||
$> mkdir -p ~/.duress | ||
$> echo '#!/bin/sh | ||
echo "Hello World"' > ~/.duress/hello.sh | ||
echo "Hello World" > /home/user/test.txt' > ~/.duress/hello.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is purpose of this change? Instead of directly getting the "Hello World" echoed to the output, users would now need to read from the file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DusanLesan, this was in response to issue #47 which I'm still finding time to replicate and am hoping to get it done today. My commentary would be if the desired intent of changing the demo would be to put it in a file (which is honestly how I did it initially) then /tmp/test.txt
would be a better option to target.
If I can replicate the error then it's worth the change in the demo guide. Just need to see if some change in bookworm made the output to stdout inoperable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just tried it out now and am unable to replicate #47, so this is still unconfirmed as a needed change. Still going to hear out @m6n50u7 until the issue is resolved to their satisfaction or the tutorial is deemed satisfactory with obvious caveats that some installations may have configurations that necessitate departure from the tutorial to confirm functionality.
check my closed issue to know why.
…On September 7, 2024 6:29:01 PM GMT+01:00, Dusan Lesan ***@***.***> wrote:
@DusanLesan commented on this pull request.
>
```bash
$> mkdir -p ~/.duress
$> echo '#!/bin/sh
-echo "Hello World"' > ~/.duress/hello.sh
+echo "Hello World" > /home/user/test.txt' > ~/.duress/hello.sh
What is purpose of this change? Instead of directly getting the "Hello World" echoed to the output, users would now need to read from the file. Also it requires more steps now.
--
Reply to this email directly or view it on GitHub:
#48 (review)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
you already had issue related to this here
<#41>
…On September 7, 2024 6:29:01 PM GMT+01:00, Dusan Lesan ***@***.***> wrote:
@DusanLesan commented on this pull request.
>
```bash
$> mkdir -p ~/.duress
$> echo '#!/bin/sh
-echo "Hello World"' > ~/.duress/hello.sh
+echo "Hello World" > /home/user/test.txt' > ~/.duress/hello.sh
What is purpose of this change? Instead of directly getting the "Hello World" echoed to the output, users would now need to read from the file. Also it requires more steps now.
--
Reply to this email directly or view it on GitHub:
#48 (review)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
Not even with test steps in this change I have the script executed and everything looks the same but with more steps. But regardless of failed script execution on my system, what caught my eye was that:
|
@m6n50u7, can you confirm you're using stock Debian 12/bookworm? I was unable to replicate the issue and am still getting stdout: |
No description provided.