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  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]
Date: Fri Apr 14 03:50:27 2006
From: william at (William Lefkovics)
Subject: Recall: Oracle read-only user
	caninsert/update/delete data

It doesn't.  It's a client-side function.

-----Original Message-----
[] On Behalf Of Brian Eaton
Sent: Thursday, April 13, 2006 7:34 PM
Subject: Re: [Full-disclosure] Recall: Oracle read-only user
caninsert/update/delete data

On 4/13/06, Michael Holstein <> wrote:
> > In my experience, it doesn't even work in an Exchange environment. 
> > The user gets a message that the message should be recalled, but the 
> > original is still there, even if it hasn't been read yet. I've heard 
> > people say that at one time it would auto-delete the message if it 
> > hadn't been read, but I've never seen that.
> It does, provided you read the "recall" message first -- but since 
> Outlook (by default) displays in reverse chronological order, and most 
> people read email in the order received, it does little good.

Anybody understand how MS Exchange implements the "recall"
functionality?  I could see nothing in the e-mail headers that appeared to
prove the sender of the original message was the sender of the recall

- Brian

Full-Disclosure - We believe in it.
Hosted and sponsored by Secunia -

Powered by blists - more mailing lists