| #!/bin/bash | |
| ###### For generate_certs.sh script ###### | |
| export COUNTRY=US | |
| export STATE=California | |
| export CITY=Irvine | |
| export ORGANIZATION=YourCompany | |
| export UNIT=YourBU | |
| export COMMON_NAME=server.example.com | |
| export SAN_NAME_1=server.example.com |
| # Credit: pwnsdx https://gist.github.com/pwnsdx/1217727ca57de2dd2a372afdd7a0fc21; nebular https://gist.github.com/pwnsdx/d87b034c4c0210b988040ad2f85a68d3#gistcomment-3019082 | |
| # IMPORTANT: Don't forget to logout from your Apple ID in the settings before running it! | |
| # IMPORTANT: You will need to disable SIP: Reboot to Recovery, in Terminal csrutil disable | |
| # WARNING: It might disable things that you may not like. Please double check the services in the TODISABLE vars. | |
| # Get active services: launchctl list | grep -v "\-\t0" | |
| # Find a service: grep -lR [service] /System/Library/Launch* /Library/Launch* ~/Library/LaunchAgents | |
| # List disabled services: launchctl print-disabled user/501 |grep true & launchctl print-disabled system |grep true |
Curve25519: A well-known Montgomery curve designed for ECC at a 128-bit security level.
X25519: The name of the scalar-point multiplication function for points on Curve25519 when performing ECDH. It is also commonly used as a shorthand for ECDH-using-Curve25519.
EdDSA:
Researched by Robert Quattlebaum darco@deepdarc.com.
Last updated 2020-02-03.
| # µPing (MicroPing) for MicroPython | |
| # copyright (c) 2018 Shawwwn <shawwwn1@gmail.com> | |
| # License: MIT | |
| # Internet Checksum Algorithm | |
| # Author: Olav Morken | |
| # https://github.com/olavmrk/python-ping/blob/master/ping.py | |
| # @data: bytes | |
| def checksum(data): | |
| if len(data) & 0x1: # Odd number of bytes |
You can locally pull data from your Rainforest Eagle-200 using cURL.
Rainforest has published a local API document which explains the details of the protocol. But this particular document is about quickly getting to the point and giving you some cURL commands you can use to immediately start pulling out data.
First, I'll assume that you have the following environment variables set:
Overall goal is to remove the requirement that hosts keep track of a packet counter across resets. This is a common source of implementation difficulty. When not implemented correctly, it can severely compromise the security of the network.
In the symmetric version of this scheme, there is a single secret
| https://rfc3161.ai.moda | |
| https://rfc3161.ai.moda/adobe | |
| https://rfc3161.ai.moda/microsoft | |
| https://rfc3161.ai.moda/apple | |
| https://rfc3161.ai.moda/any | |
| http://rfc3161.ai.moda | |
| http://timestamp.digicert.com | |
| http://timestamp.globalsign.com/tsa/r6advanced1 | |
| http://rfc3161timestamp.globalsign.com/advanced | |
| http://timestamp.sectigo.com |
The API used for DTLS is mostly the same as for TLS, because of the mapping of generic functions to protocol specifc ones. Some additional functions are still necessary, because of the new BIO objects and the timer handling for handshake messages. The generic concept of the API is described in the following sections. Examples of applications using DTLS are available at [9].
DTLS の API は TLS とほぼ同じ。 BIO オブジェクトの生成とタイマのために追加でいくつか必要。
