public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Louis Zhuang <louis.zhuang@linux.co.intel.com>
To: Corey Minyard <cminyard@mvista.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] socket interface for IPMI
Date: 13 Mar 2003 11:29:47 +0800	[thread overview]
Message-ID: <1047526187.1051.30.camel@hawk.sh.intel.com> (raw)
In-Reply-To: <3E6F6963.6020100@mvista.com>

Hmmm, security is a big problem. I can not find an elegant way to do ACL
because these is no "inode" in sockfs... But how about making only root
be able to open IPMI socket like PACKET socket? Or else we can implement
a sysctl to indicate the legal user of the IPMI socket. 

Any comments?

  - Louis
On Thu, 2003-03-13 at 01:07, Corey Minyard wrote:
> I agree, and I've thought hard about this in the past.  The code looks 
> clean, and the design is straightforward.  However, I have not figured 
> out how to handle security.  In your implementation, anyone can open an 
> IPMI socket, which is a bad thing.  I like that fact that administrators 
> can set the permissions on the device any way they like (so it can 
> belong to root, a maintenance user, ACLs can be used, etc.)
> 
> Any thoughts on that?  Once that problem is solved, I would like to 
> include this.
> 
> - -Corey
> 
> Louis Zhuang wrote:
> 
> |Dear Corey,
> |    I'd like to propose a socket interface for IPMI. IMHO, IPMI is like a
> |mini-network so it is natural to manipulate IPMI by socket. Following
> |code demostrate the interface's usage.
> |P.S. the patch is a quick and dirty implementation with full of holes,
> |I'll refine it if you like to adopt it, so do not blame me at this time
> |;-).
> |



       reply	other threads:[~2003-03-13  3:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1047462010.1051.14.camel@hawk.sh.intel.com>
     [not found] ` <3E6F6963.6020100@mvista.com>
2003-03-13  3:29   ` Louis Zhuang [this message]
2003-03-17 17:27     ` [RFC][PATCH] socket interface for IPMI Corey Minyard

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=1047526187.1051.30.camel@hawk.sh.intel.com \
    --to=louis.zhuang@linux.co.intel.com \
    --cc=cminyard@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    /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