Recommended Posts

We've been using Opera on our campus kiosk stations for a while now, and have recently decided to go in that direction again for the latest rendition of these machines. Opera's built-in kiosk feature makes it an attractive option, especially on the slow hardware that we use (older iLamps). Our kiosks use the kioskresetstation flag in full screen mode (no access to menus in the Finder bar) to ensure that private data is wiped after some interval of inactivity.

Using the latest versions of Opera on both Windows and Tiger, we see that the kioskresetstation flag does not clear authenticated sessions (or browsing history, and possibly does nothing more than take the browser to its homepage). Has kiosk mode changed? Are there additional settings that must be changed (the ability to log into webmail is essential, so we can't just outright disable cookies) in order to ensure that kioskresetstation does clear authenticated sessions?

Steps to observe this behavior:

Open Opera in kiosk mode with the -kioskmode and -kioskresetstation switches (we run -kioskmode -kioskwindows -kioskbuttons -nowin -resetonexit -nochangebuttons -nodownload -nosave -nomail -nomaillinks -nochangefullscreen -nocontextmenu -nohotlist -nokeys -nomenu -nominmaxbuttons -noprint -nosplash -nosysmenu -kioskresetstation).

Log into some website (neowin.net).

Allow the kiosk to reset (default timeout is 30 seconds of idle time).

Visit the site that you just logged into (adding insult to injury, the site URL is retained in the address bar dropdown).

Are you still logged in, and better yet, given that this is a kiosk environment, should you expect to be after a browser "reset"?

Link to comment
https://www.neowin.net/forum/topic/663060-kiosk-reset-behavior/
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.