[tor-bugs] #7419 [Tor]: Choose a faster memwipe implementation

[Tor Bug Tracker & Wiki]

#7419: Choose a faster memwipe implementation
-----------------------------+------------------------------------
     Reporter:  nickm        |      Owner:
         Type:  enhancement  |     Status:  needs_review
     Priority:  normal       |  Milestone:  Tor: 0.2.6.x-final
    Component:  Tor          |    Version:
   Resolution:               |   Keywords:  tor-relay, nickm-patch
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+------------------------------------

Comment (by teor):

 Also, from
 http://www.securityfocus.com/archive/82/298061/2002-10-27/2002-11-02/0
 linked from http://www.dwheeler.com/secure-programs/Secure-Programs-HOWTO
 /protect-secrets.html which is quoted in comment 1:

 "If you don't like the "volatile" solution
 (I don't, because access to volatile objects may be significantly slowed,
 and because aliasing volatile objects with non-volatile-qualified pointers
 and accessing through such an alias invokes undefined behavior, and
 because
 volatile seems like the sort of thing broken implementations may get
 wrong),
 use the external-memset-wrapper one I proposed in my previous note."

 I don't like undefined behaviour - it tends to make conforming, optimising
 compilers misbehave, and unpredictably as they add new optimisations. We
 don't want to do things for broken compilers that break conformant ones.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7419#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online