2.6. Maintenance
It ought to be possible to disable part or all of the access control model enforcement procedures without deleting any access control rules.¶
| RFC 8341 | NACM | March 2018 |
| Bierman & Bjorklund | Standards Track | [Page] |
The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model.¶
This document obsoletes RFC 6536.¶
This is an Internet Standards Track document.¶
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.¶
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8341.¶
Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶
The Network Configuration Protocol (NETCONF) and the RESTCONF protocol do not provide any standard mechanisms to restrict the protocol operations and content that each user is authorized to access.¶
There is a need for interoperable management of the controlled access to administrator-selected portions of the available NETCONF or RESTCONF content within a particular server.¶
This document addresses access control mechanisms for the Operations and Content layers of NETCONF, as defined in [RFC6241]; and RESTCONF, as defined in [RFC8040]. It contains three main sections:¶
YANG version 1.1 [RFC7950] adds two new constructs that need special access control handling. The "action" statement is similar to the "rpc" statement, except that it is located within a data node. The "notification" statement can also be located within a data node.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
The following terms are defined in [RFC8342] and are not redefined here:¶
The following terms are defined in [RFC6241] and are not redefined here:¶
The following terms are defined in [RFC7950] and are not redefined here:¶
The following terms are defined in [RFC8040] and are not redefined here:¶
The following term is defined in [RFC7230] and is not redefined here:¶
The following terms are used throughout this document:¶
The NACM procedures and data model have been updated to support new data modeling capabilities in version 1.1 of the YANG data modeling language. The "action" and "notification" statements can be used within data nodes to define data-model-specific operations and notifications.¶
An important use case for these new YANG statements is the increased access control granularity that can be achieved over top-level "rpc" and "notification" statements. The new "action" and "notification" statements are used within data nodes, and access to the action or notification can be restricted to specific instances of these data nodes.¶
Support for the RESTCONF protocol has been added. The RESTCONF operations are similar to the NETCONF operations, so a simple mapping to the existing NACM procedures and data model is possible.¶
The data node access behavior for path matches has been clarified to also include matching descendant nodes of the specified path.¶
The <edit-config> operation access rights behavior has been clarified to indicate that write access is not required for data nodes that are implicitly modified through side effects (such as the evaluation of YANG when-stmts, or data nodes implicitly deleted when creating a data node under a different branch under a YANG choice-stmt).¶
The Security Considerations section has been updated to comply with the "YANG module security guidelines" [YANG-SEC]. Note that the YANG module in this document does not define any RPC operations.¶
This section documents the design objectives for the NETCONF access control model presented in Section 3.¶
NETCONF allows server implementers to add new custom protocol operations, and the YANG data modeling language supports this feature. These operations can be defined in standard or proprietary YANG modules.¶
It is not possible to design an ACM for NETCONF that only focuses on a static set of standard protocol operations defined by NETCONF itself, like some other protocols. Since few assumptions can be made about an arbitrary protocol operation, the NETCONF architectural server components need to be protected at three conceptual control points.¶
These access control points, described in Section 2.1, are as follows:¶
+-------------+ +-------------+ client | protocol | | data node | request --> | operation | -------------> | access | | allowed? | datastore | allowed? | +-------------+ or state +-------------+ data access +----------------+ | notification | event --> | allowed? | +----------------+¶
There is concern that a complicated ACM will not be widely deployed because it is too hard to use. Configuration of the access control system needs to be as simple as possible. Simple and common tasks need to be easy to configure and require little expertise or domain-specific knowledge. Complex tasks are possible using additional mechanisms that may require additional expertise.¶
A single set of access control rules ought to be able to control all types of NETCONF protocol operation invocation, all datastore access, and all notification events.¶
Access control ought to be defined with a small and familiar set of permissions, while still allowing full control of datastore access.¶
NETCONF uses a Remote Procedure Call (RPC) model and an extensible set of protocol operations. Access control for any possible protocol operation is necessary.¶
It is necessary to control access to specific nodes and subtrees within the datastore, regardless of which protocol operation -- standard or proprietary -- was used to access the datastore.¶
It is necessary that access control rules for a single user or a configurable group of users can be configured.¶
The ACM needs to support the concept of administrative groups, to support the well-established distinction between a root account and other types of less-privileged conceptual user accounts. These groups need to be configurable by the administrator.¶
It is necessary that the user-to-group mapping can be delegated to a central server, such as a RADIUS server [RFC2865] [RFC5607]. Since authentication is performed by the transport layer and RADIUS performs authentication and service authorization at the same time, the underlying transport protocol needs to be able to report a set of group names associated with the user to the server. It is necessary that the administrator can disable the usage of these group names within the ACM.¶
It ought to be possible to disable part or all of the access control model enforcement procedures without deleting any access control rules.¶
Suitable configuration and monitoring mechanisms are needed to allow an administrator to easily manage all aspects of the ACM's behavior. A standard data model, suitable for use with the <edit-config> protocol operation, needs to be available for this purpose.¶
Access control rules to restrict access operations on specific subtrees within the configuration datastore need to be supported.¶
One of the most important aspects of the data model documentation, and one of the biggest concerns during deployment, is the identification of security-sensitive content. This applies to protocol operations in NETCONF, not just data and notifications.¶
It is mandatory for security-sensitive objects to be documented in the Security Considerations section of an RFC. This is nice, but it is not good enough, for the following reasons:¶
This documentation-only approach forces administrators to study the RFC and determine if there are any potential security risks introduced by a new data model.¶
If any security risks are identified, then the administrator must study some more RFC text and determine how to mitigate the security risk(s).¶
The ACM on each server must be configured to mitigate the security risks, e.g., require privileged access to read or write the specific data identified in the Security Considerations section.¶
If the ACM is not preconfigured, then there will be a time window of vulnerability after the new data model is loaded and before the new access control rules for that data model are configured, enabled, and debugged.¶
Often, the administrator just wants to disable default access to the secure content so that no inadvertent or malicious changes can be made to the server. This allows the default rules to be more lenient, without significantly increasing the security risk.¶
A data model designer needs to be able to use machine-readable statements to identify content that needs to be protected by default. This will allow client and server tools to automatically identify data-model-specific security risks, by denying access to sensitive data unless the user is explicitly authorized to perform the requested access operation.¶
This section provides a high-level overview of the access control model structure. It describes the NETCONF protocol message processing model and the conceptual access control requirements within that model.¶
The NACM data model provides the following features:¶
Independent control of RPC, action, data, and notification access is provided.¶
The concept of an emergency recovery session is supported, but configuration of the server for this purpose is beyond the scope of this document. An emergency recovery session will bypass all access control enforcement, in order to allow it to initialize or repair the NACM configuration.¶
A simple and familiar set of datastore permissions is used.¶
Support for YANG security tagging (e.g., a "nacm:default-deny-write" statement) allows default security modes to automatically exclude sensitive data.¶
Separate default access modes for read, write, and execute permissions are provided.¶
Access control rules are applied to configurable groups of users.¶
The access control enforcement procedures can be disabled during operation, without deleting any access control rules, in order to debug operational problems.¶
The number of denied protocol operation requests and denied datastore write requests can be monitored by the client.¶
Simple unconstrained YANG instance-identifiers are used to configure access control rules for specific data nodes.¶
NETCONF [RFC6241] and RESTCONF [RFC8040] are used for network management purposes within this document.¶
The YANG data modeling language [RFC7950] is used to define the data models for use with NETCONF or RESTCONF. YANG is also used to define the data model in this document.¶
The following diagram shows the conceptual message flow model, including the points at which access control is applied during NETCONF message processing.¶
RESTCONF operations are mapped to the access control model based on the HTTP method and resource class used in the operation. For example, a POST method on a data resource is considered "write data node" access, but a POST method on an operation resource is considered "operation" access.¶
The new "pre-read data node acc. ctl" boxes in the diagram below refer to group read access as it relates to data node ancestors of an action or notification. As an example, if an action is defined as /interfaces/interface/reset-interface, the group must be authorized to (1) read /interfaces and /interfaces/interface and (2) execute on /interfaces/interface/reset-interface.¶
+-------------------------+ | session | | (username) | +-------------------------+ | ^ V | +--------------+ +---------------+ | message | | message | | dispatcher | | generator | +--------------+ +---------------+ | | ^ ^ | V | | | +=============+ | | | | pre-read | | | | | data node | | | | | acc. ctl | | | | +=============+ | | | | | | V V | | +===========+ +-------------+ +----------------+ | operation |---> | reply | | <notification> | | acc. ctl | | generator | | generator | +===========+ +-------------+ +----------------+ | ^ ^ ^ V +------+ | | +-----------+ | +=============+ +================+ | operation | | | read | | <notification> | | processor |-+ | data node | | access ctl | | | | acc. ctl | | | +-----------+ +=============+ +================+ | | ^ ^ ^ V +----------------+ | | | +===========+ | | | +============+ | write | | | | | pre-read | | data node | | | | | data node | | acc. ctl | -----------+ | | | | acc. ctl | +===========+ | | | | +============+ | | | | | ^ V V V | | | +---------------+ +-------------------+ | configuration | ---> | server | | datastore | | instrumentation | | | <--- | | +---------------+ +-------------------+¶
The following high-level sequence of conceptual processing steps is executed for each received <rpc> message, if access control enforcement is enabled:¶
For each active session, access control is applied individually to all <rpc> messages (except <close-session>) received by the server, unless the session is identified as a recovery session.¶
If the <action> operation defined in [RFC7950] is invoked, then read access is required for all instances in the hierarchy of data nodes that identifies the specific action in the datastore, and execute access is required for the action node. If the user is not authorized to read all the specified data nodes and execute the action, then the request is rejected with an "access-denied" error.¶
Otherwise, if the user is not authorized to execute the specified protocol operation, then the request is rejected with an "access-denied" error.¶
If a datastore is accessed by the protocol operation, then the server checks to see if the client is authorized to access the nodes in the datastore. If the user is not authorized to perform the requested access operation on the requested data, then the request is rejected with an "access-denied" error.¶
The following sequence of conceptual processing steps is executed for each generated notification event, if access control enforcement is enabled:¶
Server instrumentation generates a notification for a particular subscription.¶
If the "notification" statement is specified within a data subtree, as specified in [RFC7950], then read access is required for all instances in the hierarchy of data nodes that identifies the specific notification in the datastore, and read access is required for the notification node. If the user is not authorized to read all the specified data nodes and the notification node, then the notification is dropped for that subscription.¶
If the "notification" statement is a top-level statement, the notification access control enforcer checks the notification event type, and if it is one that the user is not authorized to read, then the notification is dropped for that subscription.¶
The same access control rules apply to all datastores that support the NACM -- for example, the candidate configuration datastore or the running configuration datastore.¶
All conventional configuration datastores and the operational state datastore are controlled by the NACM. Local files, remote files, or datastores accessed via the <url> parameter are not controlled by the NACM.¶
It is possible that new datastores will be defined over time for use with NETCONF. The NACM MAY be applied to other datastores that have similar access rights as defined in the NACM. To apply the NACM to a new datastore, the new datastore specification needs to define how it maps to the NACM CRUDX (Create, Read, Update, Delete, eXec) access rights. It is possible that only a subset of the NACM access rights would be applicable. For example, only retrieval access control would be needed for a read-only datastore. Operations and access rights not supported by the NACM CRUDX model are outside the scope of this document. A datastore does not need to use the NACM, e.g., the datastore specification defines something else or does not use access control.¶
A small set of hard-wired datastore access rights is needed to control access to all possible protocol operations, including vendor extensions to the standard protocol operation set.¶
The CRUDX model can support all protocol operations:¶
The RESTCONF protocol utilizes HTTP methods to perform datastore operations, similar to NETCONF. The NACM procedures were originally written for NETCONF protocol operations, so the RESTCONF methods are mapped to NETCONF operations for the purpose of access control processing. The enforcement procedures described within this document apply to both protocols unless explicitly stated otherwise.¶
The request URI needs to be considered when processing RESTCONF requests on data resources:¶
For HEAD and GET requests, any data nodes that are ancestor nodes of the target resource are considered to be part of the retrieval request for access control purposes.¶
For PUT, PATCH, and DELETE requests, any data nodes that are ancestor nodes of the target resource are not considered to be part of the edit request for access control purposes. The access operation for these nodes is considered to be "none". The edit begins at the target resource.¶
For POST requests on data resources, any data nodes that are specified in the request URI, including the target resource, are not considered to be part of the edit request for access control purposes. The access operation for these nodes is considered to be "none". The edit begins at a child node of the target resource, specified in the message body.¶
Not all RESTCONF methods are subject to access control. The following table specifies how each method is mapped to NETCONF protocol operations. The value "none" indicates that the NACM is not applied at all to the specific RESTCONF method.¶
| Method | Resource class | NETCONF operation | Access operation |
|---|---|---|---|
| OPTIONS | all | none | none |
| HEAD | all | <get>, <get-config> | read |
| GET | all | <get>, <get-config> | read |
| POST | datastore, data | <edit-config> | create |
| POST | operation | specified operation | execute |
| PUT | data | <edit-config> | create, update |
| PUT | datastore | <copy-config> | update |
| PATCH | data, datastore | <edit-config> | update |
| DELETE | data | <edit-config> | delete |
The NACM access rights are not directly coupled to the <get> and <get-config> protocol operations but apply to all <rpc> operations that would result in a "read" access operation to the target datastore. This section describes how these access rights apply to the specific access operations supported by the <get> and <get-config> protocol operations.¶
Data nodes to which the client does not have read access are silently omitted, along with any descendants, from the <rpc-reply> message. This is done to allow NETCONF filters for <get> and <get-config> to function properly, instead of causing an "access-denied" error because the filter criteria would otherwise include unauthorized read access to some data nodes. For NETCONF filtering purposes, the selection criteria are applied to the subset of nodes that the user is authorized to read, not the entire datastore.¶
The NACM access rights are not directly coupled to the <edit-config> "operation" attribute, although they are similar. Instead, a NACM access right applies to all protocol operations that would result in a particular access operation to the target datastore. This section describes how these access rights apply to the specific access operations supported by the <edit-config> protocol operation.¶
If the effective access operation is "none" (i.e., default-operation="none") for a particular data node, then no access control is applied to that data node. This is required to allow access to a subtree within a larger data structure. For example, a user may be authorized to create a new "/interfaces/interface" list entry but not be authorized to create or delete its parent container ("/interfaces"). If the "/interfaces" container already exists in the target datastore, then the effective operation will be "none" for the "/interfaces" node if an "/interfaces/interface" list entry is edited.¶
If the protocol operation would result in the creation of a datastore node and the user does not have "create" access permission for that node, the protocol operation is rejected with an "access-denied" error.¶
If the protocol operation would result in the deletion of a datastore node and the user does not have "delete" access permission for that node, the protocol operation is rejected with an "access-denied" error.¶
If the protocol operation would result in the modification of a datastore node and the user does not have "update" access permission for that node, the protocol operation is rejected with an "access-denied" error.¶
A "merge" or "replace" <edit-config> operation may include data nodes that do not alter portions of the existing datastore. For example, a container or list node may be present for naming purposes but does not actually alter the corresponding datastore node. These unaltered data nodes are ignored by the server and do not require any access rights by the client.¶
A "merge" <edit-config> operation may include data nodes but not include particular child data nodes that are present in the datastore. These missing data nodes within the scope of a "merge" <edit-config> operation are ignored by the server and do not require any access rights by the client.¶
The contents of specific restricted datastore nodes MUST NOT be exposed in any <rpc-error> elements within the reply.¶
An <edit-config> operation may cause data nodes to be implicitly created or deleted as an implicit side effect of a requested operation. For example, a YANG when-stmt expression may evaluate to a different result, causing data nodes to be deleted, or created with default values; or if a data node is created under one branch of a YANG choice-stmt, then all data nodes under the other branches are¶
implicitly removed. No NACM access rights are required on any data nodes that are implicitly changed as a side effect of another allowed operation.¶
Access control for the <copy-config> protocol operation requires special consideration because the administrator may be replacing the entire target datastore.¶
If the source of the <copy-config> protocol operation is the running configuration datastore and the target is the startup configuration datastore, the client is only required to have permission to execute the <copy-config> protocol operation.¶
Otherwise:¶
If the source of the <copy-config> operation is a datastore, then data nodes to which the client does not have read access are silently omitted.¶
If the target of the <copy-config> operation is a datastore, the client needs access to the modified nodes. Specifically:¶
If the protocol operation would result in the creation of a datastore node and the user does not have "create" access permission for that node, the protocol operation is rejected with an "access-denied" error.¶
If the protocol operation would result in the deletion of a datastore node and the user does not have "delete" access permission for that node, the protocol operation is rejected with an "access-denied" error.¶
If the protocol operation would result in the modification of a datastore node and the user does not have "update" access permission for that node, the protocol operation is rejected with an "access-denied" error.¶
Access to the <delete-config> protocol operation is denied by default. The "exec-default" leaf does not apply to this protocol operation. Access control rules must be explicitly configured to allow invocation by a non-recovery session.¶
The server MUST determine the exact nodes in the running configuration datastore that are actually different and only check "create", "update", and "delete" access permissions for this set of nodes, which could be empty.¶
For example, if a session can read the entire datastore but only change one leaf, that session needs to be able to edit and commit that one leaf.¶
The client is only required to have permission to execute the <discard-changes> protocol operation. No datastore permissions are needed.¶
The <kill-session> operation does not directly alter a datastore. However, it allows one session to disrupt another session that is editing a datastore.¶
Access to the <kill-session> protocol operation is denied by default. The "exec-default" leaf does not apply to this protocol operation. Access control rules must be explicitly configured to allow invocation by a non-recovery session.¶
This section defines the conceptual components related to the access control model.¶
A "user" is the conceptual entity that is associated with the access permissions granted to a particular session. A user is identified by a string that is unique within the server.¶
As described in [RFC6241], the username string is derived from the transport layer during session establishment. If the transport layer cannot authenticate the user, the session is terminated.¶
Access to a specific NETCONF protocol operation is granted to a session. The session is associated with a group (i.e., not with a user).¶
A group is identified by its name. All group names are unique within the server.¶
Access control is applied at the level of groups. A group contains zero or more group members.¶
A group member is identified by a username string.¶
The same user can be a member of multiple groups.¶
The server MAY support a recovery session mechanism, which will bypass all access control enforcement. This is useful for restricting initial access and repairing a broken access control configuration.¶
There are five global controls that are used to help control how access control is enforced.¶
A global "enable-nacm" on/off switch is provided to enable or disable all access control enforcement. When this global switch is set to "true", all requests are checked against the access control rules and only permitted if configured to allow the specific access request. When this global switch is set to "false", all access requests are permitted.¶
An on/off "read-default" switch is provided to enable or disable default access to receive data in replies and notifications. When the "enable-nacm" global switch is set to "true", this global switch is relevant if no matching access control rule is found to explicitly permit or deny read access to the requested datastore data or notification event type.¶
When this global switch is set to "permit" and no matching access control rule is found for the datastore read or notification event requested, access is permitted.¶
When this global switch is set to "deny" and no matching access control rule is found for the datastore read or notification event requested, access is denied. This means that the requested data is not sent to the client. See step 11 in Section 3.4.5 for details.¶
An on/off "write-default" switch is provided to enable or disable default access to alter configuration data. When the "enable-nacm" global switch is set to "true", this global switch is relevant if no matching access control rule is found to explicitly permit or deny write access to the requested datastore data.¶
When this global switch is set to "permit" and no matching access control rule is found for the datastore write requested, access is permitted.¶
When this global switch is set to "deny" and no matching access control rule is found for the datastore write requested, access is denied. See step 12 in Section 3.4.5 for details.¶
An on/off "exec-default" switch is provided to enable or disable default access to execute protocol operations. When the "enable-nacm" global switch is set to "true", this global switch is relevant if no matching access control rule is found to explicitly permit or deny access to the requested NETCONF protocol operation.¶
When this global switch is set to "permit" and no matching access control rule is found for the NETCONF protocol operation requested, access is permitted.¶
When this global switch is set to "deny" and no matching access control rule is found for the NETCONF protocol operation requested, access is denied. See step 12 in Section 3.4.4 and step 13 in Section 3.4.5 for details.¶
When this global switch is set to "true", the group names reported by the transport layer for a session are used together with the locally configured group names to determine the access control rules for the session.¶
When this switch is set to "false", the group names reported by the transport layer are ignored by the NACM.¶
There are four types of rules available in the NACM:¶
There are six separate phases that need to be addressed, four of which are related to the NETCONF message processing model (#(message-processing-model)):¶
Initial operation¶
Session establishment¶
"access-denied" error handling¶
Incoming RPC message validation¶
Data node access validation¶
Outgoing <notification> authorization¶
In addition, the initial startup mode for a NETCONF server, session establishment, and "access-denied" error-handling procedures also need to be considered.¶
The server MUST use the access control rules in effect at the time it starts processing the message. The same access control rules MUST stay in effect for the processing of the entire message.¶
Upon the very first startup of the NETCONF server, the access control configuration will probably not be present. If it isn't, a server MUST NOT allow any write access to any session role except a recovery session.¶
Access rules are enforced any time a request is initiated from a user session. Access control is not enforced for server-initiated access requests, such as the initial load of the running configuration datastore, during bootup.¶
The access control model applies specifically to the well-formed XML content transferred between a client and a server after session establishment has been completed and after the <hello> exchange has been successfully completed.¶
Once session establishment is completed and a user has been authenticated, the transport layer reports the username and a possibly empty set of group names associated with the user to the NETCONF server. The NETCONF server will enforce the access control rules, based on the supplied username, group names, and the configuration data stored on the server.¶
The "access-denied" error-tag is generated when the access control system denies access to either a request to invoke a protocol operation or a request to perform a particular access operation on the configuration datastore.¶
A server MUST NOT include any information the client is not allowed to read in any <error-info> elements within the <rpc-error> response.¶
The diagram below shows the basic conceptual structure of the access control processing model for incoming NETCONF <rpc> messages within a server.¶
After the server validates the <rpc> element and determines the namespace URI and the element name of the protocol operation being requested, the server verifies that the user is authorized to invoke the protocol operation.¶
The server MUST separately authorize every protocol operation by following these steps:¶
For each rule-list entry found, process all rules, in order, until a rule that matches the requested access operation is found. A rule matches if all of the following criteria are met:¶
The rule's "module-name" leaf is "*" or equals the name of the YANG module where the protocol operation is defined.¶
Either (1) the rule does not have a "rule-type" defined or (2) the "rule-type" is "protocol-operation" and the "rpc-name" is "*" or equals the name of the requested protocol operation.¶
The rule's "access-operations" leaf has the "exec" bit set or has the special value "*".¶
If a matching rule is found, then the "action" leaf is checked. If it is equal to "permit", then the protocol operation is permitted; otherwise, it is denied.¶
At this point, no matching rule was found in any rule-list entry.¶
If the requested protocol operation is defined in a YANG module advertised in the server capabilities and the "rpc" statement contains a "nacm:default-deny-all" statement, then the protocol operation is denied.¶
If the requested protocol operation is the NETCONF <kill-session> or <delete-config>, then the protocol operation is denied.¶
If the "exec-default" leaf is set to "permit", then permit the protocol operation; otherwise, deny the request.¶
If the user is not authorized to invoke the protocol operation, then an <rpc-error> is generated with the following information:¶
<error-path xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"> /nc:rpc/nc:edit-config </error-path>¶
If a datastore is accessed, either directly or as a side effect of the protocol operation, then the server MUST intercept the access operation and make sure that the user is authorized to perform the requested access operation on the specified data, as defined in Section 3.4.5.¶
If (1) a data node within a datastore is accessed or (2) an action or notification is tied to a data node, then the server MUST ensure that the user is authorized to perform the requested "read", "create", "update", "delete", or "execute" access operation on the specified data node.¶
If an action is requested to be executed, the server MUST ensure that the user is authorized to perform the "execute" access operation on the requested action.¶
If a notification tied to a data node is generated, the server MUST ensure that the user is authorized to perform the "read" access operation on the requested notification.¶
The data node access request is authorized by following these steps:¶
For each rule-list entry found, process all rules, in order, until a rule that matches the requested access operation is found. A rule matches if all of the following criteria are met:¶
The rule's "module-name" leaf is "*" or equals the name of the YANG module where the requested data node is defined.¶
Either (1) the rule does not have a "rule-type" defined or (2) the "rule-type" is "data-node" and the "path" matches the requested data node, action node, or notification node. A path is considered to match if the requested node is the node specified by the path or is a descendant node of the path.¶
For a "read" access operation, the rule's "access-operations" leaf has the "read" bit set or has the special value "*".¶
For a "create" access operation, the rule's "access-operations" leaf has the "create" bit set or has the special value "*".¶
For a "delete" access operation, the rule's "access-operations" leaf has the "delete" bit set or has the special value "*".¶
For an "update" access operation, the rule's "access-operations" leaf has the "update" bit set or has the special value "*".¶
For an "execute" access operation, the rule's "access-operations" leaf has the "exec" bit set or has the special value "*".¶
If a matching rule is found, then the "action" leaf is checked. If it is equal to "permit", then the data node access is permitted; otherwise, it is denied. For a "read" access operation, "denied" means that the requested data is not returned in the reply.¶
At this point, no matching rule was found in any rule-list entry.¶
For a "read" access operation, if the requested data node is defined in a YANG module advertised in the server capabilities and the data definition statement contains a "nacm:default-deny-all" statement, then the requested data node and all its descendants are not included in the reply.¶
For a "write" access operation, if the requested data node is defined in a YANG module advertised in the server capabilities and the data definition statement contains a "nacm:default-deny-write" or a "nacm:default-deny-all" statement, then the access request is denied for the data node and all its descendants.¶
For a "read" access operation, if the "read-default" leaf is set to "permit", then include the requested data node in the reply; otherwise, do not include the requested data node or any of its descendants in the reply.¶
For a "write" access operation, if the "write-default" leaf is set to "permit", then permit the data node access request; otherwise, deny the request.¶
For an "execute" access operation, if the "exec-default" leaf is set to "permit", then permit the request; otherwise, deny the request.¶
The following diagram highlights the contents and structure of the NACM YANG module.¶
module: ietf-netconf-acm +--rw nacm +--rw enable-nacm? boolean +--rw read-default? action-type +--rw write-default? action-type +--rw exec-default? action-type +--rw enable-external-groups? boolean +--ro denied-operations yang:zero-based-counter32 +--ro denied-data-writes yang:zero-based-counter32 +--ro denied-notifications yang:zero-based-counter32 +--rw groups | +--rw group* [name] | +--rw name group-name-type | +--rw user-name* user-name-type +--rw rule-list* [name] +--rw name string +--rw group* union +--rw rule* [name] +--rw name string +--rw module-name? union +--rw (rule-type)? | +--:(protocol-operation) | | +--rw rpc-name? union | +--:(notification) | | +--rw notification-name? union | +--:(data-node) | +--rw path node-instance-identifier +--rw access-operations? union +--rw action action-type +--rw comment? string¶
The following YANG module specifies the normative NETCONF content that MUST be supported by the server.¶
The "ietf-netconf-acm" YANG module imports typedefs from [RFC6991].¶
<CODE BEGINS> file<EMAIL_ADDRESS>module ietf-netconf-acm { namespace "urn:ietf:params:xml:ns:yang:ietf-netconf-acm"; prefix nacm; import ietf-yang-types { prefix yang; } organization "IETF NETCONF (Network Configuration) Working Group"; contact "WG Web: <https://datatracker.ietf.org/wg/netconf/> WG List<EMAIL_ADDRESS>Author: Andy Bierman<EMAIL_ADDRESS>Author: Martin Bjorklund<EMAIL_ADDRESS>description "Network Configuration Access Control Model. Copyright (c) 2012 - 2018 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC 8341; see the RFC itself for full legal notices."; revision "2018-02-14" { description "Added support for YANG 1.1 actions and notifications tied to data nodes. Clarified how NACM extensions can be used by other data models."; reference "RFC 8341: Network Configuration Access Control Model"; } revision "2012-02-22" { description "Initial version."; reference "RFC 6536: Network Configuration Protocol (NETCONF) Access Control Model"; } /* * Extension statements */ extension default-deny-write { description "Used to indicate that the data model node represents a sensitive security system parameter. If present, the NETCONF server will only allow the designated 'recovery session' to have write access to the node. An explicit access control rule is required for all other users. If the NACM module is used, then it must be enabled (i.e., /nacm/enable-nacm object equals 'true'), or this extension is ignored. The 'default-deny-write' extension MAY appear within a data definition statement. It is ignored otherwise."; } extension default-deny-all { description "Used to indicate that the data model node controls a very sensitive security system parameter. If present, the NETCONF server will only allow the designated 'recovery session' to have read, write, or execute access to the node. An explicit access control rule is required for all other users. If the NACM module is used, then it must be enabled (i.e., /nacm/enable-nacm object equals 'true'), or this extension is ignored. The 'default-deny-all' extension MAY appear within a data definition statement, 'rpc' statement, or 'notification' statement. It is ignored otherwise."; } /* * Derived types */ typedef user-name-type { type string { length "1..max"; } description "General-purpose username string."; } typedef matchall-string-type { type string { pattern '\*'; } description "The string containing a single asterisk '*' is used to conceptually represent all possible values for the particular leaf using this data type."; } typedef access-operations-type { type bits { bit create { description "Any protocol operation that creates a new data node."; } bit read { description "Any protocol operation or notification that returns the value of a data node."; } bit update { description "Any protocol operation that alters an existing data node."; } bit delete { description "Any protocol operation that removes a data node."; } bit exec { description "Execution access to the specified protocol operation."; } } description "Access operation."; } typedef group-name-type { type string { length "1..max"; pattern '[^\*].*'; } description "Name of administrative group to which users can be assigned."; } typedef action-type { type enumeration { enum permit { description "Requested action is permitted."; } enum deny { description "Requested action is denied."; } } description "Action taken by the server when a particular rule matches."; } typedef node-instance-identifier { type yang:xpath1.0; description "Path expression used to represent a special data node, action, or notification instance-identifier string. A node-instance-identifier value is an unrestricted YANG instance-identifier expression. All the same rules as an instance-identifier apply, except that predicates for keys are optional. If a key predicate is missing, then the node-instance-identifier represents all possible server instances for that key. This XML Path Language (XPath) expression is evaluated in the following context: o The set of namespace declarations are those in scope on the leaf element where this type is used. o The set of variable bindings contains one variable, 'USER', which contains the name of the user of the current session. o The function library is the core function library, but note that due to the syntax restrictions of an instance-identifier, no functions are allowed. o The context node is the root node in the data tree. The accessible tree includes actions and notifications tied to data nodes."; } /* * Data definition statements */ container nacm { nacm:default-deny-all; description "Parameters for NETCONF access control model."; leaf enable-nacm { type boolean; default "true"; description "Enables or disables all NETCONF access control enforcement. If 'true', then enforcement is enabled. If 'false', then enforcement is disabled."; } leaf read-default { type action-type; default "permit"; description "Controls whether read access is granted if no appropriate rule is found for a particular read request."; } leaf write-default { type action-type; default "deny"; description "Controls whether create, update, or delete access is granted if no appropriate rule is found for a particular write request."; } leaf exec-default { type action-type; default "permit"; description "Controls whether exec access is granted if no appropriate rule is found for a particular protocol operation request."; } leaf enable-external-groups { type boolean; default "true"; description "Controls whether the server uses the groups reported by the NETCONF transport layer when it assigns the user to a set of NACM groups. If this leaf has the value 'false', any group names reported by the transport layer are ignored by the server."; } leaf denied-operations { type yang:zero-based-counter32; config false; mandatory true; description "Number of times since the server last restarted that a protocol operation request was denied."; } leaf denied-data-writes { type yang:zero-based-counter32; config false; mandatory true; description "Number of times since the server last restarted that a protocol operation request to alter a configuration datastore was denied."; } leaf denied-notifications { type yang:zero-based-counter32; config false; mandatory true; description "Number of times since the server last restarted that a notification was dropped for a subscription because access to the event type was denied."; } container groups { description "NETCONF access control groups."; list group { key name; description "One NACM group entry. This list will only contain configured entries, not any entries learned from any transport protocols."; leaf name { type group-name-type; description "Group name associated with this entry."; } leaf-list user-name { type user-name-type; description "Each entry identifies the username of a member of the group associated with this entry."; } } } list rule-list { key name; ordered-by user; description "An ordered collection of access control rules."; leaf name { type string { length "1..max"; } description "Arbitrary name assigned to the rule-list."; } leaf-list group { type union { type matchall-string-type; type group-name-type; } description "List of administrative groups that will be assigned the associated access rights defined by the 'rule' list. The string '*' indicates that all groups apply to the entry."; } list rule { key name; ordered-by user; description "One access control rule. Rules are processed in user-defined order until a match is found. A rule matches if 'module-name', 'rule-type', and 'access-operations' match the request. If a rule matches, the 'action' leaf determines whether or not access is granted."; leaf name { type string { length "1..max"; } description "Arbitrary name assigned to the rule."; } leaf module-name { type union { type matchall-string-type; type string; } default "*"; description "Name of the module associated with this rule. This leaf matches if it has the value '*' or if the object being accessed is defined in the module with the specified module name."; } choice rule-type { description "This choice matches if all leafs present in the rule match the request. If no leafs are present, the choice matches all requests."; case protocol-operation { leaf rpc-name { type union { type matchall-string-type; type string; } description "This leaf matches if it has the value '*' or if its value equals the requested protocol operation name."; } } case notification { leaf notification-name { type union { type matchall-string-type; type string; } description "This leaf matches if it has the value '*' or if its value equals the requested notification name."; } } case data-node { leaf path { type node-instance-identifier; mandatory true; description "Data node instance-identifier associated with the data node, action, or notification controlled by this rule. Configuration data or state data instance-identifiers start with a top-level data node. A complete instance-identifier is required for this type of path value. The special value '/' refers to all possible datastore contents."; } } } leaf access-operations { type union { type matchall-string-type; type access-operations-type; } default "*"; description "Access operations associated with this rule. This leaf matches if it has the value '*' or if the bit corresponding to the requested operation is set."; } leaf action { type action-type; mandatory true; description "The access control action associated with the rule. If a rule has been determined to match a particular request, then this object is used to determine whether to permit or deny the request."; } leaf comment { type string; description "A textual description of the access rule."; } } } } } <CODE ENDS>¶
This document reuses the URI for "ietf-netconf-acm" in the "IETF XML Registry".¶
This document updates the module registration in the "YANG Module Names" registry to reference this RFC instead of RFC 6536 for "ietf-netconf-acm". Following the format in [RFC6020], the following has been registered.¶
Name: ietf-netconf-acm Namespace: urn:ietf:params:xml:ns:yang:ietf-netconf-acm Prefix: nacm Reference: RFC 8341¶
The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS [RFC5246].¶
The NETCONF access control model [RFC8341] provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content.¶
There is a risk related to the lack of access control enforcement for the RESTCONF OPTIONS and PATCH methods. The risk here is that the response to OPTIONS and PATCH may vary based on the presence or absence of a resource corresponding to the URL's path. If this is the case, then it can be used to trivially probe for the presence or absence of values within a tree. Therefore, a server MUST NOT vary¶
its responses based on the existence of the underlying resource, which would indicate the presence or absence of resource instances. In particular, servers should not expose any instance information before ensuring that the client has the necessary access permissions to obtain that information. In such cases, servers are expected to always return the "access-denied" error response.¶
There are a number of data nodes defined in this YANG module that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and their sensitivity/vulnerability:¶
This section highlights the issues for an administrator to consider when configuring a NETCONF server with the NACM.¶
Configuration of the access control system is highly sensitive to system security. A server may choose not to allow any user configuration to some portions of it, such as the global security level or the groups that allowed access to system resources.¶
By default, NACM enforcement is enabled. By default, "read" access to all datastore contents is enabled (unless "nacm:default-deny-all" is specified for the data definition), and "exec" access is enabled for safe protocol operations. An administrator needs to ensure that the NACM is enabled and also decide if the default access parameters are set appropriately. Make sure that the following data nodes are properly configured:¶
An administrator needs to restrict write access to all configurable objects within this data model.¶
If write access is allowed for configuration of access control rules, then care needs to be taken not to disrupt the access control enforcement. For example, if the NACM access control rules are edited directly within the running configuration datastore (i.e., :writable-running capability is supported and used), then care needs to be taken not to allow unintended access while the edits are being done.¶
An administrator needs to make sure that the translation from a transport- or implementation-dependent user identity to a NACM username is unique and correct. This requirement is specified in detail in Section 2.2 of [RFC6241].¶
An administrator needs to be aware that the YANG data structures representing access control rules (/nacm/rule-list and /nacm/rule-list/rule) are ordered by the client. The server will evaluate the access control rules according to their relative conceptual order within the running configuration datastore.¶
Note that the /nacm/groups data structure contains the administrative group names used by the server. These group names may be configured locally and/or provided through an external protocol, such as RADIUS [RFC2865] [RFC5607].¶
An administrator needs to be aware of the security properties of any external protocol used by the transport layer to determine group names. For example, if this protocol does not protect against man-in-the-middle attacks, an attacker might be able to inject group names that are configured in the NACM so that a user gets more permissions than it should. In such cases, the administrator may wish to disable the usage of such group names by setting /nacm/enable-external-groups to "false".¶
Some of the readable data nodes in this YANG module may be considered sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. These are the subtrees and data nodes and their sensitivity/vulnerability:¶
An administrator needs to restrict read access to the above-listed objects within this data model, as they reveal access control configuration that could be considered sensitive.¶
There is a risk that invocation of non-standard protocol operations will have undocumented side effects. An administrator needs to construct access control rules such that the configuration datastore is protected from such side effects.¶
It is possible for a session with some write access (e.g., allowed to invoke <edit-config>), but without any access to a particular datastore subtree containing sensitive data, to determine the presence or non-presence of that data. This can be done by repeatedly issuing some sort of edit request (create, update, or delete) and possibly receiving "access-denied" errors in response. These "fishing" attacks can identify the presence or non-presence of specific sensitive data even without the "error-path" field being present within the <rpc-error> response.¶
It may be possible for the set of NETCONF capabilities on the server to change over time. If so, then there is a risk that new protocol operations, notifications, and/or datastore content have been added to the device. An administrator needs to be sure that the access control rules are correct for the new content in this case. Mechanisms to detect NETCONF capability changes on a specific device are outside the scope of this document.¶
It is possible that the data model definition itself (e.g., a YANG when-stmt) will help an unauthorized session determine the presence or even value of sensitive data nodes by examining the presence and values of different data nodes.¶
It is possible that the data model definition itself (e.g., a YANG when-stmt or choice-stmt) will allow a session to implicitly create or delete nodes that the session does not have write access to as an implicit side effect from the processing of an allowed <edit-config> operation.¶
There is a risk that non-standard protocol operations, or even the standard <get> protocol operation, may return data that "aliases" or "copies" sensitive data from a different data object. There may simply be multiple data model definitions that expose or even configure the same underlying system instrumentation.¶
A data model may contain external keys (e.g., YANG leafref), which expose values from a different data structure. An administrator needs to be aware of sensitive data models that contain leafref nodes. This entails finding all the leafref objects that "point" at the sensitive data (i.e., "path-stmt" values) that implicitly or explicitly includes the sensitive data node.¶
It is beyond the scope of this document to define access control enforcement procedures for underlying device instrumentation that may exist to support the NETCONF server operation. An administrator can identify each protocol operation that the server provides and decide if it needs any access control applied to it.¶
This document incorporates the optional use of a recovery session mechanism, which can be used to bypass access control enforcement in emergencies such as NACM configuration errors that disable all access to the server. The configuration and identification of such a recovery session mechanism are implementation specific and are outside the scope of this document. An administrator needs to be aware of any recovery session mechanisms available on the device and make sure that they are used appropriately.¶
It is possible for a session to disrupt configuration management, even without any write access to the configuration, by locking the datastore. This may be done to ensure that all or part of the configuration remains stable while it is being retrieved, or it may be done as a "denial-of-service" attack. There is no way for the server to know the difference. An administrator may wish to restrict "exec" access to the following protocol operations:¶
Designers need to clearly identify any sensitive data, notifications, or protocol operations defined within a YANG module. For such definitions, a "nacm:default-deny-write" or "nacm:default-deny-all" statement ought to be present, in addition to a clear description of the security risks.¶
Protocol operations need to be properly documented by the data model designer so that it is clear to administrators what data nodes (if any) are affected by the protocol operation and what information (if any) is returned in the <rpc-reply> message.¶
Data models ought to be designed so that different access levels for input parameters to protocol operations are not required. The use of generic protocol operations should be avoided, and if different access levels are needed, separate protocol operations should be defined instead.¶
The following XML [W3C.REC-xml-20081126] snippets are provided as examples only, to demonstrate how the NACM can be configured to perform some access control tasks.¶
There needs to be at least one <group> entry in order for any of the access control rules to be useful.¶
The following XML shows arbitrary groups and is not intended to represent any particular use case.¶
<nacm xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-acm"> <groups> <group> <name>admin</name> <user-name>admin</user-name> <user-name>andy</user-name> </group> <group> <name>limited</name> <user-name>wilma</user-name> <user-name>bam-bam</user-name> </group> <group> <name>guest</name> <user-name>guest</user-name><EMAIL_ADDRESS></group> </groups> </nacm>¶
This example shows three groups:¶
Module rules are used to control access to all the content defined in a specific module. A module rule has the "module-name" leaf set but no nodes from the "rule-type" choice set.¶
<nacm xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-acm"> <rule-list> <name>guest-acl</name> <group>guest</group> <rule> <name>deny-ncm</name> <module-name>ietf-netconf-monitoring</module-name> <access-operations>*</access-operations> <action>deny</action> <comment> Do not allow guests any access to the NETCONF monitoring information. </comment> </rule> </rule-list> <rule-list> <name>limited-acl</name> <group>limited</group> <rule> <name>permit-ncm</name> <module-name>ietf-netconf-monitoring</module-name> <access-operations>read</access-operations> <action>permit</action> <comment> Allow read access to the NETCONF monitoring information. </comment> </rule> <rule> <name>permit-exec</name> <module-name>*</module-name> <access-operations>exec</access-operations> <action>permit</action> <comment> Allow invocation of the supported server operations. </comment> </rule> </rule-list> <rule-list> <name>admin-acl</name> <group>admin</group> <rule> <name>permit-all</name> <module-name>*</module-name> <access-operations>*</access-operations> <action>permit</action> <comment> Allow the 'admin' group complete access to all operations and data. </comment> </rule> </rule-list> </nacm>¶
This example shows four module rules:¶
Protocol operation rules are used to control access to a specific protocol operation.¶
<nacm xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-acm"> <rule-list> <name>guest-limited-acl</name> <group>limited</group> <group>guest</group> <rule> <name>deny-kill-session</name> <module-name>ietf-netconf</module-name> <rpc-name>kill-session</rpc-name> <access-operations>exec</access-operations> <action>deny</action> <comment> Do not allow the 'limited' group or the 'guest' group to kill another session. </comment> </rule> <rule> <name>deny-delete-config</name> <module-name>ietf-netconf</module-name> <rpc-name>delete-config</rpc-name> <access-operations>exec</access-operations> <action>deny</action> <comment> Do not allow the 'limited' group or the 'guest' group to delete any configurations. </comment> </rule> </rule-list> <rule-list> <name>limited-acl</name> <group>limited</group> <rule> <name>permit-edit-config</name> <module-name>ietf-netconf</module-name> <rpc-name>edit-config</rpc-name> <access-operations>exec</access-operations> <action>permit</action> <comment> Allow the 'limited' group to edit the configuration. </comment> </rule> </rule-list> </nacm>¶
This example shows three protocol operation rules:¶
Data node rules are used to control access to specific (config and non-config) data nodes within the NETCONF content provided by the server.¶
<nacm xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-acm"> <rule-list> <name>guest-acl</name> <group>guest</group> <rule> <name>deny-nacm</name> <path xmlns:n="urn:ietf:params:xml:ns:yang:ietf-netconf-acm"> /n:nacm </path> <access-operations>*</access-operations> <action>deny</action> <comment> Deny the 'guest' group any access to the /nacm data. </comment> </rule> </rule-list> <rule-list> <name>limited-acl</name> <group>limited</group> <rule> <name>permit-acme-config</name> <path xmlns:acme="http://example.com/ns/netconf"> /acme:acme-netconf/acme:config-parameters </path> <access-operations> read create update delete </access-operations> <action>permit</action> <comment> Allow the 'limited' group complete access to the acme NETCONF configuration parameters. Showing long form of 'access-operations' instead of shorthand. </comment> </rule> </rule-list> <rule-list> <name>guest-limited-acl</name> <group>guest</group> <group>limited</group> <rule> <name>permit-dummy-interface</name> <path xmlns:acme="http://example.com/ns/itf"> /acme:interfaces/acme:interface[acme:name='dummy'] </path> <access-operations>read update</access-operations> <action>permit</action> <comment> Allow the 'limited' and 'guest' groups read and update access to the dummy interface. </comment> </rule> </rule-list> <rule-list> <name>admin-acl</name> <group>admin</group> <rule> <name>permit-interface</name> <path xmlns:acme="http://example.com/ns/itf"> /acme:interfaces/acme:interface </path> <access-operations>*</access-operations> <action>permit</action> <comment> Allow the 'admin' group full access to all acme interfaces. </comment> </rule> </rule-list> </nacm>¶
This example shows four data node rules:¶
Notification rules are used to control access to a specific notification event type.¶
<nacm xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-acm"> <rule-list> <name>sys-acl</name> <group>limited</group> <group>guest</group> <rule> <name>deny-config-change</name> <module-name>acme-system</module-name> <notification-name>sys-config-change</notification-name> <access-operations>read</access-operations> <action>deny</action> <comment> Do not allow the 'guest' group or the 'limited' group to receive config change events. </comment> </rule> </rule-list> </nacm>¶
This example shows one notification rule:¶


"MEONENIM "(Judges 9:37; A.V., “the plain of Meonenim;” R.V., “the oak of Meonenim”) means properly “soothsayers” or “sorcerers,”“wizards” (Deuteronomy 18:10, 14; 2 Kings 21:6; Micah 5:12). This may be the oak at Shechem under which Abram pitched his tent (see SHECHEM), the “enchanter’s oak,” so called, perhaps, from Jacob’s hiding the “strange gods” under it (Genesis 35:4).
"MEONENIM "(Judges 9:37; A.V., “the plain of Meonenim;” R.V., “the oak of Meonenim”) means properly “soothsayers” or “sorcerers,”“wizards” (Deuteronomy 18:10, 14; 2 Kings 21:6; Micah 5:12). This may be the oak at Shechem under which Abram pitched his tent (see SHECHEM), the “enchanter’s oak,” so called, perhaps, from Jacob’s hiding the “strange gods” under it (Genesis 35:4).


Hello {{.Who}},
{{.AdditionalData.User}} has requested to deploy an app with the following details.
{{if .AdditionalData.Success}}{{.AdditionalData.Success}}
{{end}} {{if .AdditionalData.Error}}{{.AdditionalData.Error}}
{{end}} {{if .AdditionalData.Link4Tag}} You can change the permission from {{.AdditionalData.Link4Tag}} {{end}}Env: {{.AdditionalData.Env}}
App: {{.AdditionalData.App}}
Server Class(es):
You can access the deployment information from HERE


find new recipes with on-hand ingredients
Input the item and the amount you have to add it to the virtual Pantry.
Find recipes based on the items in your Pantry. You can even set a tolerance for how many items that are not in the Pantry can be in the recipe
Find the perfect recipe for your mood by sorting using tags, including type of meal, difficulty level, and cook time.


Interface: Packet
interface Packet
The basic message data type accessors. Protocols may use
additional packet interfaces for their protocol specific
data/metadata.
- Author:
-
Philip Levis
- Date:
-
January 5 2005
- See:
-
TEP 116: Packet Protocols
Commands
command void clear(message_t *msg)
command void *getPayload(message_t *msg, uint8_t len)
command uint8_t maxPayloadLength()
command uint8_t payloadLength(message_t *msg)
command void setPayloadLength(message_t *msg, uint8_t len)
Commands - Details
clear
command void clear(message_t *msg)
- Parameters:
-
'message_t* ONE msg' the packet to clear
getPayload
command void *getPayload(message_t *msg, uint8_t len)
- Parameters:
-
'message_t* ONE msg' the packet
-
len
- the length of payload required
- Returns:
-
'void* COUNT_NOK(len)' a pointer to the packet's data payload for this layer
or NULL if len is too big
maxPayloadLength
command uint8_t maxPayloadLength()
- Returns:
-
the maximum size payload allowed by this layer
payloadLength
command uint8_t payloadLength(message_t *msg)
- Parameters:
-
'message_t* ONE msg' the packet to examine
- Returns:
-
the length of its current payload
setPayloadLength
command void setPayloadLength(message_t *msg, uint8_t len)
- Parameters:
-
'message_t* ONE msg' the packet
-
len
- the value to set its length field to


#KogiDecides: Melaye’s nephew killed
by Emmanuel LekeA nephew of Senator Dino Melaye, Olorunjuwon, has been confirmed dead following the orgy of violence that attended the governorship and senatorial elections in the state on Saturday.
While the governorship election held throughout the state, the senatorial election was conducted for Kogi West, where the Court of Appeal found Melaye’s election in the 2019 elections defective.
Melaye, the candidate of the Peoples Democratic Party, contested against Senator Smart Adeyemi of the All Progressives Congress.
Violence was a major factor in Saturday’s elections.
It was there that Olorunjuwon was fatally shot.
He died on Sunday morning.
Melaye made this known via his verified Twitter handle.
He tweeted: “My nephew Olorunjuwon who was shot at my polling unit yesterday died this morning. My brother your death is a Supreme sacrifice in the struggle for the liberation of our people. Rest in peace aburo… So sad.”
Melaye had earlier tweeted: “5 of the thugs who came to disrupt election in my unit have been arrested and have made confessional statements to the fact that Sunday Faleke aide of Yahaya Bello sent them. One of the cars used is also in police custody. Taofik Isah was arrested and wrote a caution statement.”
Previous Post
Zik’s Lecture: Koroma, Obi, Nwobodo, others harp on purposeful migration
Next Post
Outgoing Edo CP tasks security agencies on proficiency


Chris Simmons
logout
UniversiHTTP
Create New Course
Course Number:
Course Name:
Term:
Fall
Year:
2015
Available Students
Students in Course
John Smith
Jane Doe
Linda Zwordling
Lem Hewitt
Ted Crisp
Veronica Palmer
Phil Myman


| |
Methods defined here:
- __init__(self)
- The constructor for Oscilloscope class.
Define and initialize the Oscilloscope default parameters for the OFDM signal definition:
- Set number of carriers.
- Set modulation format.
- Set cyclic prefix.
- Set number of training symbols.
- Set number of generated symbols.
- Set number of generated symbols without TS.
- Set number of OFDM frames.
- Set samples per symbol for the DAC.
- Set DAC frequency sampling.
- Set number of iterations for BER calculation.
- Set sampling frequency of the DPO.
- Set number of received samples. Must be multiple of 4.
- Set factor for clipping the OFDM signal.
- Set quantization steps.
- Set number of bits per symbol.
- generated_data(self, dac_out, bn, En)
- Generate data with different seed for different users/clients.
:param dac_out: output port of DAC
:type dac_out: int
:param bn: array of Ncarriers positions that contains the bits per symbol per subcarrier
:type bn: int array of 512 positions
:param En: array of Ncarriers positions that contains the power per subcarrier figure
:type En: float array of 512 positions
:return: Mapped data, transmitted bitstream and OFDM signal
:rtype: list
- receiver(self, dac_out, osc_in, bn, En, eq)
- Adquires the OFDM signal received at the DPO and recovers by offline DSP the transmitted BitStream.
:param dac_out: output port of DAC
:type dac_out: int
:param osc_in: input port
:type osc_in: int
:param bn: array of Ncarriers positions that contains the bits per symbol per subcarrier
:type bn: int array of 512 positions
:param En: array of Ncarriers positions that contains the power per subcarrier figure
:type En: float array of 512 positions
:param eq: select the type of equalization (ZF or MMSE)
:type eq: str
:return: estimated SNR per subcarrier and the BER of received data
:rtype: list
Static methods defined here:
- acquire(channel_ID, npoints, fs)
- This function acquires the transmitted data from the specified OSC channel.
:param channel_ID: DPO channel used to adquire data
:type channel_ID: int
:param npoints: number of points to adquire
:type npoints: int
:param fs: sampling frequency of the DPO
:type: int
:return: adquired signal
:rtype: float array
Data descriptors defined here:
- __dict__
- dictionary for instance variables (if defined)
- __weakref__
- list of weak references to the object (if defined)
Data and other attributes defined here:
- CP = 0.019
- Constellation = 'QAM'
- NTS = 4
- Ncarriers = 512
- Nframes = 100.0
- Niters = 10
- Nsymbols = 49152
- NsymbolsTS = 51200
- Qt = 255
- bps = 2
- f_DCO =<PHONE_NUMBER>00.0
- fs =<PHONE_NUMBER>0.0
- k_clip = 2.8
- nsamplesrx = 334080.0
- sps = 3.2
|


{% extends "base.html" %} {% block title %} U.N. Universal Period Review - Home {% endblock title %} {% block content %} {{ current_user.id }} See Submissions Data See the Map of Universal Periodic Review Submissions from Around the World UPR Guide Learn more about how the Universal Periodic Review works and the basic guidelines to submit a complaint History of UOCHR A History of the United Nations Office of the High Commissioner {% endblock content %}


--- layout: post title: Rails Tutorial coupon code published: true ---
This is just a quick reminder that the coupon code rtscreencasts, good for a 10% discount on any combination of Ruby on Rails Tutorial products, expires November 1st, 2010.


Squirrels, cats, dogs ... bats? When animals ran loose in stadiums
by Kelly CohenSports are great. Animals are great. So what is the general consensus when the two mix? Chaos -- and awesomeness.
Last week, a black cat ran onto the field during last week's New York Giants and Dallas Cowboys Monday Night Football game at MetLife Stadium, and last we heard, the furry friend was still on the loose.
But that cat was not the first animal to become the star of a game. Far from it.
There was that time when a sportswriter's own dog ran onto the field, interrupting a UGA football game. And San Antonio seemingly has had as many bat encounters as Dracula. In honor of these amazing animal-on-field incidents, let's look back at some other top moments.
What: Bats
Where: AT&T Center, San Antonio
When: 2009 -- and again in 2019
Here's the thing about bats: If you don't know much about them and what they're capable of, they're terrifying. And at AT&T Center, where the San Antonio Spurs play, they've shown up more than once.
First, we have to go to October 2009, when one bat invaded the Spurs game against the Sacramento Kings. Luckily, the swift and speedy Manu Ginobili was still on the Spurs, and he was able to somehow swat the creature down and capture it. What's even more interesting is that this happened on Halloween night.
The bats weren't done though.
The Spurs were taking on the Brooklyn Nets in January when the game was delayed for a few minutes by not just one, but four bats, as the staff worked to clear the animals. Clearly fans knew who was needed, as chants of "Manu, Manu, Manu" broke out in the crowd.
Sorry to break it to you, but the bats weren't done in San Antonio. A month later, during a Spurs game against the New Orleans Pelicans, another bat made its way to the floor at AT&T Center.
This time it was the Spurs' mascot, The Coyote, who was able to capture the critter with a fishing net near the scorer's table during the first quarter. The delay lasted about 90 seconds.
The bats came back AGAIN for a third time this year in March when the Spurs were taking on the Milwaukee Bucks. Again, The Coyote came to the rescue.
What: Squirrel
Where: Busch Stadium, St. Louis
When: 2011
Imagine it's your first time bursting into the spotlight, and you win the World Series.
That's how it went down (kinda) for the gray squirrel that ran across home plate at Busch Stadium during Game 3 of the National League Division Series between the Philadelphia Phillies and the St. Louis Cardinals in October 2011.
There was no delay of game, though it was evident that every player was considerably confused.
*Note: We scoured every corner of the interwebs, and there is no original video of the Rally Squirrel. It seems that 2011 was clearly a much simpler time.
The Phillies won Game 3 though, giving them a 2-1 lead in the NLDS. But the Cardinals won Games 4 and 5, clinching the series and heading to the World Series. St. Louis went on to win the 2011 World Series against the Texas Rangers in seven games with Rally Squirrel playing a role.
What: Cat
Where: M&T Bank Stadium, Baltimore
When: 2017
Cats are pretty nimble creatures, so it's no surprise how often they make their way into any sports venue.
In 2017, a kitten snuck down into M&T Bank Stadium to take in a game between the Miami Dolphins and the Baltimore Ravens.
Tony Romo's play-by-play is highly entertaining. But the cute cat was eventually captured by stadium staff and taken away.
The story had a happy ending, though. According to the team, a stadium employee officially adopted the stray cat and named her "Rae" -- short for Ravens.
 Not only that, but Scotland is one of the most dog-friendly nations. So it's no surprise that Dunhill Links has seen its fair share of pooches during golf play.
In 2012, however, one dog took its ball obsession a bit too far, and stole Paul Casey's golf ball right off of the third hole green.
"It's the weirdest thing I've ever had happen on a golf course," Casey said. "I noticed the dog on the 12th tee and he sort of followed us down the fairway before taking a real liking to my golf ball."
The good news was that Casey was allowed to play his original ball and scored a birdie on the hole.
What: Bees
Where: Great American Ball Park, Cincinnati
When: 2019
The worst part about bees is you really have no idea which way they are going to fly. And of course the fact that they can sting you.
There was an 18-minute delay when a swarm of bees landed at the top of the backstop screen before the first pitch of a game in May between the San Francisco Giants and the Cincinnati Reds.
Honestly, we're just glad no one got stung.


PROJECTS
Here are some examples of my best work so far-
Sleek web page with everything you want to know about the most obscure vampire films made within the past century.
Featured:
- From Dusk Til Dawn
- Byzantium
- What We Do In The Shadows
Being one of my first projects, Kiki is especially close to my heart. This page is clear and concise. Scroll all the way down for an unexpected discovery about Kiki.
My most advanced site to date, Isla Paradiso showcases a luxurious, fictional island you'll wish was the real deal.
Features:
- Branching
- Merging
- Animated Background


Alignment uses display: block
and auto margins to horizontally align elemets.
Alignment uses display: block
and auto margins to horizontally align elemets.
The .center
class uses margin-left: auto
and margin-right: auto
to center elements horizontally.
The .left
class uses margin-right: auto
to left align elements horizontally.
The .right
class uses margin-left: auto
to right align elements horizontally.


GeoWise can add your messages as tasks to your Google account
Authorize
Not interested
{{m.msg}} - {{ audienceList[m.audience].label }}


{% include no-linenos.html content=post.content %} {{ content | markdownify | strip_html | truncate: 200 | escape }}
---
layout: page
# The Home page layout
---
Hi, and welcome to my portfolio site!
Im a software developer, I enjoy coding because it pushes
me to keep growing my skillset and expand my knowledge.
On this site you can read all about me and my activities. On here, i
keep track of a list of my projects, and post on my blog.
Want to know more about me? Contact me via<EMAIL_ADDRESS>{% include no-linenos.html content=post.content %} {{ content | markdownify | strip_html | truncate: 200 | escape }}


I’ve always wanted to do the Color Run with friends because it would be fun to exercise while getting color thrown at me.


module Make(
Machine
:
Std.Primus.Machine.S
)
:sig
..end
| Parameters: |
|
The low-level interface defines three primitives in terms of which we can express a more convenient high-level interface. It is recommened to get acquainted with these three primitives, to understand how the tracker works, however it is better to use the high level interface, whenever it is possible.
To denote the concrete semantics of these primitives we will
use the taint ternary relation T
that establishes a
relation between a value and an object, e.g., T(v,r,x)
is
the relation r
between the value v
and an object x
.
Conceptually, the state of the tracker can be seen as a set
of such relations. Since tracker operations may affect this set
of relations we will denote relations that existed just
before an operation with pre
, e.g., pre(T(v,r,x)
means
that before the operation there was the relation T(v,r,x)
val attach : Std.Primus.value ->
Bap_taint.Std.Taint.Rel.t ->
Bap_taint.Std.Taint.Object.Set.t -> unit Machine.t
attach v r xs
establishes the relation r
between the
value v
and every object x
in the set of objects xs
.
All other relations, as well as relations with other values
are unaffected.
Post conditions:
val lookup : Std.Primus.value ->
Bap_taint.Std.Taint.Rel.t -> Bap_taint.Std.Taint.Object.Set.t Machine.t
lookup v r
returns a set xs
of objects that are related
with the value v
by the relation r
. The operation
doesn't change the state of the tracker.
Post conditions:
val detach : Std.Primus.value ->
Bap_taint.Std.Taint.Rel.t ->
Bap_taint.Std.Taint.Object.Set.t -> unit Machine.t
detach v r xs
removes all relations of type r
between
the value v
and elements of the set of objects
xs
. Relations of other types as well as relations between
other objects and values are unaffected.
Post conditions:
The high-level interface provides a set of easy to use (and
sometimes more efficient) functions. All these functions
could be expressed in terms of the three primitive operations.
val new_direct : Std.Primus.value ->
Bap_taint.Std.Taint.Kind.t -> Bap_taint.Std.Taint.Object.t Machine.t
new_direct v k
introduces a new direct relation between the
value v
and a freshly created object of the given kind
k
. The object is returned.
Essentially:
attach v direct (add (lookup v k) (Object.create k as r)); r
val new_indirect : addr:Std.Primus.value ->
len:Std.Primus.value ->
Bap_taint.Std.Taint.Kind.t -> Bap_taint.Std.Taint.Object.t Machine.t
new_indirect ~addr:v ~len:n k
establishes a new indirect
relation between a set of addresses, denoted by interval
[v,v+n-1]
, and a freshly created object of specified
kind.val sanitize : Std.Primus.value ->
Bap_taint.Std.Taint.Rel.t -> Bap_taint.Std.Taint.Kind.t -> unit Machine.t
Taint.sanitize r k v
detaches all objects related to the
value v
by the relation r
that has the given kind k
.
In terms of the low-level operations:
detach v r (filter (has_kind k) (lookup v r))


--- layout: post status: publish published: true title: Write-in Darwin Barney for the 2011 All-Star Game author: display_name: Corey Fineran login: Corey email<EMAIL_ADDRESS>url: '' author_login: Corey author_email<EMAIL_ADDRESS>wordpress_id: 5350 wordpress_url: http://ivyenvy.com/?p=5350 date: '2011-06-08 07:25:56 +0000' date_gmt: '2011-06-08 12:25:56 +0000' categories: - General Baseball - Infield tags: - All-Star Game - MLB - Darwin Barney - 2011 All-Star comments: - id: 3718 author: Ryan author_email<EMAIL_ADDRESS>author_url: '' date: '2011-06-08 15:38:08 +0000' date_gmt: '2011-06-08 20:38:08 +0000' content: "If for no other reason, do it to cancel out some of the bullshit votes that some big city players have received undeservedly.\r\n\r\nThe list is a complete crock if you've seen who's leading. It's further proof that usually you can't trust the fans to make a decision, and if you do that, you have to have some sort of a weigted system where the writers' votes count for 40% or more. \r\n\r\nMeehan" ---
On last weekend's podcast episode, Jason from Moline asked us about our choice for the Cubs representative(s) for the 2011 MLB All-Star Game. Over the last few weeks, I've been advocating for Darwin Barney and it's time for the campaign to begin.
I'm really not going to get into his accomplishments. I'm going to simply sell him on you by saying this: Which player on the Cubs roster this deserves an All-Star appearance more than Darwin Barney? He entered Spring Training expected to start the season in the minor leagues. He worked hard and earned a spot on the team. Then his performance throughout Spring Training earned him the starting spot at 2nd base. And now he's become, perhaps the most reliable batter on this team.
I'm not a fan of fan voting for the All-Star Game, but I will be casting a ballot (or the 25 allowed by MLB) for Darwin Barney. It takes a little more effort because you have to write him in, but Darwin deserves a few seconds of your time. Do the right thing.


UnderExpress has helped me save 1000+ hours of development time, I worked passionately on my app, didn't really wanted to waste time on landing page.


In the projects CSense and CoSense, we focused on the sharing of emotional states with the remote person in order to augment empathy in both. There are many examples of how remote collaboration may help a person to perform the real world tasks more efficiently. For example, a surgeon performing an operation in an absense of a specialist surgeon, so what if the technology could be used to allow the specialist to participate remotely and instruct the operating room staff and surgeon in order to complete the task successfully. However, participating remotely is not the same as being there in person. In particular, it may be difficult for a remote person to know the exact focus of attention of the local worker (the person performing the actions). Now imagine if the specialist knows the exact focus of attention of the operating staff, he could have been more specific with the instructions and felt more conected and co-present.
The goal of our research project Gaze-Sense is to explore if sharing the focus of attention using eye-tracking information of a local worker can help in feeling the remote instructor (helper) more connected and co-present in a remote assistance scenario.
The research questions for this research project are:
For this system, the main components are:
We made a rough block diagram for the whole idea.
For HMD, we chose Brother AirScouter, a high quality, optical see-through monocular 800 x 600 resolution display with a field of view of 22.4 degrees. In order to align the display with the user's sight line, it has an adjustable mounting mechanism.
We developed a custom made eye tracker using Microsoft Lifecam HD 5000 and custom 3D printed enclosure pointing at user's eye. Now to superimpose eye gaze information on the POV real world, we used Logitech webcam C920 on the system facing outwards as the HWC.
In the software part, there were two main components. First was the eye tracking application that was tracking the eye pupil and overlaying the gaze information as a marker on the real world video feed captured from HWC. We modified the open source eye tracking software developed at Pupil Labs that uses computer vision to track eye pupil at 30 frames per second and map it over the video from HWC. The second was the annotation application that allowed the remote helper to move a mouse pointer over the remote video view of the local worker and shows the result in the display of the HMD. It was a screen cast of remote desktop over the local worker's HMD along with the mouse pointer annotation developed in .NET language.
A 2 by 2 Experiment was designed to validate the hypothesis. In the experiment, we used a remote assistance scenario where a local worker will be given a task and the remote helper who will have experience of performing the task will be assisting the local worker. For the tasks we designed 4 LEGO duplo structures with equal pieces and equal difficulty level. The local worker had to follow remote helper's instruction and perform the task. There was a time that had to be reset before it reaches 0 seconds in order to provide multiple focus points at a time that could relate to an operation theatre scenario.
For the experiment, the conditions that we had were:
The results from the experiment can be seen in the Master's thesis available in the University of Canterbury's online repository.
Project Supervisor: Dr. Christoph Bartneck Project Co-Supervisor: Prof. Mark Billinghurst and Dr. Gun Lee
Portfolio


Reach out to us
Thanks for choosing to reach out to us.
We typically respond within 2-3 business days.
Join Our Slack Community


ServerFactory
object ServerFactory
Factory for transforming json to ServerInstance.
ServerInstance
data class ServerInstance
Entity representing server instance.


| Daily Grain Table | |||
|---|---|---|---|
| DAILY RECOMMENDATION* | Daily minimum amount of whole grains | ||
| Children |
2-3 years old 4-8 years old |
3 ounce equivalents 5 ounce equivalents |
1 ½ ounce equivalents 2 ½ ounce equivalents |
| Girls |
9-13 years old 14-18 years old |
5 ounce equivalents 6 ounce equivalents |
3 ounce equivalents 3 ounce equivalents |
| Boys |
9-13 years old 14-18 years old |
6 ounce equivalents 8 ounce equivalents |
3 ounce equivalents 4 ounce equivalents |
| Women |
19-30 years old 31-50 years old 51+ years old |
6 ounce equivalents 6 ounce equivalents 5 ounce equivalents |
3 ounce equivalents 3 ounce equivalents 3 ounce equivalents |
| Men |
19-30 years old 31-50 years old 51+ years old |
8 ounce equivalents 7 ounce equivalents 6 ounce equivalents |
4 ounce equivalents 3 ½ ounce equivalents 3 ounce equivalents |
Note: Click on the top row to expand the table. If you are on a mobile device, you may need to turn your phone to see the full table.
| Ounce-equivalent of grains table | |||
|---|---|---|---|
| Amount that counts as 1 ounce-equivalent of grains | Common portions and ounce-equivalents | ||
| Bagels |
WG**: whole wheat RG**: plain, egg |
1" mini bagel |
1 large bagel = 4 ounce-equivalents |
| Biscuits |
(baking powder/ buttermilk -RG*) |
1 small (2" diameter) |
1 large (3" diameter) = 2 ounce-equivalents |
| Breads |
WG**: 100% Whole Wheat RG**: white, wheat, French, sourdough |
1 regular slice 1 small slice, French 4 snack-size slices rye bread |
2 regular slices = 2 ounce-equivalents |
| Bulgur |
cracked wheat (WG**) |
½ cup, cooked | |
| Cornbread | (RG**) |
1 small piece (2 ½" x 1 ¼” x 1¼")
|
1 medium piece (2 ½" x 2 ½” x 1 ¼") = 2ounce-equivalents
|
| Crackers |
WG**: 100% whole wheat, rye RG**: saltines, snack crackers |
5 whole wheat crackers 2 rye crisp breads 7 square or round crackers |
|
|
English muffins
|
WG**: whole wheat RG**: plain, raisin |
½ muffin |
1 muffin = 2 ounce-equivalents |
| Muffins |
WG**: whole wheat RG**: bran, corn, plain |
1 small (2 ½" diameter) |
1 large (3 ½" diameter) = 3 ounce-equivalents |
| Oatmeal |
(WG**) |
½ cup, cooked
1 packet instant
1 ounce (1/3 cup), dry (regular or quick)
|
|
| Pancakes |
WG**: Whole
wheat, buckwheat
RG**: buttermilk,
plain
|
1 pancake (4 ½" diameter)
2 small pancakes (3" diameter)
|
3 pancakes (4 ½" diameter) = 3 ounce-equivalents
|
|
Popcorn
|
(WG**) |
3 cups, popped |
1 mini microwave bag or 100-calorie bag, popped = 2 ounce-equivalents
|
|
Ready-to
eat
breakfast
cereal
|
WG**: toasted oat,
whole wheat flakes
RG**: corn flakes,
puffed rice
|
1 cup, flakes or rounds
1 ¼ cup, puffed
|
|
|
Rice
|
WG*: brown, wild
RG*: enriched,
white, polished
|
½ cup cooked
1 ounce, dry
|
1 cup, cooked = 2 ounce-equivalents |
|
Pasta--
spaghetti,
macaroni,
noodles
|
WG**: whole wheat
RG**: enriched,
durum
|
½ cup, cooked
1 ounce, dry
|
1 cup, cooked = 2 ounce-equivalents |
| Tortillas |
WG**: whole wheat,
whole grain corn
RG**: Flour, corn
|
1 small flour tortilla (6" diameter)
1 corn tortilla (6" diameter)
|
1 large tortilla (12" diameter) = 4 ounce-equivalents
|
*WG = whole grains, RG = refined grains. This is shown when products are available both in whole grain and refined grain forms.


May 2023 Status Update
It’s the first week of the month, time for your monthly status update for starbeam.one!
Welcome to May
We are here in May, with Alpha IV scheduled for launch next month. It is very heads-down for me (a good thing) and this post will be short-and-sweet.
880 Flares of Volume, Passing 3,500 Total
Last month we did 880 Flares of volume for the month, which is pretty impressive considering we did 81 total for the month of December. 🤯 We continue to trend in the right direction here, despite zero formal marketing or ad spend. More details around this may be found in this tweet.
We also passed 3,500 total sales+resale volume last month. As always you can watch our statistics on our dashboard, which gets updated every hour.
Feature Progress
The focus on Alpha IV is quality and administration. Namely, we want to be able to perform common user administration tasks quickly before onboarding new users from our planned ad spend. In particular, we have an issue with Oauth2 accounts being created accidentally, and this creates new user accounts altogether. We are working on a user account merge story that will address this. This has been the primary focus of the past two weeks for me. It is a pretty big task as it involves moving each and every property from one to another, and there are a lot. I am almost done with this and it’s getting close to testing. If everything goes well it should be done and tested by the weekend. 🤞
From there, it’s onto other tasks such as enforcing an email policy and improving the sign-in process so that accidental account creation is reduced.
Stand-up & Shine (& Shill)
That does it for this month’s update. For more information around our current state of the system, I direct you to the latest Stand-up & Shine (& Shill):


The top level Filesystem module. The Filesystem module is used for reading and saving files and directories on the device.
| Name | Description |
|---|---|
| addEventListener | add an event listener for the instance to receive view triggered events |
| fireEvent | fire a synthesized event to the views listener |
| removeEventListener | remove a previously added event listener |


WRKY PvWRKY genes drought common Plant proteins gene transcription bean expression Wang PvWRKY, factor stress tolerance Zhang family using {border-style Song abiotic analysis genome px;} #ffffff;} involved sequences soybean Liu Table data ./s--- Arabidopsis Biol. Chen group identified plant zinc However, Sci. additional biotic different elements finger number stress. China Click LINK WRKYGQK acid expressed file. genes. protein results sequence Arabidopsis. Figure Gene Science TaWRKY divided GmWRKY S). Schmutz Supplementary TFs Yang average bean. detected including phylogenetic px; ranged rice tree {font-family (), (Supplementary BMC FIGURE Huang OsWRKY bean, confers factors font-size functional stress, study, transgenic (PvWRKY) ./fpls.. ./journal.pone. Analysis Expression Front. Furthermore, Mao National Oryza Physiol. Qiu Res. Rushton Zhao Zhou double; drought-sensitive drought-tolerant gene, genes, length levels motifs multiple observed response responses sativa sequences), species ssp. structure wheat AtWRKY, Cell Chr Ding Genome GmWRKY, Identification LOI/NOI Mol. NAC Phylogenetic Qin Rep. Sun Wei Xie Yue Zhu analyzed border-color border-width change contain contained distribution drought-related enhanced exons genome-wide identification important obtained patterns performed profiles related resistance responsive seed showed solid; study subgroup superfamily used young {font-style {font-weight −Cx (PvWRKY), (rice), Arabidopsis, AtWRKY Biochem. Bot. Common Eulgem Exp. Finn Jin L.). Lata Luo Ministry NOI/NTD Nature PvWRKY. PvWRKYs Research Shen Somssich TaWRKY, Transcription Yin Yu, Zou abscisic amino article b). binding bold calculated containing courier; database domain element em; example, families full-length function generated green lower method model novel pattern plants play pods, potential promoter pt;} qRT-PCR represent respectively. responsiveness; role roles stresses suggesting up-regulated years


Before Change
import pywink
temp_unit = hass.config.units.temperature_unit
add_devices(WinkThermostat(thermostat, hass, temp_unit)
for thermostat in pywink.get_thermostats())
// pylint: disable=abstract-method,too-many-public-methods, too-many-branches
After Change
_id = climate.object_id() + climate.name()
if _id not in hass.data[DOMAIN]["unique_ids"]:
add_devices([WinkThermostat(climate, hass, temp_unit)])
for climate in pywink.get_air_conditioners():
_id = climate.object_id() + climate.name()
if _id not in hass.data[DOMAIN]["unique_ids"]:
add_devices([WinkAC(climate, hass, temp_unit)])
// pylint: disable=abstract-method,too-many-public-methods, too-many-branches
class WinkThermostat(WinkDevice, ClimateDevice):
Representation of a Wink thermostat.
def __init__(self, wink, hass, temp_unit):


What is Check It Out?
Check It Out lets you interactively see and choose what branch you want to check out without the hassle of trying to type out a long or confusing branch name. Checking out branches just got even simpler!
Installation
We're on NPM!
npm install -g check-it-out
Installing from source
Fork or clone the repository
git clone https://github.com/jwu910/check-it-out.git
Navigate to your repository and run
npm install
Creat a symbolic link to your entry point
Linux/Mac
Navigate to a desired destination directory currently in your pathway
ln -s /path/to/check-it-out/index.js checkit
Usage
Run this command to list local and remote branches!
checkit
Call git log on current highlighted branch with [space]
| Command | Description |
|---|---|
| j/k, down/up | Navigate the list |
| h/l, left/right | Previous/Next remote |
| r | Refresh list with a fetch and prune |
| enter | Select highlighted item |
| space | Git log |
| q, C-c, esc | Quit |
Contributing
Please refer to Contributing Guidelines.


Before Change
operation = video_client.annotate_video(path, features)
print("\nProcessing video for explicit content annotations:")
while not operation.done():
sys.stdout.write(".")
sys.stdout.flush()
time.sleep(15)
print("\nFinished processing.")
// first result is retrieved because a single video was processed
explicit_annotation = (operation.result().annotation_results[0].
explicit_annotation)
likely_string = ("Unknown", "Very unlikely", "Unlikely", "Possible",
"Likely", "Very likely")
for frame in explicit_annotation.frames:
frame_time = frame.time_offset.seconds + frame.time_offset.nanos / 1e9
print("Time: {}s".format(frame_time))
print("\tpornography: {}".format(
After Change
video_client = videointelligence.VideoIntelligenceServiceClient()
features = [videointelligence.enums.Feature.EXPLICIT_CONTENT_DETECTION]
operation = video_client.annotate_video(path, features=features)
print("\nProcessing video for explicit content annotations:")
result = operation.result(timeout=90)
print("\nFinished processing.")
likely_string = ("Unknown", "Very unlikely", "Unlikely", "Possible",
"Likely", "Very likely")
// first result is retrieved because a single video was processed
for frame in result.annotation_results[0].explicit_annotation.frames:
frame_time = frame.time_offset.seconds + frame.time_offset.nanos / 1e9
print("Time: {}s".format(frame_time))
print("\tpornography: {}".format(


The function can be used to automatically show dossier if the user has already logged in.
Otherwise, you can click or to log in.
This solution works on MicroStrategy 2021 Update 2. This solution works for both SAML (loginMode=1048576) and OIDC (loginMode=4194304) authentications.