rfc:secure_unserialize
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:secure_unserialize [2014/11/03 20:16] – stas | rfc:secure_unserialize [2014/11/17 00:55] – stas | ||
---|---|---|---|
Line 3: | Line 3: | ||
* Date: 2013-03-29 | * Date: 2013-03-29 | ||
* Author: Stas Malyshev, stas@php.net | * Author: Stas Malyshev, stas@php.net | ||
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
* Patch: https:// | * Patch: https:// | ||
+ | |||
===== Introduction ===== | ===== Introduction ===== | ||
Line 42: | Line 43: | ||
===== Proposed PHP Version(s) ===== | ===== Proposed PHP Version(s) ===== | ||
- | Proposed for inclusion into PHP 5.6.x or PHP 7 branches. | + | Proposed for inclusion into PHP 7 branch, and into |
===== Other issues ==== | ===== Other issues ==== | ||
* It is not planned that unserialize_callback_func function will be called on prohibited classes as it is done on non-existing classes. | * It is not planned that unserialize_callback_func function will be called on prohibited classes as it is done on non-existing classes. | ||
* This option is not available currently for sessions and any other functions that use unserialization without calling unserialize(). This may be added later if needed, but for sessions it is very unlikely that untrusted user data will be injected as serialized session data - in that case the problems with security are much larger as pretty much any session-based authentication will be immediately broken. | * This option is not available currently for sessions and any other functions that use unserialization without calling unserialize(). This may be added later if needed, but for sessions it is very unlikely that untrusted user data will be injected as serialized session data - in that case the problems with security are much larger as pretty much any session-based authentication will be immediately broken. | ||
+ | |||
+ | ===== Vote ===== | ||
+ | |||
+ | The vote is to accept the unserialize() filtering option as described in this RFC for inclusion into PHP, with options being Yes or No. 50%+1 majority is required for acceptance. | ||
+ | |||
+ | Vote started on 2014-11-03 and is open until 2014-11-10 23:59:59 PST. | ||
+ | |||
+ | <doodle title=" | ||
+ | * Yes | ||
+ | * No | ||
+ | </ | ||
+ | |||
===== References ===== | ===== References ===== |
rfc/secure_unserialize.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1