Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
You can record data on the nem (NIS1) chain by an operation like Git push.
To use this gem you need xem to be consumed as a fee.
Data written by using this gem will be exposed without hiding it in the block chain.
$ gem install record_on_chain
And you can use help
command.
$ rochain help
== Record on Chain HELP ==
descriptions
init : initialize RecordOnChain
record : record message on nem(ver-1) chain
secret : recover secret from keyfile
help : display usage
...
$ rochain init
This command generates keyfile
and configfile
. By default, these files are generated in the $HOME/.ro_chain
directory.
default
root
└ home
└ user_dir
└ .ro_chain
├ default_key.yml
└ default_config.yml
When you use -p
option.
-p /home/user_dir/my_dir
root
└ home
└ user_dir
└ my_dir
└ .ro_chain
├ default_key.yml
└ default_config.yml
keyfile
Information such as encrypted secret key is written in the key file. Please note that if the password is empty, the private key is protected only by salt. This is not secure.
configfile
Information such as the destination of the data is written in the config file.
The meaning of each item of the config file is as follows.
RecordOnChain
sends the transaction preferentially to the node at the address written in add_node
.
The format of the key file and config file is yaml.
# sample
:keyfile_path: XXX
:recipient: XXX
:add_node:
- http://127.0.0.1:7890
$ rochain record -m good_luck!
- Please enter your password
**************
!! confirm !!
sender : XXX
recipient : XXX
data : good_luck!
fee : XXX xem
Are you sure you want to record? (y)es or (n)o
y
Exit NOMAL : record command execution succeede.
tx_hash [ XXX ]
By default, this command reads the configuration file in $HOME/.ro_chain/default_config.yml
.
If you want to use the specified file, you need to use the option.
e.g. $HOME/user_dir/my_dir/.ro_chain/my_config.yml
$ rochain record -p $HOME/user_dir/my_dir -c my_config.yml -m good_luck!
Restore the private key from the key file. You will need a password to restore.
$ rochain secret
- Please enter your password
**************
Exit NOMAL : secret command execution succeede.
Secret [ XXX ]
By default, this command reads the configuration file in $HOME/.ro_chain/default_key.yml
.
If you want to use the specified file, you need to use the option.
e.g. $HOME/user_dir/my_dir/.ro_chain/my_key.yml
$ bundle exec rochain secret -k $HOME/user_dir/my_dir/.ro_chain/my_key.yml
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.
nem
highline
https://github.com/JEG2/highline
nem-ruby
https://github.com/44uk/nem-ruby
I also use the source code of the above repository for testing.
Thank you for your development!
Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/record_on_chain. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
The gem is available as open source under the terms of the MIT License.
Everyone interacting in the RecordOnChain project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.
FAQs
Unknown package
We found that record_on_chain demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.