- Windows 11
- Augusztustól nagyot változik a Shein élete
- Telekom otthoni szolgáltatások (TV, internet, telefon)
- Hálózati / IP kamera
- 3 évig még biztosan nem rendelhetünk Xiaomi EV-t
- DIGI internet
- Agyi chipes gyártóba fektetett a kriptocég
- Az Apple iPadOS-t is megrendszabályozza az EU
- Milyen routert?
- Ingyenes vagy akciós szoftverek
Új hozzászólás Aktív témák
-
X-COM
nagyúr
válasz Nagy Gábor #4 üzenetére
nem ártana komolyabban tájékozódnod mielőtt súlyos kijelentéseket teszel
[link]
98:
With WMF we want to be very clear: the Windows 9x platform is not vulnerable to any ''Critical'' attack vector. The reason Windows 9x is not vulnerable to a ''Critical'' attack vector is because an additional step exists in the Win9x platform: When not printing to a printer, applications will simply never process the SetAbortProc record. Although the vulnerable code does exist in the Win9x platform, all ''Critical'' attack vectors are blocked by this additional step. The remaining attack vectors that we have identified require extensive user interaction and are not rated ''Critical''. Again the ''Critical'' rating refers to code execution attacks that could result in automated attacks requiring little or no user interaction.
szó nincs backdoor-ról, akkoriban szükséges fícsör:
To detail it a little bit, SetAbortProc functionality was a needed component in the graphics rendering environment for applications to register a callback to cancel printing, before even the WMF file format existed. Remember, those were the days of co-operative multitasking and the only way to allow the user to cancel a print job would be to call back to them, usually via a dialog. Around 1990, WMF support was added to Windows 3.0 as a file-based set of drawing commands for GDI to consume. The SetAbortProc functionality, like all the other drawing commands supported by GDI, was ported over (all in assembly language at this point) by our developers to be recognized when called from a WMF. This was a different time in the security landscape and these metafile records were all completely trusted by the OS. To recap, when it was introduced, the SetAbortProc functionality served an important function.
MSDN:
[link]
[Szerkesztve]Blog:http://ikszkom.freeblog.hu RSS:http://ikszkom.freeblog.hu/rss.xml http://live.xbox.com/member/ikszkom
Új hozzászólás Aktív témák
- Samsung Galaxy S22 Ultra Eladó...
- Vostro 3591 15.6" FHD i5-1035G1 GeForce MX230 16GB 512GB NVMe magyar bill., gar
- ELADÓ 32 DB Nvidia RTX 3060 Ti és 8 DB Zotac Gaming Geforce RTX 3080 Trinity / KOMPLETT BÁNYAGÉP
- Intel NUC5CPYH (Celeron N3050, N3060, J3060) - 4GB RAM, 120GB SSD
- Corsair TX650 V2 650W 80+