For security reasons
I want to disable screen shot or screen sharing by any known/unknown program.
I also want to disable any programmatic mouse and keyboard or any other input. While physical keyboard/mouse should work.
Only person sitting in front of the computer should be able to access physical machine without any issue.
This is for security reason. No body should be able to put malware/spyware and see what i am doing.
SetwindowDisplayAffinity to disable screen shot of a window.
Use a low-level keyboard hook to detect and ignore injected keystrokes.
Related
I checked the Firefox share screen here https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/
When I click the button, this dialog show up: https://i.imgur.com/TdMg6Ki.png
How can I allow the share screen automatically, Firefox don't even allow remember choice. I know it's security risk, but in my case, I take the risk.
Is there any way ( config, run with hidden flag ) allow website access screen sharing without prompt ?
Thank you
This can be turned off via the media.navigator.permission.disabled preference in about:config. Quite useful for automated testing obviously.
I am using Awesome WM, and I use xscreensaver to lock the screen if I'm away for a certain amount of time. I also enabled screen power management in the xscreensaver configuration to turn off the monitor after some time. I want to implement a "persentation mode", which disables these. I can disable screen locking by calling xscreensaver-command -deactivate periodically. However, it doesn't stop the screen from going idle. I tried blocking idle in systemd-inhibit, but that doesn't help either.
Is there any way to temporarily disable screen power management in xscreensaver? Or, alternatively, is there any alternative screen locker / power management tool that allows locking the screen, turning off the screen, and temporarily disabling itself from command line?
It's hard to tell what exactly turns off your screen. You can give xset a try. You can control the screensaver (screen going black after some while) with it. For example xset s off.
From man xset:
For screen-saver control:
s [timeout [cycle]] s default s on
s blank s noblank s off
s expose s noexpose
s activate s reset
For screen locking I love to use slock.
EDIT: Slock doen't have a auto lock capability. You need a tool (for example xautolock) which watches your X and calls slock.
xautolock -time 2 -locker slock
I need that one of our computers, when it boots, automatically opens Internet Explorer. IE should be Full screen (without the border and the address bar.. totally full screen) and open a default URL (no problem on this, just set it as homepage). Then I would need that if a textbox inside this page gets focus then the on-screen keyboard should show up.
can this be achived with standard windows settings or do i have to write my own program with browser inside? if i write my own vb.net program, can the program be totally fullscreen (without the X to close and without seeing the task bar)
what we need to do is set up a sort of a internet station where random people can browse a given page without having a keyboard and without having the possibility to access the system.
thanks
I would say it is possible - but I have no idea how to achieve this. There will be a registry setting of some sort which SHOULD enable the keyboard. Sorry - I barely touched this areas :(
I'm developing a software that should be able to "lock" the computer in it, so there will be no chance for any user to return to Windows and use other softwares except if he closes the software using a key (I guess this is what people call to operate in kiosk mode).
After much research I managed to disable Ctrl, Windows Key and Alt using hooks and registry files, so with this I could eliminate (I think) all ways of the user getting away from the software from the keyboard.
But now I found that if somebody plugs an USB device (e.g. a pendrive/data traveler), considering W7, the taskbar immediately apears alongside that traditional dialog where you can choose what you're going to do with the USB device you plugged (open its contents with Explorer, etc.), so somebody can go away from the software apart from the keyboard.
I would like to know how could I stop this, by code or registry (code would be much better!), so if somebody plugs a pendrive the taskbar don't appear and neither that dialog. If I can block USB input from thoose already used (by mouse and keyboard), that could also help.
Btw, if somebody knows of any other tricky way of going away from a kiosk-mode app, tell me!
Thanks,
Momergil
If you replace explorer.exe with your own application in the Shell value of the Winlogon registry key, your application will be started instead of Explorer. Then all you need to do is disable Task Manager, which can be done via a group policy setting.
The full path to the Winlogon key is
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
Why don't you just stop explorer.exe, disable Ctrl+Alt+Delete and Ctrl+Shift+Esc to enter kiosk mode?
I've been searching forever for a solution to this, so I thought I'd seek out the brainpower of greater minds than mine. I'm developing a Cocoa app that uses the Accessibility API to manipulate another program (it's a hotkey app). The app I'm controlling typically has multiple windows open, with some hidden behind others. What I would like to do, if it's possible, is to send mouse events to windows using the Accessibility API in a way that presses a button in the window without bringing it to the foreground (interact with the window but don't activate it). The reason I'm trying to do this is that sending the mouse event to this other window will force it to the foreground and disrupt the user's interaction with the foremost window.
This is possible on Windows - apparently, because apps similar to mine do it there - but I'm getting the feeling that this isn't possible with Cocoa, given the way the window manager works. Am I mistaken?
Accessibility is higher-level than that. You send, for example, AXPress actions to AXButton objects, but “press” is not necessarily a click—pressing the space bar while a view is focused, for example, is also a “press”. AXPress is a high-level action that means “do your thing”, which obviously has meaning for some views (such as buttons) and not others (such as fields).
Accessibility activating the application does make sense when you look at it from its intended purpose: Assistive devices for disabled users. If the user “presses” something by whatever means, they probably intend to activate the application and work in it.
Quartz Event Services will get you almost there: You can create an event tap for the process you want to control, and you can forge events and send them to a tap. The catch is that you can only send events to a tap when the tap fires—i.e., when the application already has an event to deal with. When it doesn't, you're stuck.