- A pápa egyre jobban tart a romlott AI veszélyeitől
- Az USA nem akarja visszafogni Kína növekedését
- Súlyos adatvédelmi botrányba kerülhet a ChatGPT az EU-ban
- Windows 10
- OpenMediaVault
- YouTube
- Kodi és kiegészítői magyar nyelvű online tartalmakhoz (Linux, Windows)
- Milyen program, ami...?
- Microsoft Excel topic
- Otthoni hálózat és internet megosztás
Ú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
- Új Hp Pavilion 15-eh Fémházas Szuper Laptop 15,6" -30% AMD Ryzen 7 5700U 8Mag 16/1TB FHD MATT
- ATI RADEON RX 480 -8 gb DDR5 256 bit videokártya
- Geforce GTX 460-1 gb DDR5 256 bit videokártya
- Geforce G 210 -1 gb videokártya
- Díszdobozos Lenovo Yoga Slim 7i Pro "Kis Gamer" Ultrabook 14" -40% i5-11300H 16/512 QHD+ 2,8K OLED