News for hackers. Stuff that matters.
Re:Fury: 170x faster than JDK, blazing fast serialization by... by chaokunyang on Sunday October 08, 2023 @09:35AM (#37810327)
I see, totally agreed! If any objects can be serialized, the deserialization will introduce security issue. For example, `constructor/equals/hashCode` may contains malicious code, which introduce the deserialization risks.

Fury put much work on this to avoid the open dynamic deserialization risks.

But although `basic collections, enums, Strings, records, and classes that register specific serialization code` are the only objects should be allowed for serialization, and they are serialized by the construction protocal. There are so many applications has used the existing serialization protocol assumption, we have to keep compatible, otherwise most of existing application can't use fury.

There are no comments on this comment yet.