{"id":859,"date":"2019-11-11T10:00:00","date_gmt":"2019-11-11T10:00:00","guid":{"rendered":"http:\/\/172.23.1.43\/?p=859"},"modified":"2022-06-07T22:25:59","modified_gmt":"2022-06-07T22:25:59","slug":"wnf-and-task-scheduler","status":"publish","type":"post","link":"https:\/\/blog.n-dol.org\/2019\/11\/11\/wnf-and-task-scheduler\/","title":{"rendered":"WNF and Task Scheduler"},"content":{"rendered":"\n

As I was investing another subject, I came across a scheduled task with a custom trigger and when I looked at the XML, we can see WnfStateChangeTrigger<\/code> as the trigger type. I began to look for documentation but nothing valuable.<\/p>\n\n\n\n

Until I came across a blackhat conference by Alex Ionescu<\/a> and Gabrielle Viala<\/a> where they explain what WNF is.<\/p>\n\n\n\n

The interesting thing here is that WNF stand for Windows Notification Facility and is the notification system within the Windows OS. So it seems that the Task Scheduler is capable of subscribing to event and launch task against it. <\/p>\n\n\n\n

How WNF works ?<\/h2>\n\n\n\n

In a nutshell and as 20k feet view: it’s notification system where processes can subscribe and publish without the need to wait for the other processes to be there. For example, if you want to be notified that wifi is connected then you subscribe to the event and the system will notify you that it did start and also can gives you more information like SSID name etc. The system or a process can also publish information to it.<\/p>\n\n\n\n

For (wayyyy) more information, watch the conference and read these: <\/p>\n\n\n\n