From: chuck gelm <chuck@gelm.net>
To: scott@dctchambers.com
Cc: linux-admin@vger.kernel.org
Subject: Re: Single purpose
Date: Mon, 17 Jul 2006 11:44:56 -0400 [thread overview]
Message-ID: <44BBB078.4020808@gelm.net> (raw)
In-Reply-To: <3753.192.168.99.70.1153149630.squirrel@dctchambers.com>
Hi, Scott:
'What, more exactly, do you need? ' like:
On what network is the (kiosk) workstation (local, public, private) ?
Is the workstation is on the same network as the
'corporate web site' ?
Seems like a firewall using IPTABLES would suffice.
Restrict the network to only the IP address of the
'corporate web site'. Only allow port 80 (http).
Remove all uneeded applications
and services. I assume that most 'kiosks' are very much
like this. Did you find 'kiosk' examples that do not
meet your needs? If yes, what parts do not meet
your needs?
HTH, Chuck
Scott Taylor wrote:
>On Mon, July 17, 2006 08:18, chuck gelm wrote:
>
>
>>Hi, Scott:
>>
>>I am not sure about 'wisdom', but here is a thought.
>>How large is the 'specific web site' and how often does
>>the data change? Perhaps a local copy of the website
>>would suffice if the amount of data is small. Would an
>>image of the 'SWS' fit on a DVD/R?
>>
>> How often does the data on the SWS change?
>>If seldom and the data is small (<4.7 GB), a local
>>DVD/R might work.
>>
>>Or, perhaps the data returned from the SWS is
>>dynamic and this will not work.
>>
>>
>
>You're right. That wouldn't work.
>
>
>
>>What, more exactly, do you need?
>>
>>
>
>I need a workstation that can not be changed, in any way, by users, and
>they need to access a corporate web site, and nothing else. That is all,
>and nothing more.
>
>Thanks just the same.
>
>--
>Scott
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-admin" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
next prev parent reply other threads:[~2006-07-17 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-15 20:04 Single purpose Scott Taylor
2006-07-15 20:28 ` shane
2006-07-17 14:30 ` Scott Taylor
2006-07-17 15:18 ` chuck gelm
2006-07-17 15:20 ` Scott Taylor
2006-07-17 15:44 ` chuck gelm [this message]
2006-07-17 21:00 ` Glynn Clements
2006-07-26 18:35 ` Gustavo Guillermo Pérez
2006-07-26 18:42 ` Gustavo Guillermo Pérez
2006-08-02 0:42 ` Stephen Samuel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44BBB078.4020808@gelm.net \
--to=chuck@gelm.net \
--cc=linux-admin@vger.kernel.org \
--cc=scott@dctchambers.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).