From: Prayank <prayank@tutanota.de>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Nuke *notify options from Bitcoin Core
Date: Sun, 2 Jan 2022 00:29:15 +0100 (CET) [thread overview]
Message-ID: <MsMyRuH--3-2@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
Hi Daniel,
Not sure which PRs are you talking about, maybe you missed these points based on your understanding:
Lot of fancy things won't work in windows shortcut target
It is more suspicious even if you try, compared to something wrapped in *notify options provided by bitcoin core
This will not provide me option to run a command based on events like received transaction in wallet
*notify options provide some options that every malware is looking for
There is enough time to research more about the issue and respond with something new or that helps in documentation.
--
Prayank
A3B1 E430 2298 178F
[-- Attachment #2: Type: text/html, Size: 1139 bytes --]
next reply other threads:[~2022-01-01 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 23:29 Prayank [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-01 21:03 [bitcoin-dev] Nuke *notify options from Bitcoin Core Prayank
2022-01-01 22:57 ` Daniel Edgecumbe
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MsMyRuH--3-2@tutanota.de \
--to=prayank@tutanota.de \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox