-
Notifications
You must be signed in to change notification settings - Fork 686
Standup Notes 2018 07 05
Participants (alphabetical): Conor, Emmanuel, Erik, Freddy, Harris, Jen, Kushal, Mike, Mickael
Today: Qubes docs. One substantive issue: minimizing admin grants. Will work with Josh to scope that a bit more. Just for staging, dev env is a separate ticket.
Blockers: Pending Josh availability,
Yesterday: Had to reset dev env on my Linux machine, focused on SD support
Today: ^^
Blockers: None
Yesterday: Finished up clickable wireframes for minimal workstation client UI ( https://eloquence.github.io/workstation/ ) , closely modeled after current UI.
Today: Clickable wireframes for advanced client UI, thinking beyond current UI (e.g., incorporating submission management features).
Blockers: None, but comments on wireframes welcome here: https://github.com/freedomofpress/securedrop-workstation/issues/102
Yesterday:
Today: Working on SD.org API
Blockers: None
Yesterday: Made changes to the API based on comments
Today: ^^, look in more detail at the wireframes, merge in passlib
Blockers: None
Today: Will be in SF office directly after meeting, will be working on permissions stuff that he was mentioning. Staging will be in good shape.
Yesterday:
Today: Updated 3488, pointed to branch that I'm currently working on. Tor-based tests are mostly working on an external server. Found issue on my workstation.
Blockers: 3488
Recompiled grsec kernel and it went fine. Created PR
Yesterday: Infra tests this morning
Today: Helping out Kushal
Blockers: None
Yesterday: Pushed work in progress branch for grsec kernel and some basic tests for SD workstation. Running into some issues decrypting files and not sure it's related.
Today: Wrapping up package
Blockers: None
- grsec recap from Mickael: Managed to get kernel compiled, working as template VM inside Qubes. Managed to provision svs disp VM to use grsec enabled template. The big question that is remaining is how we will ship the grsec template to the workstation. The best option seems to be the Qubes builder, provisioning via dom0. There's also the possibility to do it at build time. Open questions of how we are going to manage the different applications that will be running in this VM: some will require PAX flags (e.g., LibreOffice). Can be managed as part of the build process.