unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Haider Mirza <x7and7@gmail.com>
To: Bengt Richter <bokr@bokr.com>, Maxime Devos <maximedevos@telenet.be>
Cc: 54941@debbugs.gnu.org
Subject: bug#54941: No such file or directory when running a binary
Date: Wed, 20 Apr 2022 20:46:04 +0100	[thread overview]
Message-ID: <87bkwvzgg3.fsf@smtp.gmail.com> (raw)
In-Reply-To: <20220416233249.GA2485@LionPure>

[-- Attachment #1: Type: text/plain, Size: 897 bytes --]

> (This is not to accuse you Haider, who I don't know, of probing Maxime
> -- but consider the seemingly casual example you are setting for noobs
> in suggesting running an unknown (to others) binary).

Sorry about that, usually Github Repositories ask for some way to
reproduce a bug so they can try and debug it. I had expected him to
have ran the binary in a VM. But like you said it might not be apparent
to the less experienced. 

> The con starts off as many that target individuals do
> nowadays: With a text message. In this case it's not a
> phishing attempt, it's an attempt to ascertain whether the
> person receiving the message is susceptible to further
> manipulation.

Looking back, that really did seem quite manipulative, worse with the
repository not even with a license. Thanks for spotting this out and
making me realize my mistake.

All the best,
Haider.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]

  reply	other threads:[~2022-04-20 20:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 15:34 bug#54941: No such file or directory when running a binary Haider Mirza
2022-04-16 13:25 ` Maxime Devos
2022-04-16 13:32 ` Maxime Devos
2022-04-16 23:32   ` Bengt Richter
2022-04-20 19:46     ` Haider Mirza [this message]
2022-04-23 14:47       ` Maxime Devos
2022-04-16 13:58 ` Haider Mirza
2022-04-16 14:16   ` Maxime Devos
2022-04-16 14:22 ` Haider Mirza

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bkwvzgg3.fsf@smtp.gmail.com \
    --to=x7and7@gmail.com \
    --cc=54941@debbugs.gnu.org \
    --cc=bokr@bokr.com \
    --cc=maximedevos@telenet.be \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).