For an encryption scheme to suffer enigma machine type vulnerabilities, the
concept behind it must predate WWII.
IIRC the last straw (apart from known clear text like all messages ending with
the same greeting) the broke the enigma encoding was the fact that a radio
operator on an italian ship
Hi
I noticed that the recently added options
SQLITE_OMIT_WINDOWFUNC and
SQLITE_OMIT_UPSERT are not described at:
https://www.sqlite.org/compile.html.
I suppose that they should be described in that page.
Perhaps there are other SQLITE_OMIT_* options
missing in the page. I did not check all
>
> In the simple case, the VFS that the sqlite Db is mounted in is encrypted
> with a long key. The key has cycles at 4096(A) and 16(B1-Bn) bytes
> (4096/16 = 256 cycles of Bn); such that each sector is masked with
> A^B1(256x), A^B2(256x), ... all together there is no repetition because the
>
> On Oct 15, 2018, at 5:36 AM, Rowan Worth wrote:
>
> Anyway my point is I'm not seeing evidence to support the assertion that
> gmail treats messages to the list in general as spammish.
Ditto.
___
sqlite-users mailing list
> For the record, "delete the journal file" is terrible advice
Agreed. In normal production environment, I wouldn't suggest that. The
user was testing a database, and in my own developemtn cycle, its common
when developing for a database to be in all manners of chaos states. It
was purely a
On 2018/10/15 5:05 AM, Rowan Worth wrote:
On Sat, 13 Oct 2018 at 02:20, Lars Frederiksen wrote:
Any ideas?
Not sure if this got resolved off-list, but based on the code you've posted
I wonder if there is an "fdqGloser" as well as an "fdqGloser2", and if so
what state it is in.
Update:
6 matches
Mail list logo
