Skip to content

Instantly share code, notes, and snippets.

View metaver5o's full-sized avatar
💭
cryptography enthusiast

metaver5o.eth metaver5o

💭
cryptography enthusiast
  • Pixelvault
  • Earth
View GitHub Profile

Keybase proof

I hereby claim:

  • I am mmatoscom on github.
  • I am mmatos (https://keybase.io/mmatos) on keybase.
  • I have a public key whose fingerprint is A5D6 0838 9200 89C1 4479 5E5F E7B7 DA39 F66A FAA3

To claim this, I am signing this object:

Verifying my Blockstack ID is secured with the address 1GGVGykYZ7UW7Fm2oR9sw1R7ZhAw1Moxjz https://explorer.blockstack.org/address/1GGVGykYZ7UW7Fm2oR9sw1R7ZhAw1Moxjz
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQINBFfxgy4BEACmSA/Dea3HtrfyWY3anNd3qE7QZV5+TYvtR7BkTvu1PI7YF1Ia
UrXHnh1RFb2nIwzHicJhZLgKcEh9Ohs7/xvI1rmL18d/TPX7prVy43R+ljz5Su1e
NmUI8rr5g+TD9alJ8PfdOR3/E5akR5VQRzZ9hBWlTVfFORDruJ3pmIuNtslq4WAS
uD3ajWFTGDZvZk1lUkvAFf79pC4v+8e+A4ur9HFDwBgOcilYaqerYEFauZQzCkCX
r6LTHAGh2s5HnWrg0o/JtOwa9On3kViiK3gQKXZ1PRN0Pmmio0kW/NnntTB3sS9h
kjpfL+qNVP5SppXskK/hdI6gILiOx2JWWEq+cb79zSiOxq7LIlb25ONLBIjZtOm+
Nn5XHBj/rX/8RH4e9jvWkNSEvzcv7rcnmkmKpyT3RF3BUm/FFuadgHZwNM1xKLy3
BZinkzmDnHhlV2/mFGqFDBI+2j8cyYQPqpF5f6VPVjSMqrVNVqXLZwsopmdN2aFf
abandon
ability
able
about
above
absent
absorb
abstract
absurd
abuse

AES CIS Postmortem (Jira Issue #AESEDI-53447)

  • Date
    2019-Nov-14

  • Author
    M Matos

  • Status
    Resolved

FWIW: I didn't produce the content presented here (the outline from Edmond Lau's book). I've just copy-pasted it from somewhere over the Internet, but I cannot remember what exactly the original source is. I was also not able to find the author's name, so I cannot give him/her the proper credits.


Effective Engineer - Notes

What's an Effective Engineer?

@metaver5o
metaver5o / Ethereum_private_network.md
Last active January 22, 2020 13:44 — forked from 0mkara/Ethereum_private_network.md
Ethereum private network configuration guide.

Create your own Ethereum private network

Introduction

Used nodes:

Linux raspberrypi 4.9.41-v7+ #1023 SMP Tue Aug 8 16:00:15 BST 2017 armv7l GNU/Linux
Linux localhost.localdomain 4.14.5-200.fc26.x86_64 #1 SMP Mon Dec 11 16:29:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
@metaver5o
metaver5o / netgear-private-key-disclosure.md
Created January 23, 2020 13:07 — forked from nstarke/netgear-private-key-disclosure.md
Netgear TLS Private Key Disclosure through Device Firmware Images

Netgear Signed TLS Cert Private Key Disclosure

Overview

There are at least two valid, signed TLS certificates that are bundled with publicly available Netgear device firmware.

These certificates are trusted by browsers on all platforms, but will surely be added to revocation lists shortly.

The firmware images that contained these certificates along with their private keys were publicly available for download through Netgear's support website, without authentication; thus anyone in the world could have retrieved these keys.

Transaction: https://etherscan.io/tx/0xb5c8bd9430b6cc87a0e2fe110ece6bf527fa4f170a4bc8cd032f768fc5219838

Contract Hacker Contract (4f4e)

Eth Transferred:

  • TRANSFER 5,500 Ether From Hacker Contract (4f4e) To Compound (4ddc)
  • TRANSFER 1,300 Ether From Hacker Contract (4f4e) To Unknown token (b020)
  • TRANSFER 1,300 Ether From Unknown token (b020) To 0x Weth (c02a)
  • TRANSFER 5,637.623762376237623786 Ether From 0x Weth (c02a) To Kyber 1 (57f8)
  • TRANSFER 5,637.623762376237623786 Ether From Kyber 1 (57f8) To Kyber 2 (65bf)
@metaver5o
metaver5o / bZx.exploit
Created February 20, 2020 09:26
bZx smart contract exploit
#
# Panoramix v4 Oct 2019
# Decompiled source of 0x4f4e0f2cb72E718fC0433222768c57e823162152
#
# Let's make the world open source
#
#
# I failed with these:
# - unknowna270ef06(?)
# All the rest is below.