From: Red on
nospam wrote:
> In article <hhdkoh$afg$1(a)news.albasani.net>, Red <red(a)neckspam.com>
> wrote:
>
>> Running SL 10.6.2 and want to secure delete just a single file WITHOUT
>> using the Secure Empty Trash feature. Also, the file to be deleted in on
>> an encrypted disk image-- and I can't delete the entire disk image.
>
> why do you care if a file on an encrypted image is securely deleted or
> not? the bits on the disk are already encrypted.
>
> in any event, man srm should tell you what you need to know.



Hmmm, OK- but if I'm dragging it to the trash folder-- which I don't
think is encrypted-- so I'm wondering if it can be recovered from there?
From: nospam on
In article <hhe1p1$tsa$2(a)news.albasani.net>, Red <red(a)neckspam.com>
wrote:

> >> Running SL 10.6.2 and want to secure delete just a single file WITHOUT
> >> using the Secure Empty Trash feature
> >
> > Why don't you want to use that feature?
>
> 1. Might want some of the other files back.

so don't delete those.

> 2. Many files in trash take too long to secure delete,

why would that matter if you only securely delete the one file?
From: nospam on
In article <hhe26o$vcd$1(a)news.albasani.net>, Red <red(a)neckspam.com>
wrote:

> Hmmm, OK- but if I'm dragging it to the trash folder-- which I don't
> think is encrypted-- so I'm wondering if it can be recovered from there?

that's why there's a secure delete.
From: Jolly Roger on
In article <hhe26o$vcd$1(a)news.albasani.net>, Red <red(a)neckspam.com>
wrote:

> nospam wrote:
> > In article <hhdkoh$afg$1(a)news.albasani.net>, Red <red(a)neckspam.com>
> > wrote:
> >
> >> Running SL 10.6.2 and want to secure delete just a single file WITHOUT
> >> using the Secure Empty Trash feature. Also, the file to be deleted in on
> >> an encrypted disk image-- and I can't delete the entire disk image.
> >
> > why do you care if a file on an encrypted image is securely deleted or
> > not? the bits on the disk are already encrypted.
> >
> > in any event, man srm should tell you what you need to know.
>
> Hmmm, OK- but if I'm dragging it to the trash folder-- which I don't
> think is encrypted-- so I'm wondering if it can be recovered from there?

Every volume has it's own invisible .Trash folder in Mac OS X. So the
file doesn't actually need to leave the encrypted volume to be placed
into the trash. ; )

--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.

JR
From: David Empson on
Red <red(a)neckspam.com> wrote:

> nospam wrote:
> > In article <hhdkoh$afg$1(a)news.albasani.net>, Red <red(a)neckspam.com>
> > wrote:
> >
> >> Running SL 10.6.2 and want to secure delete just a single file WITHOUT
> >> using the Secure Empty Trash feature. Also, the file to be deleted in on
> >> an encrypted disk image-- and I can't delete the entire disk image.
> >
> > why do you care if a file on an encrypted image is securely deleted or
> > not? the bits on the disk are already encrypted.
> >
> > in any event, man srm should tell you what you need to know.
>
> Hmmm, OK- but if I'm dragging it to the trash folder-- which I don't
> think is encrypted-- so I'm wondering if it can be recovered from there?

Each volume has its own hidden trash folder (actually one for each user
ID). The Trash on the Dock is a combination of all the individual trash
folders (for your user) on all mounted volumes.

If you trash a file on a disk image, the file is moved to the trash
folder on that disk image.

If the disk image is encrypted, then the trash on that disk image is
also encrypted, which means the trashed file is still encrypted.

Doing a secure empty trash will provide a theoretical additional layer
of security, but if someone else cannot mount the disk image in the
first place then it is a moot point.

If they could mount the disk image (or if you left it mounted and the
computer was unattended), then the file was never secure anyway.

--
David Empson
dempson(a)actrix.gen.nz