Re: Xwindow on shell/web server
From: jpd (read_the_sig_at_do.not.spam.it.invalid)
Date: 06/19/05
- Next message: jpd: "Re: FreeBSD 5.4 Install Guide is available"
- Previous message: Christopher Nehren: "Re: install without bootable cdrom and without floppy"
- In reply to: Ing. Branislav Gerzo: "Re: Xwindow on shell/web server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 18 Jun 2005 22:29:45 GMT
Begin <235932948.20050617151951@NO2geSPAM.us>
On 2005-06-17, Ing. Branislav Gerzo <2GE@NO2geSPAM.us> wrote:
> [...] it is picture grabber from html rendered pages. It is as:
> http://www.html2jpg.com/ - If you don't want to click, from the site:
> Did you ever need some screenshots of a website?
Me? Very, very rarely. But it does explain why you'd need X and a
browser. I'd say that is not something you want to do on your server,
but on a workstation, unless you want to do it really often.
To be honest I can't imagine why you'd want to do that, but hey.
[snip]
> I see, thanks for nice answer. My brother don't want install that all
> the crap, but I wanted to know, when X is installed, if there are some
> security / speed / performance issues
Yes, there are. X is a memory hog (and so is any browser) and it
isn't the fastest thing Out There, and this will affect the maximum
screenshots per minute you can make. But given a reasonably recent
machine with enough memory, that may or may not be an issue. This
depends, of course, on all the other things that server is doing. Add
to that the issue of this task being not the server its primary task,
and I can imagine why your brother doesn't want it on his box. This is a
different issue from having all that installed.
There are security issues, too: X is network aware. You can nail its
network interface shut in a variety of ways like using a firewall,
or not enabling its networking (forcing it to only use a unix domain
socket) in the first place. Then there's the browser, which can have its
own set of security problems, (think rogue javascript or java applets or
even just plain buffer overflows), and that you're using in an automated
fashion. That is something it wasn't designed for; popups and even
popunders or other potential problems will usually get spotted sooner
or later when you're there, but you won't be. Then there's the software
that drives it, but I'm not familiar with it so I won't comment on that
further.
So, in short: Yes, there are numerous potential problems with it.
-- j p d (at) d s b (dot) t u d e l f t (dot) n l .
- Next message: jpd: "Re: FreeBSD 5.4 Install Guide is available"
- Previous message: Christopher Nehren: "Re: install without bootable cdrom and without floppy"
- In reply to: Ing. Branislav Gerzo: "Re: Xwindow on shell/web server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
