| Age | Commit message (Collapse) | Author |
|---|
|
the make the code more readable
this commit just moves the files, the next commit should fix the imports
|
|
This reverts commit 3d2e031294b467be725a4ac5f5e65e029d25699a.
|
|
as `stderr` is being used when it shouldn't be
|
|
if no previous state events can be found it replicates git server
otherwise it just updates pushed value
|
|
bump all rust-nostr packages
move from using patched nip46 nip05 function to profile function in v33
fix send_events_to error message
|
|
when fetching a user profile from user relays it throw an error
when an existing version of the profile wasn't found
|
|
rather than as new profiles
|
|
add the ability to fetch more than just the current user from
their user write relays
|
|
only the profile from the saved user was being fetched.
tests are using cli login parameters and expecting to see the
user's name but it was only showing the npub.
fixed by allowing the explicit request of specfic user profiles.
|
|
fetch automatically gets updates to logged in user profile / relays
fetching without specifying repo pointers will just fetch user
profiles so that can be used during login, if user profile isn't
in cache
login now uses fetch
|
|
a typo prevented fetching of saved bunker-uri and therefore ngit
would act as if it wasn't saved
|
|
currently using patched version of rust-nostr with function to fetch
nip46 relays from nip05 providers. this patch has been merged so it
will make it into the next rust-nostr release.
|
|
and save details in git config
|
|
so that nip46 bunker signing can be added
|
|
ensure fresh global cache when under test conditions by conditionally
storing it in local ./git folder
|
|
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
|
|
to reflect new name in rust-nostr
|
|
it wasn't clear why no results were coming back from relays
or why it is needs (added reference to relay updates)
|
|
so that changes to relays changes can be picked up
|
|
reuse client across login and send events
|
|
get user relay list and metadata events from relays when keys are
used and last fetch attempt was more than an hour ago
uses user's write relays if known, otherwise uses fallback relays
to achieve this a method for intergration testing event fetching
from relays was added
|
|
add tests but these currently don't work when run together
|
|
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.
|
|
Create skeleton for a complete rebuild of the prototype as a production
ready product.
Includes design patterns for:
- dependency injection
- unit testing with dependency mocking
- integration testing
- error handling
- config storage
BREAKING-CHANGE: ground-up redesign with incompatible protocol standards
|