Bitcoin Forum
April 25, 2024, 01:15:33 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Bitcoin Forum > Bitcoin > Bitcoin Discussion > Important privacy issue on bitcoin (identity leak)
Pages: [1]
« previous topic next topic »
  Print  
Author Topic: Important privacy issue on bitcoin (identity leak)  (Read 1180 times)
EhVedadoOAnonimato (OP)
Hero Member
*****
Offline Offline

Activity: 630
Merit: 500



View Profile
November 23, 2011, 08:46:07 PM
 #1
See https://github.com/bitcoin/bitcoin/issues/659

(I'm opening this topic just to warn those which may be concerned. If this is not the appropriate board, mods don't hesitate to move it)
1714007733
Hero Member
*
Offline Offline

Posts: 1714007733

View Profile Personal Message (Offline)

Ignore
1714007733
1714007733
Reply with quote  #2
1714007733
Report to moderator
1714007733
Hero Member
*
Offline Offline

Posts: 1714007733

View Profile Personal Message (Offline)

Ignore
1714007733
1714007733
Reply with quote  #2
1714007733
Report to moderator
Whoever mines the block which ends up containing your transaction will get its fee.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714007733
Hero Member
*
Offline Offline

Posts: 1714007733

View Profile Personal Message (Offline)

Ignore
1714007733
1714007733
Reply with quote  #2
1714007733
Report to moderator
EhVedadoOAnonimato (OP)
Hero Member
*****
Offline Offline

Activity: 630
Merit: 500



View Profile
November 23, 2011, 10:34:39 PM
 #2
Does anyone know of an alternative client which does not suffer from any sort of identity leak?
Gavin Andresen
Legendary
*
Offline Offline

Activity: 1652
Merit: 2216


Chief Scientist


View Profile WWW
November 24, 2011, 03:24:00 AM
 #3
Try running with the -nolisten -noirc flags, see if that works around the problem (and please let me know if it does/doesn't).

I'm not sure any of the current core developers regularly use TOR; getting somebody who does to contribute patches and review code for regressions is a good idea.
How often do you get the chance to work on a potentially world-changing project?
EhVedadoOAnonimato (OP)
Hero Member
*****
Offline Offline

Activity: 630
Merit: 500



View Profile
November 24, 2011, 08:09:09 AM
 #4
Quote from: Gavin Andresen on November 24, 2011, 03:24:00 AM
Try running with the -nolisten -noirc flags, see if that works around the problem (and please let me know if it does/doesn't).

As soon as I can try that I'll tell you.

Quote from: Gavin Andresen on November 24, 2011, 03:24:00 AM
I'm not sure any of the current core developers regularly use TOR; getting somebody who does to contribute patches and review code for regressions is a good idea.

Not even Theymos? Sad

I can't possibly contribute with C++, it's way beyond my skills, sorry...
EhVedadoOAnonimato (OP)
Hero Member
*****
Offline Offline

Activity: 630
Merit: 500



View Profile
December 05, 2011, 10:42:06 PM
 #5
Just replicating what I said here, executing bitcoin with the -nolisten flag seems to be a valid workaround for this issue.
Pages: [1]
  Print  
Bitcoin Forum > Bitcoin > Bitcoin Discussion > Important privacy issue on bitcoin (identity leak)
 « previous topic next topic »
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!