Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Proposed Linux server



On 24 Jan 2000, Kyle R. Rose wrote:

> etc.  There is no good reason to have X on a firewall that's going to
> sit in a closet.  Check through your packages: I'll bet you have stuff

I'll disagree there, but only conditionally.  It depends a great deal on
how the system will be set up, and what tradeoff between convenience and
security the admin is willing to live with...

For example, I run Licq, an ICQ replacement, on my firewall, because
certain features don't work through an IP masquerading Linux firewall
(there is a kernel module that supposedly will make this work now, but I
haven't gotten around to messing with it)...  It requires that the X
libraries be in place.

Another example is you may want to run X-based sniffer or monitoring
software on the firewall, which obviously will also need to have X libs
available.


-- 
"Quis custodiet ipsos custodes?"    "Who watches the watchmen?" 
-Juvenal, Satires, VI, 347 

Derek D. Martin      |  Senior UNIX Systems/Network Administrator
Arris Interactive    |  A Nortel Company
derekm at mediaone.net  |  dmartin at ne.arris-i.com
-------------------------------------------------

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org