Anthony Thyssen wrote:
> On Thu, 22 Apr 2010 08:42:59 + (UTC)
> user1 wrote:
>
> | O>
> | > i've just started using encfs-1.2.0 on debian-3.1 to store an
> | > sqlite-3.4.2 database used by a website. i quickly started getting some
> | > scary messages from sqlite3 about the database being
On Thu, 22 Apr 2010 08:42:59 + (UTC)
user1 wrote:
| O>
| > i've just started using encfs-1.2.0 on debian-3.1 to store an
| > sqlite-3.4.2 database used by a website. i quickly started getting some
| > scary messages from sqlite3 about the database being malformed or tables
| > not existing.
O>
> i've just started using encfs-1.2.0 on debian-3.1 to store an
> sqlite-3.4.2 database used by a website. i quickly started getting some
> scary messages from sqlite3 about the database being malformed or tables
> not existing.
> will then be upgraded to debian-5.0 which has encfs-1.4.2 in sta
Although I quite like encfs, if it isn't working in certain situations, then
I'd suggest using cfs. I've used cfs in the past (still do in some areas)
and it's worked pretty well.
http://www.crypto.com/software/
On Wed, Apr 21, 2010 at 9:59 PM, raf wrote:
> raf wrote:
>
> > hi,
> >
> > i've jus
raf wrote:
> hi,
>
> i've just started using encfs-1.2.0 on debian-3.1
> to store an sqlite-3.4.2 database used by a website.
> i quickly started getting some scary messages from
> sqlite3 about the database being malformed or tables
> not existing.
>
> these errors were not actually truthful. w
hi,
i've just started using encfs-1.2.0 on debian-3.1
to store an sqlite-3.4.2 database used by a website.
i quickly started getting some scary messages from
sqlite3 about the database being malformed or tables
not existing.
these errors were not actually truthful. when i look
at the database it'
