Modify strings, generate sourcemaps
Some useful utilities I often need
A collection of utilities for working with JSON objects, including diffing, conflict resolution, bundling and more.
A compiled-away, type-safe, readable RegExp alternative
magic-string with AST shortcut.
Detect Filetype by bytes
Magically drag and drop files/links, built for React
Offers getProxyForUrl to get the proxy URL for a URL, respecting the *_PROXY (e.g. HTTP_PROXY) and NO_PROXY environment variables.
magic-wand-js =============
Checks for URLs during typing and pasting and automatically converts them to links.
No description provided.
Core typings for Magic SDK packages.
Minimalist yEnc and dynEncode encoder and decoder library for browser and NodeJS
Core business logic for Magic SDK packages.
[SWC plugin] mutable CJS exports
Custom node-sass importer for selector specific imports, node importing, module importing, globbing support and importing files only once
Parse CLI help output
Passwordless authentication for the web.
An async libmagic binding for node.js for detecting content types by data inspection
Exposes a listing of common public APIs from the Magic JS SDK ecosystem.
Variant of quickjs library: Variant with separate .WASM file. Supports browser ESM, NodeJS ESM, and NodeJS CommonJS.
Variant of quickjs library: Variant with separate .WASM file. Supports browser ESM, NodeJS ESM, and NodeJS CommonJS.
<!-- automd:badges codecov color=yellow -->
magic-string with the capability of committing changes
Provides a more Object Oriented interface to RESTful apis.
Extend ActionDispatch::HTTP::UploadedFile to detect file type from magic byte
Allows you to specify http status codes by name rather than magic numbers for more readable code. Go to https://github.com/MishaConway/httpcode for detailed examples.
High-quality integration for https://supermaker.ai/video/blog/unlocking-the-magic-of-pardon-dance-the-viral-video-effect-taking-over-social-media/
Dory lets you forget about IP addresses and port numbers while you are developing your application. Through the magic of local DNS and a reverse proxy, you can access your app at the domain of your choosing. For example, http://myapp.docker or http://this-is-a-really-long-name.but-its-cool-cause-i-like-it. Check it out on github at: https://github.com/FreedomBen/dory
An interface to libmagic to determine file types using "magic" numbers. This can be used in place of calling the file(1) command in Ruby scripts. Shu-yu Guo is the original author but all maintenance is handled by Eric Wong nowadays. source: https://yhbt.net/mahoro.git/ documentation: https://yhbt.net/mahoro/
A Magic Pipe to send data in arbitrary formats to configurable backends, with topics. It features a modular design that allows to configure and extend how the payloads are fetched, serialized, encoded, submitted, and most importantly where: SQS, HTTPS endpoints, etc.
Based on the magic of APIs, we are now capable of connecting to Hulu and retrieving their data for use in other applications. A warning to ye who dare use this, however: Hulu does not guarantee this API's stability, so it's possible (even likely) that your applications may break at any time. This library is based on the work of {hulu-php-library}[https://github.com/adammagana/hulu-php-library], an unofficial PHP client for this same API.
Grab and eval Ruby code via HTTP. You don't care about security, right? This gem is Dr. Nic's fault. We were looking for an easy way to run Ruby code that was publicly available on a web server, and though we've all written something to do this a time or two, we couldn't find a convenient gem. I hacked up a quick example: ruby -rubygems -ropen-uri -e \ 'eval open("http://gist.github.com/raw/473222/snippet.rb").read' \ jbarnette dr-nic-magic-awesome ...but why use a simple Ruby one-liner when we can go overboard and package it as a gem? While we're at it, why not add a tiny bit of extra sugar for Gists? This is not an original idea. It's been done a ton of times before, but this one is ours. Don't use it for anything real or it'll melt your face.
# SshSig - SSH signature verification in pure ruby SshSig is a Ruby gem which can be used to verify signatures signed created by `ssh-keygen`. This capability was [first added](https://github.com/openssh/openssh-portable/commit/2a9c9f7272c1e8665155118fe6536bebdafb6166) in OpenSSH 8.0 allows SSH keys to be used for GPG-like signing capabilities, [including signing git commits](https://github.com/git/git/pull/1041). ## Installation Add this line to your application's Gemfile: ```ruby gem 'ssh_sig' ``` And then execute: $ bundle install Or install it yourself as: $ gem install ssh_sig ## Usage Version 1 of [the SSH signature format](https://github.com/openssh/openssh-portable/blob/b7ffbb17e37f59249c31f1ff59d6c5d80888f689/PROTOCOL.sshsig) supports `ed25519` and `rsa` keys. It is recommended that you use `ed25519` over `rsa` where possible (`ssh-keygen -t ed25519`). In order to verify a signature you need: 1. The public key of the sender 1. The signature file 1. The message to be verified. ```ruby require 'ssh_sig' armored_pubkey = "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAILXPkJPI4TMFWZP4xRBQjNeizUG99KuZCt9G23rX48kz" blob = ::SshSig::Blob.from_armor( <<~EOF -----BEGIN SSH SIGNATURE----- U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgtc+Qk8jhMwVZk/jFEFCM16LNQb 30q5kK30bbetfjyTMAAAAEZmlsZQAAAAAAAAAGc2hhNTEyAAAAUwAAAAtzc2gtZWQyNTUx OQAAAECJITeYJIlEeydsCTh1DkfdhlDJFBa73ojfWe0MbrIzoJKd9THd9WeQrhygSRGsNG cU/stk3/919nykg67yG2gN -----END SSH SIGNATURE----- EOF ) message = "This message was definitely sent by Brian Williams" valid = ::SshSig::Verifier .from_armored_pubkey(armored_pubkey) .verify(blob, message) if valid puts 'Signature is valid' else puts 'Signature is not valid' end ``` Signatures can be created using `ssh-keygen -Y sign -n file -f ~/.ssh/ed_25519 message.txt` and will be outputted in `message.txt.sig`. Public keys can be found in a variety of places, including: - Your `~/.ssh/id_<alg>.pub` file - `authorized_keys` files on servers - `https://gitlab.com/<username>.keys` - `https://github.com/<username>.keys` The `SshSig::Verifier#from_gitlab` and `SshSig::Verifier#from_github` methods are provided to automatically load public keys from the respective `<username>.keys` urls. ```ruby require 'ssh_sig' blob = ::SshSig::Blob.from_armor( <<~EOF -----BEGIN SSH SIGNATURE----- U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgtc+Qk8jhMwVZk/jFEFCM16LNQb 30q5kK30bbetfjyTMAAAAEZmlsZQAAAAAAAAAGc2hhNTEyAAAAUwAAAAtzc2gtZWQyNTUx OQAAAECJITeYJIlEeydsCTh1DkfdhlDJFBa73ojfWe0MbrIzoJKd9THd9WeQrhygSRGsNG cU/stk3/919nykg67yG2gN -----END SSH SIGNATURE----- EOF ) message = 'This message was definitely sent by Brian Williams' valid = ::SshSig::Verifier .from_gitlab('bwill') .verify(blob, message) if valid puts 'Signature is valid' else puts 'Signature is not valid' end ``` ## Is it safe to re-purpose SSH keys for signing? Yes. The [SSH signature protocol](https://github.com/openssh/openssh-portable/blob/d575cf44895104e0fcb0629920fb645207218129/PROTOCOL.sshsig) is designed to be resistant to cross-protocol attacks, where signatures created for one purpose (i.e. signing a git commit), may be re-used for another purpose (i.e. authenticating to a server). It does this using the magic pre-amble (to differentiate between messages signed by `ssh-keygen` and messages used for SSH authentication) and namespaces (to differentiate between messages signed by `ssh-keygen` but used for different purposes). This causes identical messages to produce different signatures for each different protocol. ## 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 the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org). ## Contributing Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/ssh_sig. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/[USERNAME]/ssh_sig/blob/main/CODE_OF_CONDUCT.md). ## License The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
Simple REST api for anime.akinyele.ca
Manage your users' operations (permissions to execute some actions) in your application.
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.