[Discuss] The Ceph storage system, the CephFS filesystem

2014-04-22 Thread Rich Braun
I've fiddled unsuccessfully with the Ceph storage system and the similarly-named (but separate codebase) CephFS cluster filesystem. What I was hoping for was a more broadly-supported/easier-to-install cluster technology than OCFS2, that will hopefully work better than GlusterFS. Before I give up

Re: [Discuss] Building a non-profit membership list?

2014-04-22 Thread Will Rico
Sounds like Eric's solution and https://civicrm.org/ (which I believe the FSF uses) would be good places to start investigating. Since Eric is offering assistance, that makes his software even more compelling. Will On Mon, Apr 21, 2014 at 10:56 AM, Eric Chadbourne wrote: > On 04/20/2014 05:33

Re: [Discuss] Good and Bad Crypto

2014-04-22 Thread Richard Pieri
Tom Metro wrote: Anyone who read this thread will recall that my comments were in the context of a certain class of errors. Here's what you wrote: That's a simplistic understanding of how crypto algorithms work. An algorithm might consist of multiple layered state machines, and triggering a f

Re: [Discuss] Good and Bad Crypto

2014-04-22 Thread Tom Metro
Richard Pieri wrote: > Google's methodology has not to my knowledge been publicized. Correct. >Tom Metro wrote: >> Source code analysis has the potential to find these, if the code is >> analyzed. Back-box testing will find them only if you are very lucky. > > This is laughably false. If it we

Re: [Discuss] Good and Bad Crypto

2014-04-22 Thread Mike Small
john saylor writes: > On 4/22/14, 14:37 , Edward Ned Harvey (blu) wrote: >> You're saying, that the only way anybody in the world can trust >> anything, is to literally download everything from source, *read* >> all the source, and compile it themselves. > > instead of just calling "bs" can you s

Re: [Discuss] Good and Bad Crypto

2014-04-22 Thread Edward Ned Harvey (blu)
> From: Derek Martin [mailto:inva...@pizzashack.org] > > On Tue, Apr 22, 2014 at 06:37:51PM +, Edward Ned Harvey (blu) wrote: > > Supposing a bad guy writes software, open source, and makes it > > available for download in source form as well as precompiled binary, > > where he's compiled some

Re: [Discuss] Good and Bad Crypto

2014-04-22 Thread Derek Martin
On Tue, Apr 22, 2014 at 06:37:51PM +, Edward Ned Harvey (blu) wrote: > Supposing a bad guy writes software, open source, and makes it > available for download in source form as well as precompiled binary, > where he's compiled some trojan into the binary. Yes, this can happen. And only if the

Re: [Discuss] Good and Bad Crypto

2014-04-22 Thread john saylor
On 4/22/14, 14:37 , Edward Ned Harvey (blu) wrote: > You're saying, that the only way anybody in the world can trust anything, is > to literally download everything from source, *read* all the source, and > compile it themselves. instead of just calling "bs" can you suggest some other means by w

Re: [Discuss] Good and Bad Crypto

2014-04-22 Thread Edward Ned Harvey (blu)
> From: discuss-bounces+blu=nedharvey@blu.org [mailto:discuss- > bounces+blu=nedharvey@blu.org] On Behalf Of Derek Martin > > If you can't inspect it, you can't trust it. Period. Supposing a bad guy writes software, open source, and makes it available for download in source form as well

Re: [Discuss] Good and Bad Crypto

2014-04-22 Thread Edward Ned Harvey (blu)
> From: discuss-bounces+blu=nedharvey@blu.org [mailto:discuss- > bounces+blu=nedharvey@blu.org] On Behalf Of Derek Martin > The first AES competition lasted 5 years, up to 2001. During that time, several openly published ciphers were compared and scrutinized openly, and made available

Re: [Discuss] Good and Bad Crypto

2014-04-22 Thread Edward Ned Harvey (blu)
> From: discuss-bounces+blu=nedharvey@blu.org [mailto:discuss- > bounces+blu=nedharvey@blu.org] On Behalf Of Derek Martin > > Anything involving security or encryption is rarely simply anything. Point? > Hogwash. The difference is interested, qualified parties can't > inspect the imple

Re: [Discuss] BTSync

2014-04-22 Thread Richard Pieri
Derek Martin wrote: On Mon, Apr 21, 2014 at 06:37:03PM -0400, Richard Pieri wrote: ... but what it does isn't sync. On Tue, Apr 22, 2014 at 09:49:15AM -0400, Richard Pieri wrote: I didn't say that it doesn't do sync. Must be a case of mass-halucination... No, just you taking a phrase out

Re: [Discuss] BTSync

2014-04-22 Thread Derek Martin
On Mon, Apr 21, 2014 at 06:37:03PM -0400, Richard Pieri wrote: > ... but what it does isn't sync. On Tue, Apr 22, 2014 at 09:49:15AM -0400, Richard Pieri wrote: > I didn't say that it doesn't do sync. Must be a case of mass-halucination... -- Derek D. Martinhttp://www.pizzashack.org/ GPG

Re: [Discuss] OpenBSD and LibreSSL

2014-04-22 Thread Gregory Boyce
I really preferred the OpenTLS name that someone had suggested on the OpenBSD mailing list. On Tue, Apr 22, 2014 at 11:37 AM, Stephen Ronan wrote: > "In the wake of Heartbleed, OpenBSD group is creating a simpler, cleaner > version of the dominant OpenSSL." > http://it.slashdot.org/story/14/04/22

Re: [Discuss] OpenBSD and LibreSSL

2014-04-22 Thread Mike Small
Stephen Ronan writes: > "In the wake of Heartbleed, OpenBSD group is creating a simpler, > cleaner version of the dominant OpenSSL." > http://it.slashdot.org/story/14/04/22/1240247/not-just-a-cleanup-any-more-libressl-project-announced Would that use the Spanish or the French pronunciation of li

[Discuss] OpenBSD and LibreSSL

2014-04-22 Thread Stephen Ronan
"In the wake of Heartbleed, OpenBSD group is creating a simpler, cleaner version of the dominant OpenSSL." http://it.slashdot.org/story/14/04/22/1240247/not-just-a-cleanup-any-more-libressl-project-announced ___ Discuss mailing list Discuss@blu.org htt

Re: [Discuss] Good and Bad Crypto

2014-04-22 Thread Derek Martin
On Tue, Apr 22, 2014 at 11:40:58AM +, Edward Ned Harvey (blu) wrote: > > From: discuss-bounces+blu=nedharvey@blu.org [mailto:discuss- > > bounces+blu=nedharvey@blu.org] On Behalf Of Tom Metro > > > > Being open source [...]. It's > > is merely a necessary precondition for determining t

Re: [Discuss] Good and Bad Crypto

2014-04-22 Thread Richard Pieri
Tom Metro wrote: Steve Gibson discusses the timeline of the Heartbleed discovery. Google researchers, presumably examining the code, found the problem several weeks prior, and submitted patches to OpenSSL and fixed their own servers. I choose not to make such assumptions. Google's methodology h

Re: [Discuss] BTSync

2014-04-22 Thread Richard Pieri
Greg Rundlett (freephile) wrote: Well, according to the author Joey Hess, git-annex and git-annex assistant do synchronization, sort of like an open source Dropbox... so "it doesn't do sync" is subjective. It also handles arbitrarily large I didn't say that it doesn't do sync. I said that Git

Re: [Discuss] Good and Bad Crypto

2014-04-22 Thread Edward Ned Harvey (blu)
> From: discuss-bounces+blu=nedharvey@blu.org [mailto:discuss- > bounces+blu=nedharvey@blu.org] On Behalf Of Tom Metro > > Being open source [...]. It's > is merely a necessary precondition for determining that crypto is > trustworthy. Sorry, but this statement is simply false. Tell me t