Bitcoin Forum
January 24, 2018, 11:55:32 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Important privacy issue on bitcoin (identity leak)  (Read 1110 times)
EhVedadoOAnonimato
Hero Member
*****
Offline Offline

Activity: 616



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)
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1516794932
Hero Member
*
Offline Offline

Posts: 1516794932

View Profile Personal Message (Offline)

Ignore
1516794932
Reply with quote  #2

1516794932
Report to moderator
1516794932
Hero Member
*
Offline Offline

Posts: 1516794932

View Profile Personal Message (Offline)

Ignore
1516794932
Reply with quote  #2

1516794932
Report to moderator
1516794932
Hero Member
*
Offline Offline

Posts: 1516794932

View Profile Personal Message (Offline)

Ignore
1516794932
Reply with quote  #2

1516794932
Report to moderator
EhVedadoOAnonimato
Hero Member
*****
Offline Offline

Activity: 616



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


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
Hero Member
*****
Offline Offline

Activity: 616



View Profile
November 24, 2011, 08:09:09 AM
 #4

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.

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
Hero Member
*****
Offline Offline

Activity: 616



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  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!