|
Title: Important privacy issue on bitcoin (identity leak) Post by: EhVedadoOAnonimato on November 23, 2011, 08:46:07 PM 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) Title: Re: Important privacy issue on bitcoin (identity leak) Post by: EhVedadoOAnonimato on November 23, 2011, 10:34:39 PM Does anyone know of an alternative client which does not suffer from any sort of identity leak?
Title: Re: Important privacy issue on bitcoin (identity leak) Post by: 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).
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. Title: Re: Important privacy issue on bitcoin (identity leak) Post by: EhVedadoOAnonimato on November 24, 2011, 08:09:09 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. 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? :( I can't possibly contribute with C++, it's way beyond my skills, sorry... Title: Re: Important privacy issue on bitcoin (identity leak) Post by: EhVedadoOAnonimato on December 05, 2011, 10:42:06 PM Just replicating what I said here (https://github.com/bitcoin/bitcoin/issues/659#issuecomment-3024570), executing bitcoin with the -nolisten flag seems to be a valid workaround for this issue.
|