HP Model 755/125cL HP-UX DMI 2.0 Developer's Guide: HP-UX/HP 9000 Computers, - Page 52

Machine List Protection, User Name Check on HP-UX Clients

Page 52 highlights

Management Interface Concepts MI Security Machine List Protection This type of security uses knowledge of the DCE/RPC binding to determine the machine making the DMI call. It then checks the machine name against an internal table of allowed machine names. If the machine name or IP address matches, access to attribute values is granted. The system administrator grants access rights to machines by editing the file /var/dmi/dmiMachines. The format of this file is any valid hostname or complete internet address, one entry per line. The SP detects changes to this file when a client gets or sets an attribute value. Any machine on the network may view the data description (attribute names) of the MIF database. The following calls are restricted by the machine list protection. • DmiGetAttribute() / DmiSetAttribute() • DmiGetMultiple() / DmiSetMultiple() • DmiAddRow() / DmiDeleteRow() • DmiAddGroup() / DmiDeleteGroup() • DmiAddComponent() / DmiDeleteComponent() • DmiAddLanguage() / DmiDeleteLanguage() User Name Check on HP-UX Clients This type of security verifies that a client making a DMI call is the root user. This keeps unknown users from accessing the MIF database. Only the following calls are restricted by the user name check. • DmiGetAttribute() / DmiSetAttribute() • DmiGetMultiple() / DmiSetMultiple() • DmiAddRow() / DmiDeleteRow() • DmiAddGroup() / DmiDeleteGroup() • DmiAddComponent() / DmiDeleteComponent() • DmiAddLanguage() / DmiDeleteLanguage() 52 Chapter 7

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134

52
Chapter 7
Management Interface Concepts
MI Security
Machine List Protection
This type of security uses knowledge of the DCE/RPC binding to
determine the machine making the DMI call. It then checks the
machine name against an internal table of allowed machine names. If
the machine name or IP address matches, access to attribute values is
granted.
The system administrator grants access rights to machines by editing
the file /var/dmi/dmiMachines. The format of this file is any valid
hostname or complete internet address, one entry per line. The SP
detects changes to this file when a client gets or sets an attribute value.
Any machine on the network may view the data description (attribute
names) of the MIF database. The following calls are restricted by the
machine list protection.
DmiGetAttribute() / DmiSetAttribute()
DmiGetMultiple() / DmiSetMultiple()
DmiAddRow() / DmiDeleteRow()
DmiAddGroup() / DmiDeleteGroup()
DmiAddComponent() / DmiDeleteComponent()
DmiAddLanguage() / DmiDeleteLanguage()
User Name Check on HP-UX Clients
This type of security verifies that a client making a DMI call is the root
user. This keeps unknown users from accessing the MIF database. Only
the following calls are restricted by the user name check.
DmiGetAttribute() / DmiSetAttribute()
DmiGetMultiple() / DmiSetMultiple()
DmiAddRow() / DmiDeleteRow()
DmiAddGroup() / DmiDeleteGroup()
DmiAddComponent() / DmiDeleteComponent()
DmiAddLanguage() / DmiDeleteLanguage()