From: Charles Martin <joelisp@yahoo.com>
To: caml-list@inria.fr
Subject: [Caml-list] Does Marshal handle malicious data?
Date: Tue, 05 Mar 2002 14:56:25 -0800 [thread overview]
Message-ID: <5.1.0.14.0.20020305145423.0288b5b0@192.168.0.1> (raw)
Will the standard Marshal library correctly generate an exception for malicious data? Or is it possible that it will cause a core dump, read past end of string, etc?
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2002-03-05 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 22:56 Charles Martin [this message]
2002-03-06 3:28 ` Brian Rogoff
2002-03-06 10:59 ` Xavier Leroy
2002-03-06 14:10 ` Brian Rogoff
2002-03-07 8:59 ` Xavier Leroy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.1.0.14.0.20020305145423.0288b5b0@192.168.0.1 \
--to=joelisp@yahoo.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).