full-disclosure - Re: File system recursion and symlinks: A never-ending story (and how to bring it to an end for me)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BANLkTikAfeEttP1Rgot=V4yuyLGkX2mv0A@mail.gmail.com>
Date: Mon, 30 May 2011 18:16:09 -0700
From: coderman <coderman@...il.com>
To: Andrew Farmer <andfarm@...il.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: File system recursion and symlinks: A
 never-ending story (and how to bring it to an end for me)

On Mon, May 30, 2011 at 5:09 PM, Andrew Farmer <andfarm@...il.com> wrote:
> ....
> LVM snapshots have some nasty gotchas, though:
>
> https://bugs.launchpad.net/lvm2/+bug/360237

there are also corner cases depending on filesystem used on top of the
logical volumes, there is often no fail-safe behavior when you fuck up
sizing or lose backing devices, you need to handle application level
sync yourself (like locking DB tables and letting buffers flush to
disk), etc.

did you expect training wheels?

> They also don't solve the problem of restoring a fragment of data (e.g, a single accidentally deleted file) from a backup in an untrustworthy environment.

are you a volume shadow copy user? ;)

the poor man's way to handle this is mounting the RO snapshot
somewhere, and invoking and rsync, afick, $your_favorite_tool to see
what changed and copy/restore what you want.

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/