profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/defuse/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Taylor Hornby defuse Electric Coin Company Calgary, Canada https://defuse.ca/

defuse/crackstation-hashdb 270

CrackStation.net's Lookup Table Implementation.

defuse/crackstation 89

Source code for my crackstation.net website.

defuse/defuse.ca 46

The source code to my defuse.ca website.

defuse/email-spoofing 36

Ruby script for spoofing SMTP emails.

defuse/dnsfs 34

Host files with DNS

defuse/airgap 26

Design for an economical and simple air-gapped system.

defuse/gas-obfuscation 23

Extremely simple but inefficient x86-64 assembly obfuscation.

defuse/DAWr 19

The start of a library for building a DAW and/or sound experiments in Rust

defuse/encutil 17

Example of how to build a command-line file encryption utility with defuse/php-encryption.

MemberEvent
MemberEvent
MemberEvent
MemberEvent
MemberEvent

push eventdefuse/defuse.ca

Taylor Hornby

commit sha 2ba1e52ba8463e03c0a06805c3b5af103ee3001e

RL

view details

push time in 2 days

MemberEvent
MemberEvent
MemberEvent
MemberEvent

push eventdefuse/defuse.ca

Taylor Hornby

commit sha 156bb0d5cbb814c4d7f070b29459c936a94832cd

RL

view details

push time in 10 days

issue commentzcash/zcash-android-wallet-sdk

Add proguard consumer rules

It would be nice if our official app APKs are as easily reverse-engineerable as possible (to assist any security researchers looking at them!), so anything that heavily obfuscates rather than just being a performance optimization should probably be turned off in our apps that consume the SDK.

Low-effort things to make the SDK compatible with consumers who want to obfuscate makes sense to do, though.

ccjernigan

comment created time in 10 days

issue commentzcash/zcash-android-wallet-sdk

Add proguard consumer rules

It sounds like there's some code optimization stuff in addition to obfuscation. As we discussed in standup this may be worth doing to support (our or others') optimization of the apps, but obfuscating for obfuscation alone isn't worth doing.

ccjernigan

comment created time in 10 days

pull request commentzcash/zcash

[image-upgrade] vuln upgrade for docker base image

Do you have more details on "debian@10 › glibc/libc6@2.28-10 can cause a "infinite loop" for this package in the image" -- is there a CVE for this one or a bug ticket I can look into?

If we hardcode a date here there's a chance we won't be quick to update it, or people won't remember to git pull, and end up using an out-of-date and vulnerable image. I think we should use debian:11 (after testing this works with debian bullseye) so that everyone will get the latest image for that release.

JonLittleIT

comment created time in 11 days

issue closedzcash/zcash-gitian

Fix Zcash Smoke Tests

closed time in 14 days

mdr0id

push eventdefuse/defuse.ca

Taylor Hornby

commit sha a1510fee89762a3be27d65ca262fa7fe0491e196

RL

view details

push time in 15 days

push eventdefuse/defuse.ca

Taylor Hornby

commit sha de2c6c2ad54ac8a5adb10312d9f3b310ff199605

RL

view details

push time in 16 days

issue closedadityapk00/zecwallet-light-cli

Deserialization

closed time in 21 days

defuse

issue commentadityapk00/zecwallet-light-cli

Deserialization

oops I accidentally hit enter or something and submitted this when I didn't mean to

defuse

comment created time in 21 days

issue openedadityapk00/zecwallet-light-cli

Deserialization

created time in 21 days

created tagzcash/zcash

tagv4.5.1

Zcash - Internet Money

created time in 23 days

pull request commentzcash/zcash

Release v4.5.1

utACK

str4d

comment created time in 23 days

pull request commentzcash/lightwalletd

Improve documentation for use with docker-compose

ACK

superbaud

comment created time in 23 days

push eventsuperbaud/lightwalletd

Taylor Hornby

commit sha 2defc2501d7837d33bcb7d7b2ac0300f659f2ea9

Fix em-dashes and add instructions to use a random password

view details

push time in 23 days

pull request commentzcash/zcash

Fix bugs in testnet Orchard circuit

utACK

str4d

comment created time in 23 days

pull request commentzcash/librustzcash

NU5 testnet update

utACK again :)

str4d

comment created time in 23 days

PullRequestReviewEvent

Pull request review commentzcash/librustzcash

NU5 testnet update

 impl Parameters for TestNetwork {             NetworkUpgrade::Blossom => Some(BlockHeight(584_000)),             NetworkUpgrade::Heartwood => Some(BlockHeight(903_800)),             NetworkUpgrade::Canopy => Some(BlockHeight(1_028_500)),-            NetworkUpgrade::Nu5 => None,+            NetworkUpgrade::Nu5 => Some(BlockHeight(1_599_200)),

Did we miss this change in the previous release?

str4d

comment created time in 23 days

pull request commentzcash/librustzcash

NU5 testnet update

utACK I double-checked hashes and constants

str4d

comment created time in 23 days

issue commentzcash/lightwalletd

loggerFromContext(): Anonymize the addresses, cryptopan?

It's referring to https://en.wikipedia.org/wiki/Crypto-PAn, which is a way to log identifiers like IP addresses (and in this case zcash addresses) more privately. I don't think it's worth the effort at this point.

LarryRuane

comment created time in 24 days