# [RFC] Timing-Safe Encoding Functions

- Thread: https://externals.io/message/84705
- Original archive: https://news-web.php.net/php.internals/84705
- Started by Scott Arciszewski on 2015-03-13T18:22:30+00:00
- Messages: 2
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #84705 — Scott Arciszewski — 2015-03-13T18:22:30+00:00

URL: https://externals.io/message/84705#84705

https://wiki.php.net/rfc/timing_safe_encoding

---

## #84797 — Yasuo Ohgaki — 2015-03-15T02:17:00+00:00

URL: https://externals.io/message/84705#84797 · In reply to: #84705

Hi Scott,

On Sat, Mar 14, 2015 at 3:22 AM, Scott Arciszewski <scott@arciszewski.me>
wrote:

> https://wiki.php.net/rfc/timing_safe_encoding


Nice to see this RFC.
I haven't looked into patch yet, but no objections for the idea from me.

Only concern is existing timing safe function name. i.e. `hash_equals()`
http://php.net/manual/en/function.hash-equals.php

This function is better to named hash_equal_ts() if we are trying to have
consistent function names. (Old name should be alias, of course)

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net