This code demonstrate how to load sensitive code from encrypted files at runtime.
$ ruby sample.rb
Now, protect the sensitive code
# Tested using | |
# Ruby v3.2.2 / openssl gem v3.1.0 | |
# Ubuntu with OpenSSL 3.0.2 | |
require 'openssl' | |
class ECKey | |
CURVE='prime256v1' | |
source "https://rubygems.org" | |
gem "async-websocket" |
I hereby claim:
To claim this, I am signing this object:
@echo off | |
setlocal EnableDelayedExpansion | |
@REM Build LibZMQ, CZMQ et Zyre with their dependencies | |
@REM Toolchain : Visual Studio 2017 | |
@REM Dependencies : CMAKE, GIT (Git for Windows), PERL (Strawberry Perl), NASM | |
@REM | |
@REM After successful build the resulting DLL are moved into zmq_build_%TODAY%\out | |
@REM |
source 'https://rubygems.org' | |
ruby '2.4.1' | |
gem 'mail' | |
gem 'mailjet', git: 'https://github.com/mailjet/mailjet-gem.git', branch: 'prerelease/v1.5.2' | |
gem 'activesupport', :require => 'active_support/all' |
#cloud-config | |
--- | |
hostname: %XSVMNAMETOHOSTNAME% | |
ssh_authorized_keys: | |
# - ssh-rsa <my key !> | |
# The following entry will automatically be replaced with a public key | |
# generated by XenServer's container management. The key-entry must exist, | |
# in order to enable container management for this VM. | |
- ssh-rsa %XSCONTAINERRSAPUB% | |
coreos: |
#!/usr/bin/env ruby | |
require 'uri' | |
require 'pty' | |
require 'expect' | |
if ARGV.length == 2 | |
app = ARGV[0] | |
dump = ARGV[1] | |
else |
$ LC_ALL=C bin/rbx -X19 gem install nmatrix | |
Building native extensions. This could take a while... | |
ERROR: Error installing nmatrix: | |
ERROR: Failed to build gem native extension. | |
/home/pierre/Sources/rubinius/bin/rbx extconf.rb | |
checking for main() in -llapack... yes | |
checking for main() in -lcblas... yes | |
checking for main() in -latlas... yes | |
checking for clapack.h... no |
1) Make sure you have these tools installed and configured | |
* Ruby | |
* The ShellyCloud CLI | |
* The Scalingo CLI | |
* tar, gunzip | |
* The PostgreSQL client tools (pg_restore) | |
2) Make sure your database on scalingo side is empty (delete your postgresql addon and recreate it) | |
BEWARE : YOU WILL LOOSE ALL YOUR DATA ! So make backups before deleting your PG Addon ! |