[sqlite] Lawyers, encryption, and RC4

AM To: General Discussion of SQLite Database Subject: Re: [sqlite] Lawyers, encryption, and RC4 On 8/11/15, Eric Hill wrote: > > We're getting some pushback from our lawyers suggesting that SQLite's > use of > RC4 even just to generate random numbers is, in their minds, >

[sqlite] Lawyers, encryption, and RC4

On 12 Aug 2015, at 2:45pm, Brian Willner wrote: > If you point out to your lawyers that SQLite is not doing anything that > Apple's OS X is doing, you may get some traction as well. Sorry to have to tell you that OS X /is/ registered for a US export licence, mostly for its incorporation of AES

[sqlite] Lawyers, encryption, and RC4

On 11 Aug 2015, at 3:00pm, Rob Willett wrote: > I recall that it used to be that 40 bit RC4 was OK and I *think* that the bit > length is now longer (128bit?) as it has been shown that 40 bit RC4 is as > much use as a chocolate fireguard. While it is allowable to export software incorporatin

[sqlite] Lawyers, encryption, and RC4

ng, you may get some traction as well. -Original Message- From: sqlite-users-boun...@mailinglists.sqlite.org [mailto:sqlite-users-bounces at mailinglists.sqlite.org] On Behalf Of Richard Hipp Sent: Tuesday, August 11, 2015 10:11 AM To: General Discussion of SQLite Database Subject: Re: [sqlite]

[sqlite] Lawyers, encryption, and RC4

Just speaking as a cantankerous old cynic, I wonder how much of this is being driven by a real concern and how much is being driven by someone with an agenda to use a "more favored" product. I've been pushed even further in the latter direction, in general, when I learned from a person who was eval

[sqlite] Lawyers, encryption, and RC4

Eric, The humorous side of me would argue that RC4 isn?t encryption anymore than ROT13 is these days. The serious side of me says that exportation of encryption stuff has changed significantly and is full of weird and vagueness. Since you don?t state your country of origin its difficult to kno

[sqlite] Lawyers, encryption, and RC4

On 11 Aug 2015, at 3:11pm, Richard Hipp wrote: > The RC4 encryption algorithm consists of three subcomponents: > > (1) Key management logic > (2) The pseudo-random number generator (PRNG) > (3) The encoder/decoder > > SQLite only implements (2). It omits (1) and (3). And hence, the RC4 > ker

[sqlite] Lawyers, encryption, and RC4

On 11 Aug 2015, at 1:30pm, Eric Hill wrote: > We're getting some pushback from our lawyers suggesting that SQLite's use of > RC4 even just to generate random numbers is, in their minds, encryption for > export purposes. Now, this makes absolutely no sense to me, I can assure > you, and I am

[sqlite] Lawyers, encryption, and RC4

I think answer 27 of the FAQ https://www.sqlite.org/faq.html#q27 might help you. > On 11 Aug 2015, at 13:30, Eric Hill wrote: > > Sorry to bother folks with this. > > We're getting some pushback from our lawyers suggesting that SQLite's use of > RC4 even

[sqlite] Lawyers, encryption, and RC4

Sorry to bother folks with this. We're getting some pushback from our lawyers suggesting that SQLite's use of RC4 even just to generate random numbers is, in their minds, encryption for export purposes. Now, this makes absolutely no sense to me, I can assure you, and I am not finding anything

[sqlite] Lawyers, encryption, and RC4

On 8/11/15, Eric Hill wrote: > > We're getting some pushback from our lawyers suggesting that SQLite's use of > RC4 even just to generate random numbers is, in their minds, encryption for > export purposes. No. The RC4 encryption algorithm consists of three subcomponents: (1) Key management log

[sqlite] Lawyers, encryption, and RC4

om: sqlite-users-boun...@mailinglists.sqlite.org [mailto:sqlite-users-bounces at mailinglists.sqlite.org] On Behalf Of Eric Hill Sent: Tuesday, August 11, 2015 8:31 AM To: General Discussion of SQLite Database Subject: [sqlite] Lawyers, encryption, and RC4 Sorry to bother folks with this. We'