The Doctor [ARCHIVE] / is on Nostr

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2013-08-13 to 2014-03-24
💬 Posted a total of 4 messages
📚 Participated in the following categories: Bitcoin-development
🔇 Please do not DM this user as it's used for archive purposes only.

Last Notes

2023-06-07 15:16:02

- reply

📅 Original date posted:2014-03-24
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 03/23/2014 03:12 PM, Troy Benjegerdes wrote:
> I find it more likely that fake PGP keys are from corporate
> industrial espionage and/or organized crime outfits. Intelligence
> agencies will stick to compromised X509, network cards, and binary
> code blobs.
We're seeing the same thing happen to a couple of developers active in
the censorship circumvention problem space as well (though it's not
for the first time it's happened).
> Besides, why would an intelligence agency want your bitcoin when
> they can just intercept ASIC miners and make their own?
Perhaps they have other motives for attempting a cybil attack against
developers than trying to acquire Bitcoins. Say, by making it easier
to subtitute alternate versions which are instrumented to make the
users easier to spy upon and later take down?
- --
The Doctor [412/724/301/703] [ZS]
Developer, Project Byzantium: http://project-byzantium.org/
PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F DD89 3BD8 FF2B 807B 17C1
WWW: https://drwho.virtadpt.net/
"The enemies know the system. The allies do not." --Jay Jacobs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEAREKAAYFAlMwixgACgkQO9j/K4B7F8FQEACfQG8+5rYDuJd+6P50Bgc8RRfU
Q28AoNdyUbR2k05wTka30OcUUQNK5FcN
=IeMU
-----END PGP SIGNATURE-----

2023-06-07 15:16:02

- reply

2023-06-07 15:07:00

- reply

📅 Original date posted:2013-09-25
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/25/2013 07:35 AM, Melvin Carvalho wrote:
> It depends on the attacker. I think a large entity such as a govt
> or big to medium size corporation *may* be able to MITM https, of
> course the incentive to do so is probably not there ...
DLP (data loss prevention) products usually have MITM capability, to
make sure that proprietary information isn't being exfiltrated. Also,
some companies have full packet capture policies. The technology is
out there and people buy and use it. Whether or not they're going to
care about Bitcoin URIs in the short term, I don't know.
Some of the companies documented here have such products:
http://bluecabinet.info/wiki/Blue_cabinet#List_of_companies
You are correct in that the incentive to carry out MITM attacks in
this use case may not be there. However, detecting transactions may
be more useful to an attacker than meddling with them.
- --
The Doctor [412/724/301/703] [ZS]
Developer, Project Byzantium: http://project-byzantium.org/
PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F DD89 3BD8 FF2B 807B 17C1
WWW: https://drwho.virtadpt.net/
"Shiloh? Is your name Shiloh? Can I talk to you?"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlJDC30ACgkQO9j/K4B7F8FungCgyQtkyiQIekhlv1/Nqdd/JAIV
3EgAoKW8wTOI11lEq0ieOsRiQmnkM9w6
=W50W
-----END PGP SIGNATURE-----

2023-06-07 15:07:00

- reply

2023-06-07 15:05:53

- reply

📅 Original date posted:2013-08-14
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/13/2013 04:46 PM, Randolph D. wrote:
> you mixed up BitMail with BitMessage, this is different:
> http://bitmail.sf.net
Oops! My bad.
- --
The Doctor [412/724/301/703] [ZS]
Developer, Project Byzantium: http://project-byzantium.org/
PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F DD89 3BD8 FF2B 807B 17C1
WWW: https://drwho.virtadpt.net/
"This time we're using four times the Kevlar."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlILuDcACgkQO9j/K4B7F8HDBQCfR0F9SmCBCuFN1cAg/FExzicj
wfMAn0Fob9raimlp0/JQLi9y9hOyIwpG
=0vIZ
-----END PGP SIGNATURE-----

2023-06-07 15:05:52

- reply

📅 Original date posted:2013-08-13
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/09/2013 03:01 PM, Randolph D. wrote:
> anyone tested the secure encrypted p2p email:
> http://bitmail.sf.net
Not lately. It's pretty CPU and network intensive, which may or may
not be detrimental to your use case.
I keep meaning to read through these security analyses of Bitmessage
but I'm a little short on compute cycles at the moment:
https://bitmessage.org/forum/index.php?topic=1666.0
http://www.reddit.com/r/bitmessage/comments/1fwyx7/a_security_analysis_of_bitmessage/
- --
The Doctor [412/724/301/703] [ZS]
Developer, Project Byzantium: http://project-byzantium.org/
PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F DD89 3BD8 FF2B 807B 17C1
WWW: https://drwho.virtadpt.net/
If at first you don't succeed, call for an airstrike.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlIKk94ACgkQO9j/K4B7F8FMsgCgkuM56fI4hVT9H1ueZSFwl9Kk
qRoAoJkKZf4afKgVQKtDO6zRd/Auc/RV
=zwmX
-----END PGP SIGNATURE-----

2023-06-07 15:05:52

- reply