Brady Trainor
Brady Trainor
This is all on macOS. I just tested on a Debian VPS, and I simply get `Handshake failed. Error in the certificate.` for `taskd.server=app.wingtask.com:53589`, no matter what I put in...
Upgraded Debian VPS task to 2.6.1. With invalid client PEM files, I can confirm the behavior with WingTask, `Cannot perform this action while handshake is in progress.`.
With other taskd servers, with invalid client PEM files, I see the following error: ``` > gnutls-cli --x509keyfile --x509certfile ... *** Fatal error: Error in the pull function. *** Server...
I ran git bisect with the following scenario: - taskd - running on localhost - `TASKDDATA=./var/taskd taskd server --debug` - taskd client - implemented in Dart - client PEM files...
Tried with `faketime '2000-01-01'` tool to generate expired client PEM files, and still allowed to connect to taskd. So I think this clarifies that these certs should not be trusted...
@jakec-dev, I presume you are running a recent build of 1.2.0, not current stable 1.1.0. The issue I filed above is about taskd behavior when using invalid client PEM files....
I was able to reproduce the issue with just Taskwarrior stable, and the same git bisect commit I reported above. I created a deliberately invalid pair of client PEM files,...
In summary, changes in behavior with invalid client PEM files, regarding commit fb5fbe9ac76c0cd838bfa2ffa52e3ba34f75b70d: - Before: - Taskwarrior: - The specified session has been invalidated for some reason. Sync failed. Could...
Interestingly, Inthe.am is at taskd 1.1.0 (according to request with `type: statistics`), and with invalid client PEM files returns: ``` Cannot perform this action while handshake is in progress. Sync...
Behavior of Dart client is similar as Python client. I tested with https://github.com/jrabbit/taskd-client-py, and found behavior before commit fb5fbe9 was: ``` Traceback (most recent call last): File "main.py", line 3,...