Posts con #JavaScriptCore

#JavaScriptCore

Posts públicos de X que usan #JavaScriptCore.

Hashtags relacionados

  1. RET2 Systems@ret2systems
    One of our favorite #debugging technologies comes from @mozilla, so this week we wanted to help highlight an amazing project. Part three of our #Pwn2Own series makes use of timeless debugging to root cause an exploitable race condition in #JavaScriptCore:
    Descargar
    2139235
  2. Varik@D4RK7ET
    New write-up with @GenericCoding on pois0nSword, our iOS 26.1 port of DarkSword: bypassing PAC to reach arbitrary native calls from a WebKit renderer R/W, by making dyld's own loader do the write. #WebKit #JavaScriptCore #iOS #exploitdev
    12710516K
  3. RET2 Systems@ret2systems
    Vulnerability weaponization is the most frequently discussed topic of the #exploit development lifecycle. Here's our take on weaponizing a #JavaScriptCore vulnerability from the ground up: #Pwn2Own part four
    Descargar
    3149280
  4. WebKitGTK@WebKitGTK
    🛠 WebKitGTK+ development release 2.21.1 is now available! 👉 We are moving to a new, GLib-based API for JavaScriptCore and deprecating most of the DOM bindings API. Developers, please test and let us know what you think! 📜 Release notes:
    335
  5. WebKitGTK@WebKitGTK
    @WebKitGTK
    The new JSC API in 2.21.x should make it much more convenient to interact with the JavaScript world from your C/C++ code — or from any other languages supported through GObject-Introspection 🙌. Lack of introspection support was one of the shortcomings of the old API.
    123
  6. WebKitGTK@WebKitGTK
    @WebKitGTK
    The documentation for the new GLib-based #JavaScriptCore API we are introducing in the 2.21.x development releases is now available in our website, and should be fully GObject-Introspectable: 🛠
    012
  7. Hosein Ghasemi@_ghasemi_
    اگه تا حالا از #Phrack مقاله نخوندید، یه نگاه به این مقاله بندازید و با #Phrack آشنا بشید، بد نیست: Attacking JavaScript Engines: A case study of #JavaScriptCore and #CVE_2016_4622
    008
  8. Dk Deepak@DeepakEswar4
    🚀"Bun speeds things up by utilizing the JavaScriptCore engine, while Node.js relies on the JavaScript V8 engine. JavaScriptCore is optimized for quicker startup, making Bun a great choice for faster performance. 💨 #NodeJS #JavaScriptCore #Bun #100daysofcoding"
    Descargar
    003244
  9. Paulo Matos✓@pocmatos
    At @igalia we not only do a lot of feature development on JSC 64bits but also on 32bits (ARMv7 and MIPSel). Here's a brief tour of the implementation of the for-of intrinsic for JSC 32bit that landed a few months ago: #webkit #javascriptcore #javascript
    099
  10. Erick Wendel | localstudio.dev✓@erickwendel_
    @erickwendel_
    One of the best videos I've ever recorded is the one I teach how to recreate Node.js from Scratch and it has reached more than 100K people around the globe🥳 I have researched a lot about the main components used in the original project such as Event Loop, V8, and C++ layers /2
    105844
  11. Paulo Matos✓@pocmatos
    The first is always special - My first task as an Igalian and WebKit contributor was to refactor register information in the JSC backend. Happy to say the bird has landed: #igalia #webkit #javascriptcore
    0111
  12. NativeScripting@NativeScripting
    The #NativeScript team is working on total revamp of the #iOS runtime. The goal is to use the V8 engine instead of #JavaScriptCore. Several months ago the team shipped an alpha version of this runtime and now it’s time to announce the next iteration.
    0514
  13. Mostrar más posts