> > > tested it).
> > > >
> > > > Of course if you are paying proper attention to security you should
> > > already
> > > > be onto the SQL injection vectors that put ATTACH in user's hands
> > anyway
> > > :)
> > > >
> &
ying proper attention to security you should
> > already
> > > be onto the SQL injection vectors that put ATTACH in user's hands
> anyway
> > :)
> > >
> > > -Rowan
> > >
> > > On 16 November 2016 at 07:10, jungle Boogie <jungleboog...@gmail.com&g
r's hands anyway
> :)
> >
> > -Rowan
> >
> > On 16 November 2016 at 07:10, jungle Boogie <jungleboog...@gmail.com>
> > wrote:
> >
> > > Hi All,
> > >
> > > Pretty interesting article:
> > > https://www.invincealabs.com/bl
already
> be onto the SQL injection vectors that put ATTACH in user's hands anyway :)
>
> -Rowan
>
> On 16 November 2016 at 07:10, jungle Boogie <jungleboog...@gmail.com>
> wrote:
>
> > Hi All,
> >
> > Pretty interesting article:
> > https://www.invi
in user's hands anyway :)
-Rowan
On 16 November 2016 at 07:10, jungle Boogie <jungleboog...@gmail.com> wrote:
> Hi All,
>
> Pretty interesting article:
> https://www.invincealabs.com/blog/2016/11/sqlite-shell-script/
>
> This post documents how we were able to create a SQ
Hi All,
Pretty interesting article:
https://www.invincealabs.com/blog/2016/11/sqlite-shell-script/
This post documents how we were able to create a SQLite database that
can be executed as an ash shell script purely from SQL queries.
Found here:
https://www.reddit.com/r/netsec/comments/5cwb07
Hello everyone,
I couldn't find this in the existing bug list so I decided to send this
email.
I downloaded the latest SQLite autoconf version from
https://www.sqlite.org/2016/sqlite-autoconf-3140200.tar.gz and tried
building it using this compile option, doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/11/2010 10:28 PM, Kirk Clemons wrote:
> I would like to be able to tell SQLite that if line 2 is bad just skip to
> line 3 and so on until the database has been parsed all the through
> maximizing the amount of data I retain.
It would require
I am trying to alter the dump function of the command line shell. I am not
completely familiar with C Programming so I am sort of in the dark here.
As I understand it's workings now the .dump command performs a 'select *' on
each row in row id order. If it encounters an error it skips to the end
The MSYS "start" command just circumvents the problem by starting a new clunky
Windows cmd window.
The Cygwin, Emacs and remote users logging into a Windows box via telnet/ssh
who prefer to work in
their native terminal program either have to hack the sqlite3 shell.c code to
force an
to stdout
>> (until close() anyway).
>> If you blindly type in the sqlite commands - it does work. Once you exit the
>> shell via .q you can
>> see the entire output of the session.
>>
>> One workaround is to use a cygwin-compiled sqlite3.exe. Perhaps hacking the
>
n the sqlite commands - it does work. Once you exit the
> shell via .q you can
> see the entire output of the session.
>
> One workaround is to use a cygwin-compiled sqlite3.exe. Perhaps hacking the
> sqlite shell not to
> buffer its console output would also do the trick.
>
I ente
see the entire output of the session.
One workaround is to use a cygwin-compiled sqlite3.exe. Perhaps hacking the
sqlite shell not to
buffer its console output would also do the trick.
--- rahed <[EMAIL PROTECTED]> wrote:
> I can run sqlite3 from a windows cmd but running it from m
I can run sqlite3 from a windows cmd but running it from msys shell or
emacs shell doesn't work. No sqlite prompt and I have to interrupt the
process with Ctrl c.
Does anyone know the cause?
Thank you.
--
Radek
14 matches
Mail list logo
