profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/ebiggers/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.

google/syzkaller 3607

syzkaller is an unsupervised coverage-guided kernel fuzzer

google/fscrypt 575

Go tool for managing Linux filesystem encryption

google/adiantum 425

Adiantum and HPolyC specification and test vectors

ebiggers/libdeflate 355

Heavily optimized library for DEFLATE/zlib/gzip compression and decompression

ebiggers/ntfs-3g-system-compression 69

NTFS-3G plugin for reading "system compressed" files

google/fscryptctl 66

Small C tool for Linux filesystem encryption

ebiggers/avl_tree 64

High performance C implementation of AVL trees

ebiggers/xpack 24

Experimental compression format (unmaintained, do not use!)

ebiggers/wimlib 15

Mirror of git://wimlib.net/wimlib: Library supporting the Windows Imaging Format (WIM). Please file issues on the official forums (https://wimlib.net/forums/viewforum.php?f=1) rather than here.

ebiggers/fat-fuse 8

Simple readonly FUSE driver for FAT filesystems

issue commentebiggers/libdeflate

Support future detection for Embarcadero C++ Free compiler

I haven't used this compiler before, and it doesn't appear to be commonly used. It also doesn't appear to be easily installable on Linux like apt-get install clang (presumably because it is closed source?). So I am not planning to test it myself. If you would like some things to be changed to support it anyway, then please submit a pull request.

zedxxx

comment created time in 3 days

push eventebiggers/fscrypt

Eric Biggers

commit sha a3b365be9878b14fd36cc310d3c8b1fdccfdcb04

README: add troubleshooting section for ENOPKG error Inspired by https://reddit.com/r/linuxquestions/comments/n75dv4

view details

Eric Biggers

commit sha 6e38153e0d471ec1fe50fca31c9bb3e847eca8cc

cli-tests: fix failure with latest bash version

view details

push time in 8 days

delete branch ebiggers/fscrypt

delete branch : cli-test-fix

delete time in 8 days

push eventgoogle/fscrypt

Eric Biggers

commit sha 6e38153e0d471ec1fe50fca31c9bb3e847eca8cc

cli-tests: fix failure with latest bash version

view details

push time in 8 days

issue commentgoogle/fscryptctl

Unable to write file on ecrypted directory with zero-ed key

For future reference, this issue was specific to v1 encryption policies that use AES-256-XTS; it was caused by the two halves of the AES-256-XTS keys being identical which is not allowed. fscryptctl v1.0 only supports v2 encryption policies, which don't have this quirk and will accept an all-zeros key, due to the use of a new key derivation function which results in the halves of the AES-256-XTS keys differing even if the halves of the input key are the same.

That being said, it obviously doesn't make sense to use an all-zeroes key, except possibly for testing.

comio

comment created time in 8 days

delete branch ebiggers/fscryptctl

delete branch : man-page

delete time in 8 days

push eventgoogle/fscryptctl

Eric Biggers

commit sha a3a0333c5cb6782ea7c40dba4e1fb9b4b0602186

Add a man page for fscryptctl Add a manual page for fscryptctl, documenting all subcommands and options. The page is written in Markdown and is translated to groff using pandoc.

view details

Eric Biggers

commit sha e8636420a94d36a5691b5720821ef49f96648a21

Mention the man page in `fscryptctl --help` output

view details

push time in 8 days

PR merged google/fscryptctl

Add a man page for fscryptctl

Add a manual page for fscryptctl, documenting all subcommands and options.

The page is written in Markdown and is translated to groff using pandoc.

+202 -17

0 comment

6 changed files

ebiggers

pr closed time in 8 days

push eventebiggers/fscrypt

Eric Biggers

commit sha e2ec4e44b8d9170344634da556728f2c5e6de78f

cli-tests: fix failure with latest bash version

view details

push time in 8 days

PR opened google/fscrypt

cli-tests/t_lock: fix failure with latest bash version

The bash error message now starts with "bash: line 1: " instead of just "bash: ", which breaks the comparison with the expected output. Make the test use 'touch' instead.

+2 -2

0 comment

2 changed files

pr created time in 8 days

create barnchebiggers/fscrypt

branch : cli-test-fix

created branch time in 8 days

delete branch ebiggers/fscrypt

delete branch : troubleshooting

delete time in 8 days

push eventgoogle/fscrypt

Eric Biggers

commit sha a3b365be9878b14fd36cc310d3c8b1fdccfdcb04

README: add troubleshooting section for ENOPKG error Inspired by https://reddit.com/r/linuxquestions/comments/n75dv4

view details

push time in 8 days

PR merged google/fscrypt

README: add troubleshooting section for ENOPKG error

Inspired by https://reddit.com/r/linuxquestions/comments/n75dv4

+17 -0

0 comment

1 changed file

ebiggers

pr closed time in 8 days

push eventebiggers/fscryptctl

Eric Biggers

commit sha 0b6950bfc3f4e8700fa281e1373082cd7a5c0a16

Add a man page for fscryptctl Add a manual page for fscryptctl, documenting all subcommands and options. The page is written in Markdown and is translated to groff using pandoc.

view details

Eric Biggers

commit sha 676469b3e86ae2db280e3d8902d4a73d023b6439

Mention the man page in `fscryptctl --help` output

view details

push time in 8 days

push eventebiggers/fscryptctl

Eric Biggers

commit sha ed852269f92bef11f7452d925345682a65dd6bb8

Mention the man page in `fscryptctl --help` output

view details

push time in 8 days

PR opened google/fscrypt

README: add troubleshooting section for ENOPKG error

Inspired by https://reddit.com/r/linuxquestions/comments/n75dv4

+17 -0

0 comment

1 changed file

pr created time in 8 days

push eventebiggers/fscrypt

Eric Biggers

commit sha add42b8fd53dabd267980da67638d7070b6c779a

README: add troubleshooting section for ENOPKG error Inspired by https://reddit.com/r/linuxquestions/comments/n75dv4

view details

push time in 8 days

push eventebiggers/fscrypt

Eric Biggers

commit sha 587d43b56417afd9c764c79d5efda61faafbf5d2

README: add troubleshooting section for ENOPKG error Inspired by https://reddit.com/r/linuxquestions/comments/n75dv4

view details

push time in 8 days

create barnchebiggers/fscrypt

branch : troubleshooting

created branch time in 8 days

delete branch ebiggers/libdeflate

delete branch : release

delete time in 10 days

created tagebiggers/libdeflate

tagv1.8

Heavily optimized library for DEFLATE/zlib/gzip compression and decompression

created time in 10 days

PR merged ebiggers/libdeflate

Release v1.8
+235 -204

0 comment

5 changed files

ebiggers

pr closed time in 10 days

push eventebiggers/libdeflate

Eric Biggers

commit sha 8efdabddaea177a9b9766da82754b2eb1be87455

Convert NEWS file to markdown

view details

Eric Biggers

commit sha 047aa84e01b38d82f3612810e357bd40f14a3d39

v1.8

view details

push time in 10 days

PR opened ebiggers/libdeflate

Release v1.8
+235 -204

0 comment

5 changed files

pr created time in 10 days

create barnchebiggers/libdeflate

branch : release

created branch time in 10 days

issue commentsystemd/systemd

RFE: systemd-homed: support v2 fscrypt policies that do not require keyring inheritance for access

I think they wanted to rework this, adding a mode that makes no weird keyring restrictions like that. Not sure where that went though. So it appears this is fscrypt v2 policies that work without the keyring and they have been merged into the kernel. Hence, converting this into an RFE issue for homed.

For the record, v2 encryption policies had already been implemented and released prior to systemd-homed being merged, as I mentioned on the original systemd-homed request (https://github.com/systemd/systemd/pull/14096#discussion_r355036704). Also prior to the merge, I mentioned (https://github.com/systemd/systemd/pull/14096#discussion_r356763491) the issues that will arise if v1 is used, including encrypted files not working in containers. So this shouldn't be surprising --- choose to use the old broken API instead of the new one which was specifically designed to fix the problems with the old one, and things will be broken :-(

justinfenn

comment created time in 11 days

created tagebiggers/wimlib

tagv1.13.5-BETA1

Mirror of git://wimlib.net/wimlib: Library supporting the Windows Imaging Format (WIM). Please file issues on the official forums (https://wimlib.net/forums/viewforum.php?f=1) rather than here.

created time in 14 days