| etsysTlsEnabled |
.1.3.6.1.4.1.5624.1.2.30.1.1.1 |
|
Controls the operation of the Transport Layer Security
server task on the embedded system. When enabled, the
TLS server will accept connection requests and create
a secure transport layer on which to transmit target
system configuration data.
|
| etsysTlsNumSoftConnects |
.1.3.6.1.4.1.5624.1.2.30.1.1.2 |
|
The soft limit for the maximum number of concurrent connections.
If a new connection is initiated and it would exceed the soft
limit, a '530 Service Unavailable' error will be reported to the
client. Managed entities are free to enforce implementation
specific limits on the upper limit of this object.
|
| etsysTlsNumHardConnects |
.1.3.6.1.4.1.5624.1.2.30.1.1.3 |
|
The hard limit for the maximum number of concurrent connections.
If a new connection is initiated and it would exceed the hard
limit, the connection is closed unconditionally. Managed
entities are free to enforce implementation specific limits on
the upper limit of this object.
|
| etsysTlsMaxHardConnects |
.1.3.6.1.4.1.5624.1.2.30.1.1.4 |
|
The maximum number of concurrent connections a platform supports.
Allows managed entities to enforce implementation specific limits on
the upper limit of the etsysTlsNumHardConnects object.
|
| etsysTlsKeepOpenTimeout |
.1.3.6.1.4.1.5624.1.2.30.1.2.1 |
|
How long in time a 'Keep-Alive' connection is kept open if new
requests are not seen. The timeout is given in seconds.
|
| etsysTlsHttpsPort |
.1.3.6.1.4.1.5624.1.2.30.1.2.2 |
|
The TCP port that the HTTPs server will listen to.
|
| etsysTlsGenerateKeys |
.1.3.6.1.4.1.5624.1.2.30.1.3.1 |
|
Causes the host to generate a new key pair using the
cipher algorithm currently selected in etsysTlsAdminKeyType.
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.
|
| etsysTlsAdminKeyType |
.1.3.6.1.4.1.5624.1.2.30.1.3.2 |
|
Determines the type of the key to be (re)created
on the next key (re)creation operation. The
etsysTlsOperKeyType object returns the type of
key that is currently being used by the TLS server.
|
| etsysTlsOperKeyType |
.1.3.6.1.4.1.5624.1.2.30.1.3.3 |
|
Indicates the type of the key pair currently in
effect on the managed entity. The value of the
etsysTlsAdminKeyType object is copied to the
etsysTlsOperKeyType object upon successful completion
of the (re)creation of a key pair.
|
| etsysTlsSignatureType |
.1.3.6.1.4.1.5624.1.2.30.1.3.4 |
|
Denotes the signature method that is used for
authenticating the exchange of keys.
DSS (Digital Signature Standard)
DSA (Digital Signature Algorithm, DSS compliant)
RSA (Rivest, Shamir and Adelman)
Sha (Secure Hash Algorithm)
Md5 (Message Digest 5)
dhAnon (1) - Anonymous Diffie Hellmen, no signatures
dsaSha1 (2) - DSS , Sha-1 Hash
dsaSha (3) - DSS signatures, Sha Hash
rsaSha1 (4) - RSA signatures, Sha-1 Hash
rsaMd2 (5) - RSA signatures, Md2 Hash
rsaMd5 (6) - RSA signatures, Md5 Hash
|
