New answers tagged

3

Answer is quite simple Win+L is not a sas and it does not need to be. It is used for locking the device. There is a group policy to control the sas for triggering the login. You may set it so the CTRL+ALT+DEL is required for every login independently of how the station got locked, be it via shortcut, time-out or any other way, after all locked state is ...


1

To answer this question, you need to understand the context and history of operating systems and their security model. Desktop operating systems were designed in a time where the biggest security consideration was protecting you and the system itself from the other human users of the system. When multiple people are all using a shared machine, you need to ...


1

From a security POV the reason this is possible in Windows is that there are 3 (more than that really) permissions levels that a program may run at. Windows Store apps run with enumerated App permissions that restrict the application's ability to run as the desktop user. A normal "desktop" program runs with the full privileges of the desktop user, ...


1

The Windows API have native support for doing this. A scripting language I have experience with, AutoHotKey, can readily make full screen any window available, using a single line of code. These functionalities are not some complex "hack" into the OS, but are built-in functions of the OS given to external software. You can also make commands to ...


37

A fullscreen app in C#: using System; using System.Windows.Forms; namespace FullScreen { static class Program { [STAThread] static void Main() { Application.EnableVisualStyles(); Application.SetCompatibleTextRenderingDefault(false); var fullscreen = new Form(); fullscreen....


44

Fullscreen is easy: The vast majority of video games, for example, do it. I don't know if Windows has a dedicated API call for this, but if it doesn't, it's easy to fake: Just make a screen-sized window with the "Always on Top" attribute and no window decorations. Disabling ALT+TAB is harder, but there are a number of options: for example, the ...


3

... it does not "talk to the internet ... There is a difference between does not usually talk to the internet or is not able to talk to the internet. As long as the application is not somehow sandboxed or firewalled some exploit can likely make the application talk to the internet. ... this application is a local tool only ... Just because it runs ...


1

Allowing unrestricted Docker commands on a host from (relatively) untrusted users is likely to be a cause of problems, as it allows for access to the underlying host OS. One example is file mounts. Using Hyper-V Windows containers, the user on the host used to check for permissions is LocalSystem , so any directory that user has access to can be mounted ...


2

When you do a PKINIT authentication to the KDC an additional field is included in the krbtgt response in the PAC called PAC_CREDENTIAL_INFO. This includes supplemental credentials for your logon such as the NTLM hash and the data is encrypted to the PK (DH) session key. The PAC is stuffed into the TGT where it's unreadable by the client. The client then ...


Top 50 recent answers are included