| etsysSshEnabled |
.1.3.6.1.4.1.5624.1.2.26.1.1.1 |
|
Controls the operation of the Secure Shell server task
on the embedded system. When enabled, the SSH server
will accept connection requests and create a secure
transport layer on which to transmit system configuration
data.
|
| etsysSshEventLogFilter |
.1.3.6.1.4.1.5624.1.2.26.1.1.2 |
|
Specifies the filter for event log messages. Valid
values are information, warning, and error.
The values are defined as follows:
none (1) Pass no messages. This is effectively
a disable condition for Event Logging.
information (2) Pass Informational Level, Warning Level
and Error Level messages.
warning (3) Pass Warning Level and Error Level
messages.
error (4) Pass Error Level messages only.
|
| etsysSshMaxConnections |
.1.3.6.1.4.1.5624.1.2.26.1.1.3 |
|
Specifies the maximum number of simultaneous connections
that the target system supports. This is an
implementation restriction.
|
| etsysSshNumConnections |
.1.3.6.1.4.1.5624.1.2.26.1.1.4 |
|
Specifies the maximum number of simultaneous connections
that the server will currently allow. This value must be
less than or equal to etsysSshMaxConnections.
|
| etsysSshCiphers |
.1.3.6.1.4.1.5624.1.2.26.1.3.1 |
|
Specifies the ciphers to use for encrypting the session.
Current enumerated types, DES, 3DES, Blowfish, Arcfour,
Twofish, and CAST128 are supported. Special values to
this option are any, anystd, that allows only standard
(see below) ciphers, and anycipher that allows either any
available cipher or excludes non-encrypting cipher mode
none but allows all others. anystdcipher is the same as
above, but includes only those ciphers mentioned in the
IETF-SecSH-draft (excluding 'none').
|
| etsysSshMACs |
.1.3.6.1.4.1.5624.1.2.26.1.3.2 |
|
Specifies the MAC (Message Authentication Code) algorithm
to use for data integrity verification. Currently enumerated
types, hmacSha1, hmacSha1Dash96, hmacMd5, hmacMd5Dash96,
hmacRipemd160, and hmacRipemd160Dash96 are supported, of
which hmacSha1, hmacSha1Dash96, hmacMd5, and hmacMd5Dash96 are
included in all distributions. Special values to this option
are anyStdMac, that allows only standard (see below) MACs,
and anyMac that allows either any available MAC or excludes
none but allows all others. AnyStdMac is the same as above,
but includes only those MACs mentioned in the IETF-SecSH-draft
(excluding none).
|
| etsysSshRekeyIntervalSeconds |
.1.3.6.1.4.1.5624.1.2.26.1.3.3 |
|
Specifies the number of seconds after which the key
exchange is done again. A value of 0 (zero) turns re-key
requests off. This does not prevent the client from
requesting re-keys. Note that not all clients support
this function.
|
| etsysSshRandomSeed |
.1.3.6.1.4.1.5624.1.2.26.1.3.4 |
|
Specifies optional additional entropy information that
will be merged with the seed for the random number
generator.
|
| etsysSshLoginGraceTime |
.1.3.6.1.4.1.5624.1.2.26.1.4.1 |
|
The server disconnects after this many seconds if the user
has not successfully been authenticated and logged in. The
range limit is from 1 second to 1 hour.
|
| etsysSshIdleTimeout |
.1.3.6.1.4.1.5624.1.2.26.1.4.2 |
|
Specifies the maximum number of minutes before a user is
disconnected due to lack of activity.
A value of zero means that there is no idle timeout.
|
| etsysSshBannerMessage |
.1.3.6.1.4.1.5624.1.2.26.1.4.3 |
|
Banner message that is displayed at the client before
the login.
|
| etsysSshGenerateHostKeys |
.1.3.6.1.4.1.5624.1.2.26.1.5.1 |
|
Causes the host to generate a new private/public host
key pair, using the cipher algorithm currently selected
in etsysSshAdminKeyType. Note that this can be compute
intensive on many platforms.
The meaning of the values are as follows:
notInitiated (1) On a write, this is a no-operation,
on a read, it indicates that no key
material generation operation has
ever been initiated, at least since
the last reset to factory defaults
initialization of the managed entity.
No key material exists.
completed (2) On a write, this is a no-operation,
on a read, this indicates that a key
pair has been successfully generated.
failed (3) On a write, this is a no-operation,
on a read, it indicates that the key
generation operation has failed.
generate (4) On a write, this causes the managed
entity to generate a new key pair,
on a read, it indicates that the
managed entity is still working on
creating the new keys.
completedPending (5)
On a write, this is a no-operation,
on a read, this indicates that a key
pair has been successfully generated
but its use is pending due to another
required operation, such as a reboot.
|
| etsysSshPublicHostKey |
.1.3.6.1.4.1.5624.1.2.26.1.5.2 |
|
The host's public key, of type etsysSshOperKeyType.
|
| etsysSshAdminKeyType |
.1.3.6.1.4.1.5624.1.2.26.1.5.3 |
|
Determines the type of the key pair to be (re)created
on the next key (re)creation operation. The
etsysSshOperKeyType object returns the type of
key that is currently being used by the SSH server.
|
| etsysSshOperKeyType |
.1.3.6.1.4.1.5624.1.2.26.1.5.4 |
|
Indicates the type of the key pair currently in
effect on the managed entity. The value of the
etsysSshAdminKeyType object is copied to the
etsysSshOperKeyType object upon successful completion
of the (re)creation of a key pair. A value of none
indicates that due to the failure of the initial key
pair generation there is no active key pair.
|
| etsysSshPasswordGuesses |
.1.3.6.1.4.1.5624.1.2.26.1.6.1 |
|
Specifies the number of tries that the user has when
attempting to authenticate using password authentication.
|
| etsysSshAllowedAuthentications |
.1.3.6.1.4.1.5624.1.2.26.1.6.2 |
|
This specifies the authentications methods that are
allowed. This is an enumerated list currently consisting
of the following types: password, publickey. Each specifies
an authentication method.
With RequiredAuthentications, the administrator can
force users to complete several authentications before
they are considered authenticated.
|
| etsysSshRequiredAuthentications |
.1.3.6.1.4.1.5624.1.2.26.1.6.3 |
|
Related to AllowedAuthentications, this is used to
specify what authentication methods the users must
complete before continuing. If this value is left
zero, it does not mean that no authentications are
required. It means that the client can authenticate
itself with any of the authentications given in
AllowedAuthentications. This parameter has no default.
Note: This parameter has to be a subset for
AllowedAuthentications. Otherwise, the server denies
connection every time.
|
