mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: chip@valinux.com (Chip Salzenberg)
To: linux-kernel@vger.kernel.org
Cc: terje.malmedal@usit.uio.no
Subject: Remote Management (was Re: Alert on LAN)
Date: Wed, 14 Mar 2001 13:26:04 -0800	[thread overview]
Message-ID: <E14dImS-0006DX-00@traeki.engr.valinux.com> (raw)
In-Reply-To: <E14d8Rh-0007Xr-00@morgoth>
In-Reply-To: <Pine.LNX.4.10.10103131842110.19423-100000@clueserver.org>

IBM says, as quoted by Terje Malmedal:
>   With the latest release, Alert on LAN 2 now extends IT
>   capabilities to remotely manage and control their
>   networked PCs:
>
>       Remote system reboot upon report of a critical failure 
>       Repair Operating System 
>       Update BIOS image 
>       Perform other diagnostic procedures 

OK, fine... but: Where are the authentication and authorization?!
Surely I'm not the only person to see in this "Alert On LAN 2" the
potential for a security disaster.  I know I will never buy anything
that supports AOL2 until its security features are openly documented
and testable.

> The feature I really need is to be able to reset the machine
> remotely when Linux is hung.

Some current PC motherboards support remote management via a serial
line.  Of course, you'll need software: The VA Cluster Manager (GPL'd
- http://sourceforge.net/projects/vacm) can monitor and control any
number of clients, limited only by the number of serial ports you can
give it.  VACM also includes optional client support for enhanced
monitoring, e.g. of temperatures.  I'm not sure which motherboards it
supports, but I'm sure you can find current documentation.  :-)

Granted, this is not cheap.  A VACM-style approach costs some money
for the monitor computer, and some convenience for installing the
serial lines; meanwhile, AOL2 promises to do it all over Ethernet.
But with VACM, you can be sure that somebody has to log in to the
monitor computer -- with security levels you control! -- before they
can control or even monitor any connected clients.

BTW, in the spirit of full disclosure: VACM is a product of VA Linux
engineering, and I work for VA.  But VACM is GPL'd and we don't charge
for it, so I have little financial interest in seeing it used.  I just
*hate* it when people play fast & loose with my security.

  parent reply	other threads:[~2001-03-14 21:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-13 20:33 Alert on LAN for Linux? Terje Malmedal
2001-03-14  2:43 ` Alan Olsen
2001-03-14 10:23   ` Terje Malmedal
2001-03-14 21:26   ` Chip Salzenberg [this message]
2001-03-15 18:31     ` Remote Management (was Re: Alert on LAN) Terje Malmedal
2001-03-15 19:03       ` Chip Salzenberg
2001-03-14 22:23   ` Alert on LAN for Linux? Bernd Eckenfels
2001-03-21 17:08 ` Alan Cox
2001-03-24  6:51   ` Eric W. Biederman

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=E14dImS-0006DX-00@traeki.engr.valinux.com \
    --to=chip@valinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=terje.malmedal@usit.uio.no \
    /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

all inboxes | Powered by JetHome®