Anthony, you describe BitMail - http://bitmail.sf.net not, BitMessage,
please dont mix it up! Regards Tom
On Sat, Jan 30, 2016 at 3:06 AM, Anthony Papillion
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 01/29/2016 07:05 AM, anonymous coward wrote:
> > Good day (again),
> >
>
Thanks Tom but I want even aware that Bitmail existed lol. I think these are
problems I've seen talked about around Bitmessage. For example, someone can
observe you connect to peers and know you're transmitting data through them.
But maybe not to whom or what your saying. Am I wrong? If I a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/30/2016 04:30 AM, Anthony Papillion wrote:
> Thanks Tom but I want even aware that Bitmail existed lol. I think
> these are problems I've seen talked about around Bitmessage. For
> example, someone can observe you connect to peers and know yo
Yes take care and look yourself or believe so called experts or
multiplicators. I agree that all closed source crypto is obsolete. Regards
Tom
Am 30.01.2016 11:47 schrieb "Jeremy Rand" :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 01/30/2016 04:30 AM, Anthony Papillion wrote:
> > Th
Have used Tor for years with no problems on Windows. Tried to download
Tor to a new RCA droid tablet and kept getting message "This is not Tor."
This was done before shutting off all apps designed by Google to line its
pockets. With everything turned off that could be turned off, it no
longer dow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30/01/2016 04:36, Niels Elgaard Larsen wrote:
> True, but making it official also makes it easier to enforce and to
> make every service provider cooperate.
>
> For Tor competent and systematically logging might worse that
> draconian measures by d
> Date: Saturday, January 30, 2016 20:50:22 +0100
> From: libertyinpe...@ruggedinbox.com
>
> Have used Tor for years with no problems on Windows. Tried to
> download Tor to a new RCA droid tablet and kept getting message
> "This is not Tor." This was done before shutting off all apps
> designed b
Niels Elgaard Larsen:
> * Session volume (number of bytes)
> 1. Tor would kill this right at the entry-node? Even a user fired up
> TorBrowser, typed in http://example.com/foo.mp4, watched the video and
> closed the brower, there would be enough negoitiation to obfuscate the
> bytecount?
>
I ass
aka:
> Niels Elgaard Larsen:
>> * Session volume (number of bytes)
>
>> 1. Tor would kill this right at the entry-node? Even a user fired up
>> TorBrowser, typed in http://example.com/foo.mp4, watched the video and
>> closed the brower, there would be enough negoitiation to obfuscate the
>> byte
