Comment 8 for bug 1006414

So we all agree that this is not directly exploitable in Swift current security model, but it would be a very welcome improvement to serialize to something less potentially harmful ?

If yes, I'd suggest we open this bug to the public as a welcome security strengthening issue (rather than keep it as an embargoed exploitable vulnerability).

Thomas/Sebastian: do you agree ?