1. 25 Apr, 2022 1 commit
  2. 24 Apr, 2022 2 commits
  3. 20 Apr, 2022 1 commit
  4. 19 Apr, 2022 1 commit
  5. 18 Apr, 2022 2 commits
  6. 16 Apr, 2022 1 commit
  7. 12 Apr, 2022 1 commit
  8. 11 Apr, 2022 1 commit
  9. 09 Apr, 2022 1 commit
    • longpanda's avatar
      cc · 07693bf8
      longpanda authored
      07693bf8
  10. 08 Apr, 2022 2 commits
  11. 07 Apr, 2022 3 commits
  12. 06 Apr, 2022 10 commits
  13. 05 Apr, 2022 3 commits
  14. 02 Apr, 2022 1 commit
  15. 01 Apr, 2022 1 commit
  16. 30 Mar, 2022 2 commits
  17. 29 Mar, 2022 2 commits
  18. 26 Mar, 2022 5 commits
    • longpanda's avatar
      1.0.72 release · ed1aa3d5
      longpanda authored
      ed1aa3d5
    • longpanda's avatar
      Update README.md · 8e661103
      longpanda authored
      8e661103
    • Kerollos Magdy's avatar
      add GitHub actions state to README (#419) · f5f65aa8
      Kerollos Magdy authored
      
      
      * add GitHub actions state to README
      
      * Update README.md
      
      * remove link in README
      Co-authored-by: default avatarDylan M. Taylor <dylan@dylanmtaylor.com>
      f5f65aa8
    • geeseven's avatar
      add IMG to no iso tip (#480) · 4e5fcf21
      geeseven authored
      4e5fcf21
    • Celine Lee's avatar
      Modify casting in protection against underflow (#1514) · 9789069c
      Celine Lee authored
      Dear Ventoy community –
       
      Our team is working with your code and we noticed this if logical expression:
       
                      if (len - 1 - (int)(long)(pos - pwdstr) != 32)
       
      We studied the surrounding code. We believe we understand the intention of the type casts in the above if statement. It seems they were meant to ensure an underflow doesn’t occur by the subtraction between to char pointers, which is a great catch (!). However, we believe the way the type casts are structured, the code is not actually protecting against such underflow because pwdstr isn’t cast into a signed long until after the subtraction occurs. To properly protect this code against underflow, we believe it should be changed to something like the following:
      
      if (len - 1 - ((long)pos – (long)pwdstr) != 32)
      
      Or, to enhance readability for junior engineers who may not know that the “long” type cast is implicitly of a signed integer type, we could include the `signed` keyword for added verbosity:
       
      if (len - 1 - ((signed long)pos – (signed long)pwdstr) != 32)
       
      Thank you!
      9789069c