>> (p.1)
    Author Topic: Important privacy issue on bitcoin (identity leak)  (Read 1227 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)

  • 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: 2401


    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  
Page 1
Viewing Page: 1

IRLBTC™ © 2025 IRLBTC.com