Re: [cobalt-users] Telnet

[Kris Dahl <kris@xxxxxxxxxxxxx>]

> I agree.... there is no reason to give telnet access to a
> Linux box, or RAQ server.... A good system admin or assistant
> will be willing to help out a user.

There are plenty of reasons to give shell access.  MySQL client for
one--security on the database access and from what host is important as
well.  Have you ever tried to debug PERL scripts without shell access?  Its
like trying to cut a steak with spoon.  Ever tried developing PERL on a
remote NT machine?  Same thing.  Have you ever tried to set up an advanced
ecommerce site without shell access?  I'd like to know how you compile
OpenSSL over FTP.  Or cURL.  Or any of the graphics editing libraries.  If
you are doing anything serious you NEED shell access.

I've administered machines before and I can attest that I am very willing to
help, but I am not going to make it my full time job to act as someone's
personal shell. (ksh-- kris shell)

I guess that anyone who is serious should either have own server.

> A user should only have FTP access, and sometime chmog
> depending on the RAQ and the user trust.

Nutz.  Just crazy.
 
> 1 There is a real good user interface on the RAQ's

For somethings.  I never saw anything like Maintenance-->GCC Compile in the
gui.

> With Linux becoming real popular among users vs Windows I see a time
> when there will be just as many Linux security patches as there is with
> windows
> because some of the bad boys will figure out how to exploit a hole in Linux
> Red Hat 6 is the same basic OS as the Cobalt OS and lots of
> Mall stores are now carrying it, I even saw Red Hat 6 in Sams Club...
> (I also include Mandrake and Suse in that category)

When I am looking for an outside, out-sourced, leased web host, I require
several things:
-OUTSTANDING route (read: direct) to one or more of the major backbones
-Adequate power protection (at least 8 hours)
-Linux server
-Apache
-PHP
-MySQL
-Recent version of PERL
-Shell access
-Competent admins that when I request a legitimate request (like please add
a .php3 handler in your httpd.conf--heres the code and line you should edit)

> Cobalt will have to get off there high horse and address these issues of
> security and
> not say "Updates will Void your Warranty"

More than often, I have found Cobalt to be more than willing to help with
'voided' machines.  They just don't have the ability to or want the liablity
in supporting anything except the 'norm'.  I don't blame them.  If you are
wanting to do something a little different, I would suggest several things:
-ALWAYS buy from a VAR with skilled systems engineers.  They will save your
ass and your money when it hits the fan.  They can push Cobalt.  They are
trained and are good at making 'solutions' out of puzzle pieces.
-Be prepared to spend a little money on consulting fees to get your server
into tip-top shape.  This is if you aren't able to do it yourself.  This
isn't rocket science, but it isn't building a bird house either.  It takes
some skills that you may not have, but your VARs SEs may.
-If need be, purchase a different server.  You may be outgrowing Cobalt's
target market.  Your VAR can help you decide which server is best for
you--which may or may not be a Cobalt product.  It depends on a lot of
factors.  Again, if you are serious about provided your clients with the
right solution, be prepared to pay an engineer or consultant to make it
happen.

Someone said "Linux isn't free if you value your time."  Weather you take
the time to learn and then do-it-yourself, or if you want to pay a
consultant, it is going to cost you something.  So when I say 'be prepared
to pay a consultant'--I mean either be prepared to pay a consultant or be
prepared to learn the necessary skills to match those of the consultant.  I
suggest comparing the cost of both and then make your decision on which to
go with.

-k