* Adam Fields:
> I find it hard to believe that even the most uninformed dissidents
> would be using an untested, unaudited, _beta_, __foreign__ new service
> for anything. Is there any reason to believe otherwise?
I wouldn't be surprised if there are plenty such tools in circulation
which are us
* Adam Fields schrieb am 2010-09-15 um 20:48 Uhr:
> I find it hard to believe that even the most uninformed dissidents
> would be using an untested, unaudited, _beta_, __foreign__ new service
> for anything. Is there any reason to believe otherwise? My first guess
According to my experience the qu
On Sep 15, 2010, at 11:48 AM, Adam Fields wrote:
> I find it hard to believe that even the most uninformed dissidents
> would be using an untested, unaudited, _beta_, __foreign__ new service
> for anything. Is there any reason to believe otherwise? My first guess
> would have been that it was a g
On 09/15/2010 11:48 AM, Adam Fields wrote:
> On Wed, Sep 15, 2010 at 03:16:34AM -0700, Jacob Appelbaum wrote:
> [...]
>> What Steve has written is mostly true - though I was not working alone,
>> we did it in an afternoon. It took quite a bit of effort to get Haystack
>> to take this seriously. Eve
On Wed, Sep 15, 2010 at 03:16:34AM -0700, Jacob Appelbaum wrote:
[...]
> What Steve has written is mostly true - though I was not working alone,
> we did it in an afternoon. It took quite a bit of effort to get Haystack
> to take this seriously. Eventually, there was an internal mutiny because
> of
On Sep 15, 2010, at 6:16 AM, Jacob Appelbaum wrote:
> An interesting unintended consequence of the original media storm is
> that no one in the media enjoys being played; it seems that now most of
> the original players are lining up to ask hard questions. It may be too
> little and too late, fran
On 09/14/2010 09:57 AM, Steve Weis wrote:
> There have been significant developments around Haystack since the
> last message on this thread. Jacob Applebaum obtained a copy and found
> serious vulnerabilities that could put its users at risk. He convinced
> Haystack to immediately suspend operatio
Obliged, Steve. My & Simon Phipps' write-up is at ComputerWeekly:
http://blogs.computerworlduk.com/simon-says/2010/09/burning-haystack/index.htm
- a
On 14 Sep 2010, at 17:57, Steve Weis wrote:
> There have been significant developments around Haystack since the
> last messag
There have been significant developments around Haystack since the
last message on this thread. Jacob Applebaum obtained a copy and found
serious vulnerabilities that could put its users at risk. He convinced
Haystack to immediately suspend operations. The developer of Haystack,
Daniel Colascione,
Flamewar seems to have broken out:
http://neteffect.foreignpolicy.com/posts/2010/09/02/hay_what
I've had issues[1] with some of Morozov's previous writing[2] but if EM is
reporting accurately how Haystack is deployed - let alone used - then even
laying aside Kerckhoffs' principle / the
From another list.
Begin forwarded message:
From: Austin Heap
Date: August 23, 2010 8:27:43 PM EDT
To: liberationt...@lists.stanford.edu
Subject: [liberationtech] Haystack Q&A
Hi All,
I understand some of you have concerns/comments regarding our
project.
It would be great if a list could be
11 matches
Mail list logo
