Securing Linux based public access terminals
From: Andrew Shore (andrew.shore_at_holistecs.com)
Date: 07/15/04
- Previous message: dsimcik_at_bentley.edu: "Tunneling SMTP Traffic Via SSH Question"
- Next in thread: tbishop_at_micron.com: "RE: Securing Linux based public access terminals"
- Maybe reply: tbishop_at_micron.com: "RE: Securing Linux based public access terminals"
- Reply: Ant: "Re: Securing Linux based public access terminals"
- Reply: Brett Anderson: "Re: Securing Linux based public access terminals"
- Reply: mr.happy: "Re: Securing Linux based public access terminals"
- Reply: E.Scichilone: "Re: Securing Linux based public access terminals"
- Maybe reply: M Shirk: "RE: Securing Linux based public access terminals"
- Maybe reply: Rocky Heckman: "RE: Securing Linux based public access terminals"
- Maybe reply: Brett Anderson: "RE: Securing Linux based public access terminals"
- Reply: Shyam Mani: "Re: Securing Linux based public access terminals"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 15 Jul 2004 12:48:33 +0100 To: <security-basics@securityfocus.com>
Hi
I have a project where I need to give access to the internet to groups
of users who do not work for the company running the workstations.
Hence, the company do not want the users to access any other part of the
network. For reasons too complicated to go into here I can't hive this
portion of the network off onto a DMZ or even a secure vlan.
What I would like to is run a Linux workstation (RedHat probably 9 even
though it's out of support) but when the user logs into the windows
session all they get is the browser. No menus no right click on the desk
top just a basic single application "dumb terminal". I've seen this done
before but it was too well secured for me to see how it was done! Also
I'd like to the workstation to log straight in as a local user with out
user intervention.
Any ideas how I can achieve this or perhaps secure it in another way, I
remember with windows 3.x you could change the windows manager settings
in win.ini and it did exactly what I want. I just really don't want to
use Windows 3.1 ;)
TIA
Andy
---------------------------------------------------------------------------
Ethical Hacking at the InfoSec Institute. Mention this ad and get $545 off
any course! All of our class sizes are guaranteed to be 10 students or less
to facilitate one-on-one interaction with one of our expert instructors.
Attend a course taught by an expert instructor with years of in-the-field
pen testing experience in our state of the art hacking lab. Master the skills
of an Ethical Hacker to better assess the security of your organization.
Visit us at:
http://www.infosecinstitute.com/courses/ethical_hacking_training.html
----------------------------------------------------------------------------
- Previous message: dsimcik_at_bentley.edu: "Tunneling SMTP Traffic Via SSH Question"
- Next in thread: tbishop_at_micron.com: "RE: Securing Linux based public access terminals"
- Maybe reply: tbishop_at_micron.com: "RE: Securing Linux based public access terminals"
- Reply: Ant: "Re: Securing Linux based public access terminals"
- Reply: Brett Anderson: "Re: Securing Linux based public access terminals"
- Reply: mr.happy: "Re: Securing Linux based public access terminals"
- Reply: E.Scichilone: "Re: Securing Linux based public access terminals"
- Maybe reply: M Shirk: "RE: Securing Linux based public access terminals"
- Maybe reply: Rocky Heckman: "RE: Securing Linux based public access terminals"
- Maybe reply: Brett Anderson: "RE: Securing Linux based public access terminals"
- Reply: Shyam Mani: "Re: Securing Linux based public access terminals"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|