A question

A question

[khalid fahad]

Hi,
What is  the sudoers entry created to allow localuser to cat /etc/shadow)
Thanks

Re: A question

[William Roberts]

[-- Attachment #1.1: Type: text/plain, Size: 530 bytes --]

Sorry for the HTML...

This seems off topic. This is list for questions surrounding the linux
audit subsystem.

That file is usually user=root group=root mode=0644. Ie read only for all,
writeable for user root. No sudoers entry needed for read access.

On Sun, Sep 23, 2018, 21:30 khalid fahad <kfgm2001@gmail.com> wrote:

> Hi,
> What is  the sudoers entry created to allow localuser to cat /etc/shadow)
> Thanks
>
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
>

[-- Attachment #1.2: Type: text/html, Size: 1074 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: A question

[Frank Thommen]

All systems I know disallow reading of /etc/shadow for others or even 
group (for good reasons).  Hence sudo would be required.

frank


On 09/24/2018 06:35 AM, William Roberts wrote:
> Sorry for the HTML...
> 
> This seems off topic. This is list for questions surrounding the linux 
> audit subsystem.
> 
> That file is usually user=root group=root mode=0644. Ie read only for 
> all, writeable for user root. No sudoers entry needed for read access.
> 
> On Sun, Sep 23, 2018, 21:30 khalid fahad <kfgm2001@gmail.com 
> <mailto:kfgm2001@gmail.com>> wrote:
> 
>     Hi,
>     What is  the sudoers entry created to allow localuser to cat
>     /etc/shadow)
>     Thanks
> 
>     --
>     Linux-audit mailing list
>     Linux-audit@redhat.com <mailto:Linux-audit@redhat.com>
>     https://www.redhat.com/mailman/listinfo/linux-audit
> 
> 
> 
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit
> 

--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit

Re: A question

[Ed Christiansen MS]

[-- Attachment #1.1: Type: text/plain, Size: 1502 bytes --]

If you expect to pass any kind of security audit, the perms on 
/etc/shadow must be 0600.  Since it contains the actual password hashes 
no one can read it except root to prevent bad puppies from getting the 
hashes so they can reverse the hash by brute force on some other host.

On 9/24/2018 3:50 AM, Frank Thommen wrote:
> All systems I know disallow reading of /etc/shadow for others or even 
> group (for good reasons).  Hence sudo would be required.
> 
> frank
> 
> 
> On 09/24/2018 06:35 AM, William Roberts wrote:
>> Sorry for the HTML...
>>
>> This seems off topic. This is list for questions surrounding the linux 
>> audit subsystem.
>>
>> That file is usually user=root group=root mode=0644. Ie read only for 
>> all, writeable for user root. No sudoers entry needed for read access.
>>
>> On Sun, Sep 23, 2018, 21:30 khalid fahad <kfgm2001@gmail.com 
>> <mailto:kfgm2001@gmail.com>> wrote:
>>
>>     Hi,
>>     What is  the sudoers entry created to allow localuser to cat
>>     /etc/shadow)
>>     Thanks
>>
>>     --
>>     Linux-audit mailing list
>>     Linux-audit@redhat.com <mailto:Linux-audit@redhat.com>
>>     https://www.redhat.com/mailman/listinfo/linux-audit
>>
>>
>>
>> -- 
>> Linux-audit mailing list
>> Linux-audit@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-audit
>>
> 
> -- 
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4707 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: A question

[William Roberts]

[-- Attachment #1.1: Type: text/plain, Size: 2048 bytes --]

On Mon, Sep 24, 2018 at 11:40 AM Ed Christiansen MS <edwardc@ll.mit.edu>
wrote:

> If you expect to pass any kind of security audit, the perms on
> /etc/shadow must be 0600.  Since it contains the actual password hashes
> no one can read it except root to prevent bad puppies from getting the
> hashes so they can reverse the hash by brute force on some other host.
>

Before everyone gathers the villagers, pitchforks and torches, I made a
mistake.
I crossed passwd with shadow in my response.

With that said, I was going to let it die with Frank's response, but I can
see folks
will keep at it. Just let it die. It's an off topic question related with
how linux permissions
work not with the audit subsystem.


>
> On 9/24/2018 3:50 AM, Frank Thommen wrote:
> > All systems I know disallow reading of /etc/shadow for others or even
> > group (for good reasons).  Hence sudo would be required.
> >
> > frank
> >
> >
> > On 09/24/2018 06:35 AM, William Roberts wrote:
> >> Sorry for the HTML...
> >>
> >> This seems off topic. This is list for questions surrounding the linux
> >> audit subsystem.
> >>
> >> That file is usually user=root group=root mode=0644. Ie read only for
> >> all, writeable for user root. No sudoers entry needed for read access.
> >>
> >> On Sun, Sep 23, 2018, 21:30 khalid fahad <kfgm2001@gmail.com
> >> <mailto:kfgm2001@gmail.com>> wrote:
> >>
> >>     Hi,
> >>     What is  the sudoers entry created to allow localuser to cat
> >>     /etc/shadow)
> >>     Thanks
> >>
> >>     --
> >>     Linux-audit mailing list
> >>     Linux-audit@redhat.com <mailto:Linux-audit@redhat.com>
> >>     https://www.redhat.com/mailman/listinfo/linux-audit
> >>
> >>
> >>
> >> --
> >> Linux-audit mailing list
> >> Linux-audit@redhat.com
> >> https://www.redhat.com/mailman/listinfo/linux-audit
> >>
> >
> > --
> > Linux-audit mailing list
> > Linux-audit@redhat.com
> > https://www.redhat.com/mailman/listinfo/linux-audit
>
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit

[-- Attachment #1.2: Type: text/html, Size: 3723 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: A question

[Stephen Buchanan]

[-- Attachment #1.1: Type: text/plain, Size: 690 bytes --]

The best way I can think of to let it die off would be to specifically
answer the OP's question (even though we've established that it's a Very
Bad Idea)

Add the following line to /etc/sudoers (using visudo of course):
(assuming the intended user is "localuser" as implied by the language in
OP, and 'which cat' returns '/usr/bin/cat')
localuser   ALL:/usr/bin/cat /etc/shadow

On Mon, Sep 24, 2018 at 2:58 PM William Roberts <bill.c.roberts@gmail.com>
wrote:

> With that said, I was going to let it die with Frank's response, but I can
> see folks
> will keep at it. Just let it die. It's an off topic question related with
> how linux permissions
> work not with the audit subsystem.
>

[-- Attachment #1.2: Type: text/html, Size: 1301 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

Re: A question

[Zhang, Helin]

Hi Kanani

Within around one year, we have implemented input set to reconfigure some registers to select which field to be used for hash calculation.
So I think it should work quite better now with using X710 or XL710. What’s your issue here?
Could you help to have a try and tell me the real issue in your side? Hopefully I can help a little bit.

Regards,
Helin

From: kamiar kanani [mailto:kamiar.kanani@gmail.com]
Sent: Sunday, January 8, 2017 8:04 PM
To: Zhang, Helin <helin.zhang@intel.com>
Subject: A question

Hi Helin

I read a post from you in one of the DPDK mailing list about a problem with XL710 symmetric RSS configuration.
the problem states limitation in the XL710's capability of redirecting fragmented packets. the link is:
http://dpdk.org/ml/archives/dev/2015-July/022453.html
I searched through internet but I didn't find any thing better. It would be a great help to me if you could
give me any hint about what can be done for the problem, if there is any update.

thanks a lot

a question

[lxc-users]

Hello,

I've got a question regarding that stuff we discussed recently, please read it here <http://sheltebave.fmsrep.com/aerhfce>

Warmest, lxc-users

A question..

[Nicola Ranaldo]

Dear Dave,

Some time ago Chirstophe Varoqui wrote me telling about a SCSI Start/Stop 
Handler you are writing.
I'd like to know when you think to release it.

Thank you

    Nicola 

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

a question

[Hari Gadi]

Hi,
I have a small question regarding the use of NETLINK sockets. I have a
small character driver and  an application which to I want to send some
data using NETLINK sockets.

The questions I have are:
Can I use NETLINK functions from any character driver and to any
process?
Below is the skeleton of my application.

(1)
Below is the skeleton of my application program (ioctl.c) which tries to
read data sent by
char_dev driver.

int kernelsock_open(void)
{

  int kernelfd; 
  kernelfd = open("/dev/char_dev",0);
  length=read(kernelfd,(char *)buffer,(sizeof(struct buffermsg);
}

(2) 
And the skeleton of my driver program is as shown below. (trying to add
netlink support to
chardev.c)

/* chardev.c 
 * 
 * Create an input/output character device
 */

/* Copyright (C) 1998-99 by Ori Pomerantz */

int init_module()
{
  int ret_val;

  /* Register the character device (atleast try) */
  ret_val = register_chrdev(MAJOR_NUM, 
                                 DEVICE_NAME,
                                 &Fops);  
  sendnetlinkpacket();

  return 0;
}

void sendnetlinkpacket(void)
{

  struct  buffermsg *s;
  struct sk_buff *tmpskb;  
  tmpskb=alloc_skb((sizeof(struct buffermsg)),GFP_ATOMIC);
  if(tmpskb)
{
  skb_put(tmpskb,sizeof(struct buffermsg));
  s=(struct buffermsg *)tmpskb->data;
  s->version= 1;
  s->type=SADBM_ACQUIRE;
  
  if(sadb_netlink_post(NETLINK_FIREWALL,tmpskb))
  kfree_skb(tmpskb);
}
}

int sadb_netlink_post(int unit,struct sk_buff *skb)
{
  struct socket *socket1;  
  struct sock *sk=netlink_kernel_create(NETLINK_FIREWALL,NULL);
  socket1=  sk->socket;
  if(socket1)
{
  netlink_broadcast(socket1->sk,skb,0,~0,GFP_ATOMIC);
  return 0;
}
  return 1;

}/*static int sabd_netlink_post()*/



static int device_open(struct inode *inode, 
                       struct file *file)
{
  Device_Open++;

  /* Initialize the message */
  Message_Ptr = Message;

  MOD_INC_USE_COUNT;
  return SUCCESS;
}
     
static int device_release(struct inode *inode, 
                          struct file *file)
{ 
  /* We're now ready for our next caller */
  Device_Open --;

  MOD_DEC_USE_COUNT;

#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,2,0)
  return 0;
#endif
}



static ssize_t device_read(
    struct file *file,
    char *buffer, /* The buffer to fill with the data */   
    size_t length,     /* The length of the buffer */
    loff_t *offset) /* offset to the file */
{
  /* Number of bytes actually written to the buffer */
  int bytes_read = 0;


  /* If we're at the end of the message, return 0 
   * (which signifies end of file) */
  if (*Message_Ptr == 0)
    return 0;

  /* Actually put the data into the buffer */
  while (length && *Message_Ptr)  {    
    put_user(*(Message_Ptr++), buffer++);
    length --;
    bytes_read ++;
  }
  return bytes_read;
}


static ssize_t device_write(struct file *file,
                            const char *buffer,
                            size_t length,
                            loff_t *offset)
{
  int i;
  for(i=0; i<length && i<BUF_LEN; i++)
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,2,0)
    get_user(Message[i], buffer+i);
#else
    Message[i] = get_user(buffer+i);
#endif  

  Message_Ptr = Message; 
  return i;
}


int device_ioctl(
    struct inode *inode,
    struct file *file,
    unsigned int ioctl_num,/* The number of the ioctl */
    unsigned long ioctl_param) /* The parameter to it */
{
  int i;
  char *temp;
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,2,0)
  char ch;
#endif

  /* Switch according to the ioctl called */
  switch (ioctl_num) {
    case IOCTL_SET_MSG:
       temp = (char *) ioctl_param; 
   
      get_user(ch, temp);
      for (i=0; ch && i<BUF_LEN; i++, temp++)
        get_user(ch, temp);
      device_write(file, (char *) ioctl_param, i, 0);
      break;

    case IOCTL_GET_MSG:
      /* Give the current message to the calling 
       * process - the parameter we got is a pointer, 
       * fill it. */
      i = device_read(file, (char *) ioctl_param, 99, 0); 
      put_user('\0', (char *) ioctl_param+i);
      break;

    case IOCTL_GET_NTH_BYTE:     
      return Message[ioctl_param];
      break;
  }

  return SUCCESS;
}


struct file_operations Fops = {
  NULL,   /* seek */
  device_read, 
  device_write,
  NULL,   /* readdir */
  NULL,   /* select */
  device_ioctl,   /* ioctl */
  NULL,   /* mmap */
  device_open,
#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,2,0)
  NULL,  /* flush */
#endif
  device_release  /* a.k.a. close */
};

/* Cleanup - unregister the appropriate file from /proc */
void cleanup_module()
{
  int ret;

  /* Unregister the device */
  ret = unregister_chrdev(MAJOR_NUM, DEVICE_NAME);
 
  /* If there's an error, report it */ 
  if (ret < 0)
    printk("Error in module_unregister_chrdev: %d\n", ret);
}

Re: a question

[P. Barrette]

I think you need to put it in the main directory, ie. just drop it on the
"Macintosh HD" hard drive icon.  It should be in the same area as your
system folder.  Re partitions, hda5 should be right, I don't know about
the ata stuff though.

--------
Paul Barrette
Ph.D. Candidate Classics (Latin Literature)
System Administrator
McMaster University

"Oppositaque ad os manu nescio quid taetrum 
exsibilavit, quod postea Graecum esse affirmabat."
                                      --Petronius

On Sat, 19 Jun 1999, Akiko Tanaka wrote:

> 
> I've been tryint to install Linux (downloaded from 
> mklinux.apple.com/pub site) on my Mac (power Mac 5400), but it seems 
> like I don't know the basics that the READ ME's and your FAQ's don't 
> explain, and am having trouble for hours.  The problem I have is the 
> "bootstrap cannot find configuration file" message that I get, which 
> seems to be a common problem.  But, I think my problem is that I Don't 
> know how to do "4) Place the "mach_servers" folder at the top level 
> (ie. not on the desktop)
>    of a suitable volume on your Mac."  Am I supposed to put 
> "mach_server" folder inside the patrition for MacHFS when I look at 
> through the pdisk?  How do you do that?  I just don't know how to put 
> things above the desktop level.
> 
> Also, if I manage to put it where it's supposed to go and edit the 
> line in lilo.conf, am I supposed to just put rootdev=/dev/hda (or 
> ata0.0) or whatever, or supposed to write 
> /dev/boot_device/mach_servers/bootstrap.conf, which comes up in the 
> error message when I try to boot it?  Also, it seems that I have to 
> specify a patition when I do this.  How do I do that?  If the 
> patrition # in pdisk is 5, do I put rootdev=/dev/hda/5 or hda5? or 
> what?  If it's ata0.0, does it become ata0.5 or ata0.0/5 or some other 
> kind of way?
> 
> Please Help!!
> 
> Akiko Tanaka
> tanak002@gold.tc.umn.edu

> 


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

a question

[Akiko Tanaka]

I've been tryint to install Linux (downloaded from 
mklinux.apple.com/pub site) on my Mac (power Mac 5400), but it seems 
like I don't know the basics that the READ ME's and your FAQ's don't 
explain, and am having trouble for hours.  The problem I have is the 
"bootstrap cannot find configuration file" message that I get, which 
seems to be a common problem.  But, I think my problem is that I Don't 
know how to do "4) Place the "mach_servers" folder at the top level 
(ie. not on the desktop)
   of a suitable volume on your Mac."  Am I supposed to put 
"mach_server" folder inside the patrition for MacHFS when I look at 
through the pdisk?  How do you do that?  I just don't know how to put 
things above the desktop level.

Also, if I manage to put it where it's supposed to go and edit the 
line in lilo.conf, am I supposed to just put rootdev=/dev/hda (or 
ata0.0) or whatever, or supposed to write 
/dev/boot_device/mach_servers/bootstrap.conf, which comes up in the 
error message when I try to boot it?  Also, it seems that I have to 
specify a patition when I do this.  How do I do that?  If the 
patrition # in pdisk is 5, do I put rootdev=/dev/hda/5 or hda5? or 
what?  If it's ata0.0, does it become ata0.5 or ata0.0/5 or some other 
kind of way?

Please Help!!

Akiko Tanaka
tanak002@gold.tc.umn.edu

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]