-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client integration #194
Client integration #194
Conversation
3e4ebd9
to
4dddeaf
Compare
LGTM, rebased on latest master and fixed securedrop-client dependency name. |
just tested this, working well in sd-svs, confirmed |
OK on top of the latest debs I can confirm I can sign into a staging server via the client (I hit an error due to a database migration that we forgot in freedomofpress/securedrop-client#114, but I added that in https://github.com/freedomofpress/securedrop-client/pull/129/files which was merged this morning, so tomorrow AM we can do another |
Worked for me! That is, I also encountered the app crash after logging in. Error messages were accurate when I provided bad credentials. |
* sd-journalist will now be used mostly for securedrop-proxy * sd-svs will now be used to host the securedrop-client
thanks for adding the docs updates @emkll, they LGTM! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just did a clean reinstall on this branch, and submissions decrypt successfully in the client 🎉 .
I did, however, experience an error (see image below). This error occurs every time I open the client. One of my sources is encrypted to a different GPG key, which might be the cause. I will validate this assumption and open a ticket.
good QA 🥇 , let's open a followup ticket to track this, thanks @emkll |
Close #179
Let's do sd-journalist -> sd-proxy rename in a followup