Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v1.7.1 2024-09-04T12:30:59+00:00 2024-09-04T12:30:59+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-09-04T07:04:48+00:00 urn:sha1:949c6459aa7683453a7160423b689ceadb08954b the make the code more readable this commit just moves the files, the next commit should fix the imports 2024-06-24T08:39:18+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-06-24T08:39:18+00:00 urn:sha1:173ab188b326fbe78cfba4ab455a74619f4556bb replace ngit yaml file config with: * nsec / ncryptsec / npub in git config in nostr.* namespace * sql database cache for metadata and relay events allow different logins to be used for different git repositories by storing login in local git config 2024-06-11T11:33:09+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-04-18T06:39:27+00:00 urn:sha1:7c6a5ab4c5e7a81c7442061029b9230748a6639d bump nostr and nostr-sdk packages and also in test_utils remove custom ncryptsec implementation and use the newly added implementation nip49 version in rust-nostr note a patched v0.30 is used so that log_n is exposed so that user can be warned it might take a few seconds to decrypt. this has now been merged into the library. note that this will no longer decrypt existing ncryptsec values as it is uses a longer string. this should therefore be bundled with the upcoming change to storing nsec and ncryptsec in git config. 2024-03-22T15:51:34+00:00 DanConwayDev DanConwayDev@protonmail.com 2024-03-22T15:51:34+00:00 urn:sha1:0d7a8383d7d54e64bb0e1d5f4e06110c1e6a818b to reflect new name in rust-nostr 2023-09-01T00:00:00+00:00 DanConwayDev DanConwayDev@protonmail.com 2023-09-01T00:00:00+00:00 urn:sha1:96660a90e4cd296a2922d7a547de4cd9d0b1928b Enables the user to only handle the nsec upon first use of the tool by encrypting it with a password and storing it on disk in an application cache. The approach to encryption draws heavily from that used by the gossip nostr client. - unencrypted nsec is zeroed from memory - a salt is used to defend against rainbow tables - computationally expensive key stretching defends against brute-force attacks of passwords with low entropy. There is UX trade-off between decryption speed and key-stretching computation. This UX challenge is exacerbated in a cli tool as decryption must take place more regularly. Thought was put into the selected n_log and a heavily reduced value is provided for long passwords where security benefits are smaller. A more granular reducing in computation was also considered by rejected to avoided to revealing just how weak a password is as most weak passwords are reused.