p - Gitea: Git with a cup of tea

p pushed to main at p/hedgedoc-exporter

181f45d92f add readme and requirements file

3 months ago

p created branch main in p/hedgedoc-exporter

3 months ago

p pushed to main at p/hedgedoc-exporter

5f2ddd562a add scraped pages
2170046d2c scrape all markdown from hedgedoc wiki
202dfc2902 initialize scrapy project

3 months ago

p created repository p/hedgedoc-exporter

3 months ago

p commented on issue p/signal_group_analysis#3

Run failure: get_decryption_key

whoops I gave you the path for a linux system. git pull; ./build.sh; ./run.sh -c ~/Library/Application\ Support/Signal -p peanuts

5 months ago

p commented on issue p/signal_group_analysis#3

Run failure: get_decryption_key

ok I fixed a stupid bug I introduced dealing with the default `peanuts` key. if you feel like running this one-liner one last time and seeing if there's any error git pull; ./build.sh;…

5 months ago

p pushed to main at p/signal_group_analysis

11d3aea0d4 fix bug handling default "peanut"-encrypted encryptedKey

5 months ago

p pushed to main at p/signal_group_analysis

b7c1b7a189 fix bug handling default peanut-encrypted encryptedKey

5 months ago

p opened issue p/signal_group_analysis#4

add v10/peanuts handling earlier in exectuion

5 months ago

p commented on issue p/signal_group_analysis#3

Run failure: get_decryption_key

wait a sec!! you've got the v10 prefix! v10 - means that the hard-coded key "peanuts" was used to encrypt the string, which is used as a fallback on Linux systems where the keyring or other…

5 months ago

p pushed to main at p/signal_group_analysis

f7c733c2a1 detect default peanuts encryption key

5 months ago

p commented on issue p/signal_group_analysis#3

Run failure: get_decryption_key

ok that means that after decoding from a hex string to byes the password does not start with v11 as expected. I dropped the error and made it just print a warning instead now, but I'm not super…

5 months ago

p pushed to main at p/signal_group_analysis

5c3ff994b5 warning instead of failure when password doesn't start with v11

5 months ago

p pushed to main at p/signal_group_analysis

452b39fc88 update docs on safestorage password option

5 months ago

p pushed to main at p/signal_group_analysis

4fe191b65d update docs on safestorage password option

5 months ago

p commented on issue p/signal_group_analysis#3

Run failure: get_decryption_key

somebody already wrote it for me! https://gist.github.com/flatz/3f242ab3c550d361f8c6d031b07fb6b1 if you pull and build now you should be able to do ./run.sh -c ~/Library/Application\…

5 months ago

p pushed to main at p/signal_group_analysis

c9d326e926 add option to let user add password to decrypt db key

5 months ago

p commented on issue p/signal_group_analysis#3

Run failure: get_decryption_key

oh wait I think the prefix would actually appear in the config.json `encryptedKey` entry

5 months ago

p commented on issue p/signal_group_analysis#3

Run failure: get_decryption_key

@lp does the password stored in your keychain have the v11 prefix?

5 months ago

p commented on issue p/signal_group_analysis#3

Run failure: get_decryption_key

the problem is that as far as I understand it, the process would look like this: ``` metaKey = getSignalSafeStorageKeyFromKeychain() ciphertext = getCipherTextFromSignalConfigFile() dbEncrypt…

5 months ago