Hardware key backends for YubiKey PIV and macOS Secure Enclave
Hardware key backends for AAuth: YubiKey PIV and macOS Secure Enclave
Isomorphic client library for Azure KeyVault's keys.
Hardware key backends for macOS ARM64 native binary
Hardware key backends for macOS x64 native binary
Hardware key backends for Linux x64 (glibc) native binary
Hardware key backends for AAuth — macOS x64 native binary
Hardware key backends for AAuth — macOS ARM64 native binary
Hardware key backends for Windows x64 (MSVC) native binary
Hardware key backends for AAuth — Linux x64 (glibc) native binary
Hardware key backends for AAuth — Windows x64 (MSVC) native binary
Constants and utilities about visitor keys to traverse AST.
SDK to interact with GridPlus Lattice1 device
Visitor keys used to help traverse the TypeScript-ESTree AST
An Object.keys replacement, in case Object.keys is not available. From https://github.com/es-shims/es5-shim
Compile objects with duplicate keys to valid strict ES5
Robustly get an object's own property keys (strings and symbols), including non-enumerables when possible
Unique machine (desktop) id (no admin privileges required).
An Abstract Class for desribing an Ethereum Signer for ethers.
IndexedDB stamper for Phantom Wallet SDK with non-extractable key storage
Lowercase the keys of an object
Like `Object.keys()` but also includes symbols
Hardware Wallet support for ethers.
Most modern mobile touch slider and framework with hardware accelerated transitions
FIDO2 hardware key unlock and Shamir secret sharing for Sigillum
Secret access layer for cooperative AI agents — structured, policy-gated, audited credential access
Cross-platform hardware-backed device keystore abstraction with attestation
Hardware private key storage for next-generation cryptography (e.g. BLS) initially targeting USB armory Mk II devices from F-Secure
Hardware private key storage for next-generation cryptography (e.g. BLS) initially targeting USB armory Mk II devices from F-Secure
Automatically link the hardware data bag items to their node
The scrypt key derivation function is designed to be far more secure against hardware brute-force attacks than alternative functions such as PBKDF2 or bcrypt.
OVH::Provisioner ================ Interact with OVH REST API, mainly targeted to manage dedicated servers and OVH DNS. Installation ------------ Add this line to your application's Gemfile: ```ruby gem 'ovh-provisioner' ``` And then execute: $ bundle Or install it yourself as: $ gem install ovh-provisioner Configuration ------------- The best way to use ovh-provisioner is to create a configuration file (recommended path: ~/.config/ovh-provisioner.yml) containing your keys and some general configuration. Then, just launch it to get all commands with their description. Example: ```yaml # All keys can be overriden with cli options api_url: https://eu.api.ovh.com/1.0 app_key: XXXXXXXXXXXX app_secret: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX consumer_key: XXXXXXXXXXXXXXXXXXXXXXXXXXXX template: template_name # is be defined in OVH manager when you save a template use_distrib_kernel: true ssh-key: 'key_name_to install' # name_scheme support any variable available as attribute in # lib/ovh/provisioner/api_object/dedicated_server.rb # Along with name_domain, it is used to rename (reverse dns) servers name_scheme: '%{location}-%{flavor_tag}-%{server_id}.%{vrack}' name_domain: example.com # example of flavors, you can use any hardware parameters from # GET /dedicated/server/{serviceName}/specifications/hardware # to differentiate your flavors flavors: EG-16S: tag: eg16s hardware: description: 'Serveur EG-16 - E3-1230v6 - 16GB - SoftRaid 2x450GB NVMe' EG-32S: tag: eg32s hardware: description: 'Serveur EG-32 - E3-1270v6 - 32GB - SoftRaid 2x450GB NVMe' EG-64S: tag: eg64s hardware: description: 'Serveur EG-64 - E5-1650v3 - 64GB - SoftRaid 2x450GB NVMe' ``` Development ----------- After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment. To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org). Contributing ------------ Please read carefully [CONTRIBUTING.md](CONTRIBUTING.md) before making a merge request. License and Author ------------------ - Author:: Samuel Bernard (<samuel.bernard@gmail.com>) ```text Copyright (c) 2015-2016 Sam4Mobile, 2017-2018 Make.org Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ```
TOTP stands for Time-Based One-Time Password. Many websites and services require two-factor authentication (2FA) or multi-factor authentication (MFA) where the user is required to present two or more pieces of evidence: Something only the user knows, e.g., password, passphrase, etc. Something only the user has, e.g., hardware token, mobile phone, etc. Something only the user is, e.g., biometrics. TOTP stands for Time-Based One-Time Password. Many websites and services require two-factor authentication (2FA) or multi-factor authentication (MFA) where the user is required to present two or more pieces of evidence. A TOTP value serves as the second factor, i.e., it proves that the user is in possession of a device (e.g., mobile phone) that contains a TOTP secret key from which the TOTP value is generated. Usually the service provider that provides a user's account also issues a secret key encoded either as a Base32 string or as a QR code. This secret key is added to an authenticator app (e.g., Google Authenticator) on a mobile device. The app can then generate TOTP values based on the current time. By default, it generates a new TOTP value every 30 seconds.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.