## 引入 ---- ````javascript var QINIU = require('ym-modules').qiniu; var qiniu = new QINIU({ ACCESS_KEY: ACCESS_KEY, SECRET_KEY: SECRET_KEY, BUCKET: BUCKET, SERVER_URL: SERVER_URL, TOKEN_EXPIRE: TOKEN_EXPIRE TOKEN_CACHE_EXPIRE: TOKE
``` MY_EMAIL="email" MY_EMAIL_PASSWORD="password" SECRET_KEY="key" SECRET_IV="secret" # Recaptcha ENCRYPTION_METHOD="aes-256-cbc" RECAPTCHA_V3_SECRET_KEY="key"
```bash export JWT_KEY=<secret_key> ``` ```javascript const {permitRole, permitAction} = require('jwt-permit') // JWT in headers : -H 'authorization: bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJkYXRhIjp7ImFjY291bnRJZCI6IjM1NTIwMGU...' // Permit by Role
Javascript Server SDK for Amplitude Experiment
PM2.io Agent Daemon
ES6 Compatible JWT Module
A simple wrapper for localStorage/sessionStorage that allows one to encrypt/decrypt the data being stored.
Nordigen official API client for Node.js
Universal payments API SDK
OKX CLI - Command line tool for OKX exchange
Node.js client to interact with the Pusher Channels REST API
This tool allows you to execute CLI commands on a Screeps server and export the results via an API.
CLI tool to generate secret keys and UUIDs directly from your terminal.
A package for generating signed tokens. Useful for CSRF tokens or generally to round-trip trusted data through an untrusted client.
Paystack SDK written in Typescript
Official Node library for Rave by Flutterwave
Encrypts and decrypts parts of your objects with KMS
OKX MCP Server - Model Context Protocol server for OKX exchange
A downloader for articles from yuque
ZAPI NodeJS Client with jwt generator.
JsonWebToken implementation for node.js
An SDK for the Altitude platform.
FedEx REST API client for address validation, ground end of day close, OAuth tokens, rate quotes, shipment cancellation, shipment creation, and tracking.
Site management command line interface for THG Altitude platform
A secure vault for managing age-encrypted accounts and data.
CryptGuard is a post-quantum cryptography library with support for Kyber, Falcon, Dilithium in combination with AES and XChaCha20.
CLI client for the Autonomi network
A realtime, decentralized, offline-first, graph data synchronization engine (Rust port)
fastn ID52 identity and cryptographic key management
A Rust library for integrating eSewa payment gateway - supports payment initiation, signature generation, and response validation
Key Policy attribute encryption based on subset cover
MCP server for managing configuration files on OBS (Object Storage Service)
API bindings for the Culqi v2 HTTP API
The unofficial Rust crate for the Coinbase Advanced Trade API
Zero-dependency secrets management for Rust applications
Integrate search data into your rust application. This library is the official wrapper for SerpApi. SerpApi supports Google, Google Maps, Google Shopping, Baidu, Yandex, Yahoo, eBay, App Stores, and more.
Provides an accessor for a secret key stored in tmp
Provides an accessor for a secret key stored in tmp
Tinsy tiny gem to create a new SECRET_KEY value for Symfony apps 🔐
Simple mechanism for loading JSON file with encrypted values.
Git-friendly encrypted secrets for Rails.
Allows easy integration with marketo from ruby. You can synchronize leads and fetch them back by email. By default this is configured for the SOAP wsdl file: http://app.marketo.com/soap/mktows/1_4?WSDL but this is configurable when you construct the client, e.g. client = Rapleaf::Marketo.new_client(<access_key>, <secret_key>, (api_subdomain = 'na-i'), (api_version = '1_5'), (document_version = '1_4')) More information at https://www.rapleaf.com/developers/marketo.
Allows easy integration with marketo from ruby (v2 and up). You can synchronize leads and fetch them back by email. By default this is configured for the SOAP wsdl file: http://app.marketo.com/soap/mktows/1_4?WSDL but this is configurable when you construct the client, e.g. client = Rapleaf::Marketo.new_client(<access_key>, <secret_key>, (api_subdomain = 'na-i'), (api_version = '1_5'), (document_version = '1_4')) More information at https://www.rapleaf.com/developers/marketo. Forked from James O'Brien's marketo gem.
# Cloudutil A utility library for performing helpful tasks with various cloud platform providers ## Installation Add this line to your application's Gemfile: gem 'cloudutil' And then execute: $ bundle install Or install it yourself as: $ gem install cloudutil ## Usage For AWS helpers: require 'cloudutil/aws' aws = Cloudutil::AWS(config: existing_AWS::Config_object) -or- aws = Cloudutil::AWS(access_key: your_AWS_access_key, secret_key: your_AWS_secret_key) subnet_id = aws.resolve_subnet_id('my_subnet_name_or_tag') sec_grp_id = aws.resolve_subnet_id('my_security_group_name_or_tag') ami_id = aws.resolve_subnet_id('my_ami_name_or_tag') ## Contributing 1. Fork it ( https://github.com/mmmorris1975/cloudutil/fork ) 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit -am 'Add some feature'`) 4. Push to the branch (`git push origin my-new-feature`) 5. Create a new Pull Request
# SecureDataBag / Knife Secure Bag Knife Secure Bag provides a consistent interface to DataBagItem, EncryptedDataBagItem as well as the custom created SecureDataBagItem while also providing a few extra handy features to help in your DataBag workflows. SecureDataBagItem, can not only manage your existing DataBagItems and EncryptedDataBagItems, but it also provides you with a DataBag type which enables you to selectively encrypt only some of the fields in your DataBag thus allowing you to be able to search for the remaining fields. ## Installation To build and install the plugin add it your Gemfile or run: ```shell gem install secure_data_bag ``` ## Configuration #### Knife Secure Bag Defaults for the Knife command may be provided in your _knife.rb_ file. ```ruby knife[:secure_data_bag][:encrypted_keys] = %w( password ssh_keys ssh_ids public_keys private_keys keys secret ) knife[:secure_data_bag][:secret_file] = "#{local_dir}/secret.pem" knife[:secure_data_bag][:export_root] = "#{kitchen_dir}/data_bags" knife[:secure_data_bag][:export_on_upload] = true knife[:secure_data_bag][:defaults][:secrets][:export_format] = 'plain' ``` To break this up: `knife[:secure_data_bag][:encrypted_keys] = []` When Knife Secure Bag encrypts a hash with an _encryption format_ of *nested*, it will recursively walk through the hash from the bottom up and encrypt any key found within this array. `knife[:secure_data_bag][:secret_file]` When encryption is required, the shared secret found at this location will be loaded. `knife[:secure_data_bag][:export_root]` When exporting a data\_bag\_item, files will be created in below this root directory. Typically this would be the data\_bag folder located within your kitchen. `knife[:secure_data_bag][:export_on_upload]` When a data\_bag\_item is edited using `knife secure bag edit`, it may be automatically exported to the _export\_root_. `knife[:secure_data_bag][:defaults][:secrets][:export_format]` The configuration file additionally supports the _defaults_ hash which provides default values for all _command line arguments_ that one might use. Of all of them only the _export\_format_ key is likely to be of much use. ## Examples #### Chef cookbook recipe ```ruby metadata = {} # Define the keys we wish to encrypt metadata[:encrypted_keys] = %w(encoded) # Optionally load a specific shared secret. Otherwise, the global # encrypted\_data\_bag\_secret will be automatically used. secret_key = SecureDataBagItem.load_key("/path/to/secret") # Create a hash of data to use as an exampe raw_data = { id: "item", data_bag: "data_bag", encoded: "my string", unencoded: "other string" } # Instantiate a SecureDataBagItem from a hash item = SecureDataBagItem.from_hash(data, metadata) # Or more explicitely item = SecureDataBagItem.from_hash(data, encrypted_keys: %w(encoded)) # Or load from server item = SecureDataBagItem.load("data_bag", "item") # Print the un-encrypted raw data pp item.raw_data # Print the un-encrypted `encoded` key pp item['encoded'] # Print the encrypted hash as a data_bag_item hash pp item.to_hash =begin { id: "item", data_bag: "data_bag", encoded: { encrypted_data: "encoded", cipher: aes-256-cbc, iv: 13453453dkgfefg== version: 1 } unencoded: "other string", } =end ``` ## Usage #### Knife commands Print an DataBagItem, EncryptedDataBagItem or SecureDataBagItem, auto-detecting the encryption method used as plain text. ```shell knife secure bag show -F js secrets secret_item ``` Print an DataBagItem, EncryptedDataBagItem or SecureDataBagItem, auto-detecting the encryption method used as a SecureDataBagItem in encrypted format. ```shell knife secure bag show -F js secrets secret_item --enc-format nested ``` Edit an EncryptedDataBagItem, preserve it's encryption type, and export a copy to the _data\_bag_ folder in your kitchen. ```shell knife secure bag edit secrets secret_item --export ``` ## Knife SubCommands Most of the SubCommands support the following command-line options: `--enc-format [plain,encrypted,nested]` Ensure that, when displaying or uploading the data\_bag\_item, we forcibly encrypt the data\_bag\_item using the specified format instead of preserving the existing format. In this case: - plain: refers to a DataBagItem - encrypted: refers to an EnrytpedDataBagItem - nested: refers to a SecureDataBagItem `--dec-format [plain,encrypted,nested]` Attempt to decrypt the data\_bag\_item using the given format rather than the auto-detected one. The only real reason to use this is when you wish to specifically select _plain_ as the format so as to not decrypt the item. `--enc-keys key1,key2,key3` Provide a comma delimited list of hash keys which should be encrypted when encrypting the data\_bag\_item. This list will be concatenated with any key names listed in the configuration file or which were previously encrypted. `--export` Export the data\_bag\_item to json file in either of _export-format_ or _enc-format_. `--export-format` Overrides the encryption format only for the _export_ feature. `--export-root` Root directly under which a folder should exist for each _data_bag_ into which to export _data_bag_items_ as json files. When displaying the content of the _data\_bag\_item_, an additional key of *_secure_metadata* will be added to the output which contains gem specific metadata such as the encryption formats and any encrypted keys found. This key will _not_ be saved with the item, however it may be manipulated to alter the behavior of the _edit_ or _export_ commands. #### knife secure bag show DATA_BAG ITEM This command functions just like `knife data bag show` and is used to print out the content of either a DataBagItem, EncryptedDataBagItem or SecureDataBagItem. By default, it will auto-detect the Item type, and print it's unencrypted version to the terminal. This behavior, however, may be altered using the previously mentioned command line options. #### knife secure bag open PATH This commands functions much like `knife secure bag show`, however it is designed to load a _data\_bag\_item_ from disk as opposed to loading it from Chef server. This may be of use when view the content of an exported encrypted file. #### knife secure bag edit DATA_BAG DATA_BAG_ITEM This command functions just like `knife data bag edit` and is used to edit either a DataBagItem, EncryptedDataBagItem or a SecureDataBagItem. It supports all of the same options as `knife secure bag show`. #### knife secure bag from file DATA_BAG PATH This command functions just like `knife data bag from file` and is used to upload either a DataBagItem, EncryptedDataBagItem or a SecureDataBagItem. It supports all of the same options as `knife secure bag show`. ## Recipe DSL The gem additionally provides a few Recipe DSL methods which may be useful. ```ruby load_secure_item = secure_data_bag_item( data_bag_name, data_bag_item, cache: false ) load_plain_item = data_bag_item(data_bag_name, data_bag_item) convert_plain_to_secure = secure_data_bag_item!(load_plain_item) ```
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.