Re: Is memcpy secure?
From: Olga Sayenko (sayenko_at_yahoo.com)
Date: 01/11/04
- Next message: Alan P: "Re: Why is Win Explorer accessing the Net?"
- Previous message: Olga Sayenko: "Re: Is memcpy secure?"
- In reply to: Christian Bau: "Re: Is memcpy secure?"
- Next in thread: Richard Heathfield: "Re: Is memcpy secure?"
- Reply: Richard Heathfield: "Re: Is memcpy secure?"
- Reply: CBFalconer: "Re: Is memcpy secure?"
- Reply: Andras Tantos: "Re: Is memcpy secure?"
- Reply: Damian Menscher: "Re: Is memcpy secure?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 11 Jan 2004 13:02:16 -0800
Christian Bau <christian.bau@cbau.freeserve.co.uk> wrote in message news:<christian.bau-D18859.10293411012004@slb-newsm1.svr.pol.co.uk>...
> In article <50ab56cb.0401101820.40659138@posting.google.com>,
> sayenko@yahoo.com (Olga Sayenko) wrote:
>
> > Hi,
> >
> > I am trying to make sure that my data doesn't show up anywhere outside
> > my process unencrypted. I am concerned that if I use memcpy, the bytes
> > copied will end up in some memory somewhere after I am done with it.
> > Am I being paranoid?
>
> Yes, but are you paranoid enough?
Finally, someone understands! :)
>
> Seriously, memcpy will not be a special case. It won't do anything that
> straightforward C code couldn't do. I would be more worried about the
> data that was in a memory block that gets free()d.
Wouldn't setting buffers to null characters when I am done with them
take care of this?
- Next message: Alan P: "Re: Why is Win Explorer accessing the Net?"
- Previous message: Olga Sayenko: "Re: Is memcpy secure?"
- In reply to: Christian Bau: "Re: Is memcpy secure?"
- Next in thread: Richard Heathfield: "Re: Is memcpy secure?"
- Reply: Richard Heathfield: "Re: Is memcpy secure?"
- Reply: CBFalconer: "Re: Is memcpy secure?"
- Reply: Andras Tantos: "Re: Is memcpy secure?"
- Reply: Damian Menscher: "Re: Is memcpy secure?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
