aboutsummaryrefslogtreecommitdiffstats
path: root/src/bin/rbw-agent/agent.rs
Commit message (Collapse)AuthorAgeFilesLines
* clippyJesse Luehrs2024-04-201-6/+1
|
* clippyJesse Luehrs2023-07-201-10/+16
|
* Fallback to the nop clipboard provider.Benjamin Jacobs2023-07-201-4/+15
|
* more correct websocket notification handlingJesse Luehrs2023-07-191-19/+16
| | | | | | | | | | the servers tend to be fairly chatty with messages, mostly pings and heartbeats of various sorts, and we don't want to sync on all of those. also, the message type in the first array element of the messagepack structure is not the same thing as the UpdateType - that is stored as an argument to the ReceiveMessage invocation, so we need to parse a bit further to get the actual UpdateType. this still just does a full sync on any changes, though.
* reconnect to websockets after every successful syncJesse Luehrs2023-07-181-20/+5
| | | | rather than scattering it around various parts of the code
* stop trying to reconnect to notifications so aggressively1.8.0Jesse Luehrs2023-07-181-18/+13
| | | | it adds a bunch of latency to every command otherwise
* make clipboard manipulation happen from the agentJesse Luehrs2023-07-181-8/+18
| | | | | | | | | on x11 systems, you can't just send data to the os to store on the clipboard, you just register which application currently owns the clipboard and then other applications can use ipc to request the owning application to send them the clipboard data. this requires there to be an application still running in order to respond to those requests. luckily, we have one of those available in the form of the agent.
* clippy and fmtJesse Luehrs2023-07-161-22/+22
|
* Cargo format and reconnect websocket on syncBernd Schoolmann2023-04-271-22/+44
|
* Improve error logging for websocketsBernd Schoolmann2023-04-271-1/+4
|
* Fix panic when websocket endpoint is not availableBernd Schoolmann2023-04-171-1/+1
|
* Restructure codeBernd Schoolmann2023-04-161-10/+26
|
* Implement basic websocket supportBernd Schoolmann2023-04-081-0/+11
|
* sync the db every hour, like other bitwarden clientsJesse Luehrs2023-03-251-1/+31
|
* stop using tokio::select!Jesse Luehrs2023-03-251-53/+38
|
* clippyJesse Luehrs2023-02-181-5/+4
|
* clippyJesse Luehrs2021-12-151-7/+3
|
* add a separate "register" command to log in with api keysJesse Luehrs2021-10-271-16/+5
|
* start working on apikey authenticationJesse Luehrs2021-10-271-2/+17
| | | | | | | | | | not entirely working yet, because api keys aren't allowed to use the offline_access scope which provides access to the oauth refresh token. we will probably need to move to using stable device identifiers (should be able to generate one when the config is first created) and move this logic to a separate "rbw register" command which just does an apikey login but doesn't try to store any data, and then use the normal login flow after that
* clippyJesse Luehrs2021-10-271-2/+2
|
* upgrade to tokio 1.2Jesse Luehrs2021-03-021-9/+9
|
* implement rbw unlockedJesse Luehrs2020-07-251-0/+9
|
* remove more unnecessary error contextsJesse Luehrs2020-05-251-9/+3
|
* fix unlocking org keys on initial loginJesse Luehrs2020-05-031-4/+5
|
* expand the protocol to allow decrypting with organization keysJesse Luehrs2020-05-021-5/+29
| | | | not implemented yet, just changing the interface
* check protocol version before agent communicationJesse Luehrs2020-05-021-0/+4
|
* don't kill the agent if it fails to parse a messageJesse Luehrs2020-05-021-0/+9
|
* add encryption to the agent protocolJesse Luehrs2020-04-181-0/+4
|
* drop timeout due to tokio limitationsJesse Luehrs2020-04-181-1/+2
|
* fix private key timeout handlingJesse Luehrs2020-04-121-18/+73
|
* rename some stuff to be less confusingJesse Luehrs2020-04-121-7/+7
|
* improve error handling and reportingJesse Luehrs2020-04-121-11/+31
|
* don't block the main loop on timer eventsJesse Luehrs2020-04-111-1/+4
|
* also refactor the agent codeJesse Luehrs2020-04-111-0/+74