Re: Preventing Denial of Service Attack In IPC Serialization
On Jun 28, 7:27 am, c...@mailvault.com wrote:
On Jun 25, 1:24 pm, Le Chaud Lapin <jaibudu...@gmail.com> wrote:
Naturally, it is optimal in many cases that an object be
serialized from an archive by construction only, not by assign-after-
construct. Some objects have heavy-weight default-construction, and
if one uses this scheme to deserialize say, a 1-million-element
list<Heavyweight_Class_With_Massive_Constructor>, the performance
penalty will be interesting indeed.
I've thought about this some also and like the term
stream constructor here. Recently I've thought that
if a derived object is being received and an error
occurs late in the process, it makes sense to attempt
to salvage what you can.
class B {...};
class I : public B {...};
class D : public I {...};
B* b = new D(stream_identifier_here);
If D's constructor releases an exception, the
standard says the sub-objects should be destructed.
Since that is how things have been set up over the
years, it can't easily be changed, but it might be
helpful if there was a way to indicate to the
compiler that a constructor is a stream constructor
and then instead of giving up, it could return an I.
The main reason I think this way is the sender,
network and receiver have put in a lot of work to
get to where it fails.
Hmm...yes, a lot of work, but don't you think it might be better to
just let the entire object go? After all, there is intuitive merit in
keeping with the spirit of automatic unwinding when full construction
failed. Also, the partially-received object will not have affected
the state at the sender in any way, so no harm would be lost.
Finally, the context in which the serialization occurs is
indeterminate when the serialization code is written. What happens
the partial object, I, is accepted? Then what? I think it would be a
bit like buying an automobile might or might not come with the wheels
and windshield, and you must agree to purchase such an automobile
before you know whether it will be complete.
Might be better to have all or nothing.
-Le Chaud Lapin-
--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]