On 24 Jun 2017, at 2:29am, Ryan Whitworth wrote:
> GDB backtrace details and input files can be found here:
> https://github.com/rwhitworth/sqlite-fuzz/tree/master/2017-06-23-sqlite3.
For those interested, all the faults found seem to concern dot commands. Here
is an
Hello all,
I was using American Fuzzy Lop (afl-fuzz) to fuzz test stdin to the sqlite3
interactive shell. AFL found a few inputs that cause segmentation faults
(mostly due to failed assertions, I think?). Is this sort of thing worth
investigating further or a non-issue?
GDB backtrace details
I think you and I are on the same page here, Clemens? I abhor the BOM, but the
question is whether or not SQLite will cater to the fact that the bigger names
in the industry appear hell-bent on shoving it in users’ documents by default.
Given that ‘.import’ and ‘.mode csv’ are “user mode”
On 6/23/17, Thien, Christoph wrote:
>
> we are compiling and using the User Authentication extension (Windows,
> MSVC10 and MSVC14, x86 and amd64).
>
> Problem:
> In 3.19 branch one can access a database without authentication.
>
Bummer. Do you have a patch to fix
I'd recommend the system.data.sqite.dll wrapper
http://system.data.sqlite.org/index.html/doc/trunk/www/index.wiki
This is a .Net component which works very well with SQLite databases.There
are a plethora of downloads, which can seem daunting. Depending on your
.Net flavour you're working with (I
Mahmoud Al-Qudsi wrote:
> with `.import ……`, SQLite3 includes a BOM (UTF-8) as part of the first
> column of the first record.
The Unicode Standard 9.0 says in section 3.10:
| When represented in UTF-8, the byte order mark turns into the byte
| sequence . Its usage at the beginning of a UTF-8
Hi all,
we are compiling and using the User Authentication extension (Windows, MSVC10
and MSVC14, x86 and amd64).
Problem:
In 3.19 branch one can access a database without authentication.
Example:
When using sqlite 3.12 series (e.g. 3.12.2) everything works like expected.
One can do:
7 matches
Mail list logo