Delivery-Date: Mon, 22 Sep 2014 14:56:48 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id A3A4E1E0C76;
	Mon, 22 Sep 2014 14:56:45 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 0BF142794A;
	Mon, 22 Sep 2014 18:56:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 0C1A326D77
 for <tor-talk@lists.torproject.org>; Mon, 22 Sep 2014 18:56:37 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id oHRXRFBfKBfK for <tor-talk@lists.torproject.org>;
 Mon, 22 Sep 2014 18:56:36 +0000 (UTC)
Received: from mail-vc0-x231.google.com (mail-vc0-x231.google.com
 [IPv6:2607:f8b0:400c:c03::231])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id DCFD726080
 for <tor-talk@lists.torproject.org>; Mon, 22 Sep 2014 18:56:36 +0000 (UTC)
Received: by mail-vc0-f177.google.com with SMTP id im17so4475049vcb.36
 for <tor-talk@lists.torproject.org>; Mon, 22 Sep 2014 11:56:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=6Uid+aOdhx7+SI/sUlrViO+GC8dOxK1hlXSyKwIk0Z8=;
 b=eYltKGrsQFecnMHxWBNzwczEJQJkm2m1EXOxrpc0N8DogbR+wsTEk3YiNfOQkLk5Vo
 v5DUI6XuZVEnSzu2i8TLho+QH4Xc86LBg+/u4k8Xefdzg7PWRZ+k4tpmN353byj2wl56
 49D81hGNa88U+LAgawrtiJ6M9In+YX8rzGd97WtKXm9inqgrPNiOEY1piDwUmcVwm5hE
 x+Ag5/HzSluGTmK6tny6i5TlQI6gVVBi7+la57wgI4n24sArNCCKxOiMGk1kOusxLvKb
 XStNkSUMMzkXR2v8qvYnEdG2uwvDuz/7yMTNdNNcAuU6b1z7RsWRICxkBBdQsh8+AkCF
 tczg==
MIME-Version: 1.0
X-Received: by 10.52.253.39 with SMTP id zx7mr17729629vdc.2.1411412194325;
 Mon, 22 Sep 2014 11:56:34 -0700 (PDT)
Received: by 10.221.64.74 with HTTP; Mon, 22 Sep 2014 11:56:34 -0700 (PDT)
In-Reply-To: <CAD2Ti280QCEBo7maHvt_NkZuf7yt_so8dY45smr5ecV1eGdmAA@mail.gmail.com>
References: <CAD2Ti2-BgskWH1LXfWVr89vGByu8b1k52VL84vrH3y4ZEWVnoA@mail.gmail.com>
 <CAD2Ti280QCEBo7maHvt_NkZuf7yt_so8dY45smr5ecV1eGdmAA@mail.gmail.com>
Date: Mon, 22 Sep 2014 14:56:34 -0400
Message-ID: <CAD2Ti28h4FUrO_MBAdp8Nn6EpDobRTrFd7DA4KEs0Hf-Cfs-0A@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] GoldBug SF projects [was: Bittorrent Bleep]
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On Mon, Sep 22, 2014 at 2:55 AM, grarpamp <grarpamp@gmail.com> wrote:
>> https://cpunks.org//pipermail/cypherpunks/2014-September/005507.html
>
> Reply in thread please.
>
>> the point was that I would not use bleep messenger from bittorrent, as
>> it is not open source.
>
> The point in this particular thread is... that since day one you
> and your project developers are ignoring real concerns being raised
> about your apparent cluster of projects.
>
>> Others like the one you did a research on might
>> be worth for further testings, either by the binaries
>
>> Why don' t you test the binaries?
>
>> 7) Ask a friend [...] to use the binaries: exchange keys,
>> and chat. Done. All is encrypted and you never need to exchange keys.
>
> Your repeated classic dodge... suggesting that people run blobs
> instead of answering the question.
>
> The 'research' was posted to throw up red flags about these projects
> for anyone searching so the can see and form their own opinion.
>
> The world does not need more closed source.
> And it does not need more non-reproducible binaries.
> ESPECIALLY from software projects claiming to protect users privacy
> through encryption, and further enticing the masses to run them by
> putting cute little doggies on the tin.
>
>> The source and the binaries might not be machting from hash,
>> because if you know source projects, the source might be corrected
>> on one or two files even when the binaries have been build.
>
> Fix your code then. Reproducible builds are a MUST for any
> security/privacy project like yours.
>
>> So better build the software from source and use your own binaries.
>> I would suggest to build the crypto core first, which is spot-on.
>
>> I cannot help you with compile firefloo messenger on linux or
>> windows, as I have not done this yet.
>
> I'm not going to waste time attempting to build stuff that apparently
> no one but you and or your devs have been able to build. And I'm
> not going to waste time disassembling the binaries either.
>
> Post your SHA-256 reproducible build instructions on the wiki's for
> your projects. Then ask for build confirmation/review from the
> community.
>
>
> Until you either ...
>
> A) Quit distributing binaries
>  or
> B) Tell people in a COMPILING doc included in the sources how to
> make binaries that SHA-256 match the ones you distribute
>
>
>  and then
>
> C) Answer why you claimed to be announced/partnered with EFF/CCC
> (which they have both denied [1]), why you are continuing to mimic
> the Tor homepage/TBB, why you're directly spamming people with
> invites, why you are dodging these and other questions, and generally
> appearing and acting very unusual for an opensource privacy suite
>
> ... no one is going to believe these projects are anything but
> untrustworthy snake oil.
>
> Help us help you.
>
> In my opinion at this time, these (your) projects have serious trust
> issues and I wouldn't recommend them until resolved.
>
> And while this list isn't perfect or comprehensive, those needing
> privacy solutions have other options to choose from here...
> https://www.prism-break.org/
>
>
> License issues...
> http://www.gossamer-threads.com/lists/gnupg/users/62118
>
> An example of a decent model announcement and request for review,
> that your seeming sockpuppet then replied to with a lure...
> https://lists.torproject.org/pipermail/tor-talk/2014-March/032498.html
>
> Old stuff... (RetroShare?)
> http://nabble.documentfoundation.org/Instant-Messenger-for-Libre-Office-serverle
> ss-and-open-source-td2595287.html
> http://comments.gmane.org/gmane.os.haiku.devel/18674
>
> Can anyone provide an overall interpretation in English of posts?
> http://moenchengladbach.hopto.org/k/buecher/cd0001/instit/org/Aktion_Grundrechte
> /AKV-mailarchiv-2009-201310/author.html
> http://moenchengladbach.hopto.org/k/buecher/cd0001/instit/org/Aktion_Grundrechte
> /AKV-mailarchiv-2009-201310/26906.html
>
>
> Ps: To date, none of the people potentially related to these projects
> that I previously CC'd seeking comment from have replied either.
>
> [1] Official Comments
> EFF:
> https://lists.torproject.org/pipermail/tor-talk/2013-July/029129.html
> CCC:
> Subject: [rt.ccc.de #40481] False press using EFF / CCC? goldbug.sf.net

Inserting to 'many cc' auto moderated list via self reply.
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

