Misspellings found by codespell.
used = fr_bio_buf_used(&my->buffer);
/*
- * Somehow (magically) we can satisy the read from our buffer. Do so. Note that we do NOT run
+ * Somehow (magically) we can satisfy the read from our buffer. Do so. Note that we do NOT run
* the activation callback, as there is still data in our buffer
*/
if (size < used) {
/*
* We've tried to make room and failed. Which means that the buffer is full, AND there
- * still isn't a compelte packet in the buffer. This is therefore a fatal error. The
+ * still isn't a complete packet in the buffer. This is therefore a fatal error. The
* application has not supplied us with enough read_buffer space to store a complete
* packet.
*/
fr_bio_fd_info_t const *info;
/*
- * We are only useable for FD bios. We need to get "offset" into the packet_ctx, and we don't
+ * We are only usable for FD bios. We need to get "offset" into the packet_ctx, and we don't
* want to have an API which allows for two different "offset" values to be passed to two
* different bios.
*/
* NULL means "nothing matches", which should also be interpreted as "deny".
*
* The difference between "NULL" and "deny" is that NULL is an IP address which was never inserted into
- * the trie. Whereas "deny" menas that there is a parent "allow" range, and we are carving out a "deny"
+ * the trie. Whereas "deny" means that there is a parent "allow" range, and we are carving out a "deny"
* in the middle of that range.
*/
#define FR_BIO_NETWORK_ALLOW ((void *) (-1))
*/
packet_len = talloc_array_length((uint8_t *) eap_packet);
if (packet_len <= EAP_HEADER_LEN) {
- fr_strerror_printf("Invalid EAP data lenth %zd <= 4", packet_len);
+ fr_strerror_printf("Invalid EAP data length %zd <= 4", packet_len);
return false;
}
*/
if (!eap_round->set_request_id) {
/*
- * Id serves to suppport request/response
+ * Id serves to support request/response
* retransmission in the EAP layer and as such
* must be different for 'adjacent' packets
* except in case of success/failure-replies.
return eap_session;
}
-/** 'destroy' an EAP session and dissasociate it from the current request
+/** 'destroy' an EAP session and disassociate it from the current request
*
* @note This could be done in the eap_session_t destructor (and was done previously)
* but this made the code too hard to follow, and too fragile.
* In some EAP methods, the identity may be encrypted, and padded
* out to the block size of the encryption method. These identities
* may contain nuls, and may be much larger than humanly readable
- * identiies.
+ * identities.
*
* The identity value *MUST NOT* be artificially limited or truncated
* here.
/** Check that this EAP-TLS packet is correct and the progression of EAP-TLS packets is sane
*
- * @note In the received packet, No data will be present incase of ACK or NAK
+ * @note In the received packet, No data will be present in case of ACK or NAK
* in this case the packet->data pointer will be NULL.
*
* @param[in] request the current subrequest.
* Here we implement a basic state machine. The state machine is implicit and
* is driven by the state of the TLS session and the flags sent.
* INCOMING DATA:
- * 1. EAP-TLS should get the compelete TLS data from the peer.
+ * 1. EAP-TLS should get the complete TLS data from the peer.
* 2. Store that data in a data structure with any other required info
* 3. Hand this data structure to the TLS module.
* 4. TLS module will perform its operations on the data and hands back to EAP-TLS
if (err) *err = 0;
/*
- * Navigate to the correct request context (parent, outer, curent, etc...)
+ * Navigate to the correct request context (parent, outer, current, etc...)
*/
if (tmpl_request_ptr(&request, tmpl_request(vpt)) < 0) {
if (err) *err = -3;
///< from uctx.ptr.
} tmpl_escape_uctx_type_t;
-/** Funtion to allocate a user context for escaping
+/** Function to allocate a user context for escaping
*
* @param[in] request Request that the tmpl is being evaluated for.
* @param[in] uctx The user context that was passed via the tmpl_escape_t.
/** Set escape parameters for the tmpl output
*
- * @parma[in] vpt to alter.
+ * @param[in] vpt to alter.
* @param[in] escape to set.
*/
void tmpl_set_escape(tmpl_t *vpt, tmpl_escape_t const *escape)
*/
#define TEST_LOG_MAXSIZE ((TEST_DUMP_MAXSIZE * 3) + TEST_MSG_MAXSIZE + 3)
-/* Common test initialiation/clean-up
+/* Common test initialisation/clean-up
*
* In some test suites, it may be needed to perform some sort of the same
* initialization and/or clean-up in all the tests.
char msg[TEST_LOG_MAXSIZE];
size_t count;
- /* Create pipe for receiveing log entries */
+ /* Create pipe for receiving log entries */
if (!CreatePipe(&hRead, &hWrite, &lpPipeAttribute, 0)) {
fprintf(stderr, "Error creating pipe\n");
acutest_exit_(2);
/** Escape a single value box in place
*
- * @note Applies recurssively to the children of group boxes.
+ * @note Applies recursively to the children of group boxes.
*
* @param[in] vb to escape.
* @param[in] escape function to apply to the value box.
/** Escape a list of value boxes in place
*
- * @note Applies recurssively to the children of group boxes.
+ * @note Applies recursively to the children of group boxes.
*
* @note on error, the list may be left in an inconsistent/partially escaped state.
*
/** @name Escape functions
*
- * Apply a tranformation to a value box or list of value boxes.
+ * Apply a transformation to a value box or list of value boxes.
*
* @{
*/
/*
* Custom hackery to figure out if data was set we can't do it any other way because we can't
- * parse the tmpl_t execept within a call_env.
+ * parse the tmpl_t except within a call_env.
*
* We have custom body data so we set REST_HTTP_BODY_CUSTOM, but also need to try and
* figure out what content-type to use. So if they've used the canonical form we