Welcome, Guest. Please login or register.

Author Topic: Security risks using data saves that include pointers ?  (Read 3236 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline JoseTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show all replies
Security risks using data saves that include pointers ?
« on: January 30, 2007, 06:07:24 PM »
Probably a stupid question as on the Amiga you don't have much concerns (or uses) for security, but in general is there any big security risk if I include a dump of the memory location some pointer points to? This is used to signal if the next batch of data in the file is the data the pointer points to or not (if the ptr is NULL).
The only risk I see is that someone could use that to get the a memory location on the program, but then again that location contains only data, stuff exploiting buffer overrunns probably doesn't need to know where the data is anyway, they just flood the buffer to see the results...
What's your opinions on this ?

:pint:
\\"We made Amiga, they {bleep}ed it up\\"
 

Offline JoseTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show all replies
Re: Security risks using data saves that include pointers ?
« Reply #1 on: January 30, 2007, 06:30:51 PM »
Edited 2 setences, one that was wron the other to make it more clear....
\\"We made Amiga, they {bleep}ed it up\\"
 

Offline JoseTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show all replies
Re: Security risks using data saves that include pointers ?
« Reply #2 on: January 31, 2007, 05:31:54 PM »
Hey 8-)
@Piru
More or less what I thought. I ended up not doing it though, as after trying it I discovered it would imply changes that wouldn't make the current algorithms I'm using faster.

@Karlos
Most of what you describe is more or less done  :-) Still need to finish some parts and test/correct bugs though..

"versus offset into the file"
That screws up alignment a bit and is a problem I still don't know ver well how to solve. If you compile it with a different compiler or with different settings that alter the alignment it will make the resulting file format different.

"..as opposed to structuring it for saving is surely just laziness."
Someone called me ? :-D I end up rewriting and tweeking stuff sooner or later though, honestly.

"Of course, if it's just a whole bunch of binary data, who would know which value in there was a pointer in the first place?"
Because the loader uses that same data block descriptions of the saver. So if it's loading a part of a block that's described as a pointer to something it needs to know if the pointer actually pointed to something or not. If it did it's non NULL (and hence I could just dump the pointer for speed), and the data it points to follows.
That the use:) But I ended up just put 1 or 0 values in there.
\\"We made Amiga, they {bleep}ed it up\\"
 

Offline JoseTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show all replies
Re: Security risks using data saves that include pointers ?
« Reply #3 on: January 31, 2007, 05:33:59 PM »
"That screws up alignment a bit and is a problem I still don't know ver well how to solve."

Without making the descriptions huge that is... They're mostly describing data blocks right now.
\\"We made Amiga, they {bleep}ed it up\\"