-
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
coordination with upstream Whonix #451
Comments
hey @adrelanos! so we don't have securedrop workstation deployed anywhere yet, the plan right now is mid-March for an initial beta release where we'd install in prod for a few news organizations for testing and feedback. thanks for flagging the many changes approaching - before our prod release next month we should definitely ensure that we do some basic testing of our workstation code with whonix testers or stable-proposed-updates. we can do this at first manually and then we can investigate modifying the dev/staging envs in this repository such that SecureDrop workstation developers and testers would find issues early (we do something similar with Tails before a SecureDrop release, we perform pre-release testing on the Tails release candidates when available to catch any issues). |
@adrelanos Are you aware of the If you're up for it, it may be useful for you, @ninavizz, myself and other interested/relevant parties from Whonix/SD to have a call about the user experience of that system tray widget; right now there are IMO a lot of usability issues with it, and working together, we may be able to identify some low hanging fruit improvements beyond bugfixes. (Thanks again for making this issue!) |
About ~ 2 weeks ago I received the e-mail from @ninavizz (cc'd was @eloquence) and replied shortly after and re-send a week later or so. Just wondering, did you receive my reply or perhaps it was lost in some spam filter or something? |
Just reply related to sdwdate-gui so anyone else who's reading here can follow. This was also posted and discussed a bit here: Yes, a call would be possible. To avoid (potential) e-mail issues, @marmarek or anyone are welcome to share my mobile number and other messenger account names for this purpose. |
On reflection, probably best to test using Whonix testers repository. Not Whonix stable-proposed-updates. That is because #491 wasn't caught by any Whonix testers and then fixes take yet longer to hit stable-proposed-updates or stable. |
Whonix recently added (in stable) drop-in configuration snippet support for folders I've also worked on making authenticated v3 onion services easier to use. That could use some feedback on that design.
You might also find |
We haven't hit any breaking issues with Whonix so far (Tor weather lately has caused the occasional update issue but that's not related). Closing this for now, will revisit once we have a better overall plan for automation of Qubes testing. |
Is securedrop-workstation deployed live anywhere yet?
Reason I am asking, there are significant changes in Whonix testers repository which will then flow to stable-proposed-updates repository and then flow to stable repository. I would like to avoid any upgrades bricking [1] running instances.
There is also a Q/A issue. And lack of automated testing, though it is getting better.
Therefore if this is deployed live, I'd suggest to run tests using Whonix testers repository or stable-proposed-updates repository. Some sort of coordination. If you'll find any grave regressions, then it would still be time to fix these before upgrades flow to Whonix stable repository.
Maybe there are other opportunities for coordination with upstream Whonix. Just keeping this kinda brief as a dialog starter.
[1] Brick loosely, quickly defined as: grave issues such as no longer bootable, no longer upgradeable, broken connectivity at least not without manual fixes.
The text was updated successfully, but these errors were encountered: