Re: [tor-bugs] #25841 [Core Tor/Tor]: Write test for Rust fragile hardening

[Tor Bug Tracker & Wiki]

#25841: Write test for Rust fragile hardening
--+--
 Reporter:  Hello71   |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  rust  |  Actual Points:
Parent ID:  #25386| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dgoulet):

 * keywords:   => rust
 * milestone:   => Tor: unspecified


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #25841 [Core Tor/Tor]: Write test for Rust fragile hardening

[Tor Bug Tracker & Wiki]

#25841: Write test for Rust fragile hardening
--+
 Reporter:  Hello71   |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:  #25386
   Points:|   Reviewer:
  Sponsor:|
--+
 We should write some tests to ensure that asan is working to check memory
 leaks, dangling pointers, and so on. I know that #25386 links asan, but I
 don't know if it actually checks stuff that we want checked. We should
 check that it checks what we want checked.

 I envision this looking like a `test_fragile_hardening.c` (or a series of
 such files) and some helper Rust code that does some bad behavior and a
 wrapper that ensures that it crashes.

 Landing this requires #25386, but writing it does not; just assume that
 Rust and C can arbitrarily call each other (with the proper boilerplate),
 and asan is supposed to catch everything that it catches in C.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs