Re: [Tails-dev] Persistent storage creation accessibility issues with Orca
Hi There, Thanks so much for taking the time to respond. I assume without being able to access the persistent storage features, there is no other way to store PGP keys - perhaps the most important thing I was hoping to do. I mean, changing personalized settings from their defaults is a miner inconvenience, but I was hoping to at least be able to store keys. If not I will just have to wait until next year *sigh*. Thanks again. Cory > On May 2, 2019, at 12:11 PM, intrigeri wrote: > > Hi Cory, > > sorry for the delay… > > Cory Samaha: >> I emailed the Orca screen reader list today with a query regarding >> the accessibility of the persistent storage volume creation tool. >> While I do see a bug that seems somewhat related on Redmine Bug >> #7503, it seems that this only refers to error messages. >> In contrast, I couldn’t get any portion of this tool to read with >> Orca, never mind the error messages. > > Thanks for your report. I've updated our #7503 ticket so it now > reflects better the status quo. It's not easy to solve but we plan to > fix this next year, as part of porting Tails to Wayland. > >> Also, while we are on the subject of Tails accessibility with Orca, >> I tried to use the auto update tool (I believe called senity) to >> update from 3.12 to 3.12.1. Unfortunately, this tool does not seem >> to read either. > > Thanks again. I've reported this as #16685, which we'll fix at the > same time as the other problem. > >> When trying to subvert the GUI and run >> tails-upgrade-frontend-wrapper from terminal, I did get >> a notification that an update was available, immediately followed >> by the text **WARNING **: Couldn't connect to accessibility bus. >> While it seemed that I could type “Upgrade now" or “Upgrade later”, >> it dumped me back into the graphical interface which, again, does >> not read with Orca. > > Indeed, there's no way to interact with the Upgrader in a terminal :( > >> I’m just trying to figure out if this is an issue with Orca or the >> way Tails is developed > > It's due to poor design decisions I made while developing some parts > of Tails years ago. > > Cheers, > -- > intrigeri ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Persistent storage creation accessibility issues with Orca
Hi Cory, sorry for the delay… Cory Samaha: > I emailed the Orca screen reader list today with a query regarding > the accessibility of the persistent storage volume creation tool. > While I do see a bug that seems somewhat related on Redmine Bug > #7503, it seems that this only refers to error messages. > In contrast, I couldn’t get any portion of this tool to read with > Orca, never mind the error messages. Thanks for your report. I've updated our #7503 ticket so it now reflects better the status quo. It's not easy to solve but we plan to fix this next year, as part of porting Tails to Wayland. > Also, while we are on the subject of Tails accessibility with Orca, > I tried to use the auto update tool (I believe called senity) to > update from 3.12 to 3.12.1. Unfortunately, this tool does not seem > to read either. Thanks again. I've reported this as #16685, which we'll fix at the same time as the other problem. > When trying to subvert the GUI and run > tails-upgrade-frontend-wrapper from terminal, I did get > a notification that an update was available, immediately followed > by the text **WARNING **: Couldn't connect to accessibility bus. > While it seemed that I could type “Upgrade now" or “Upgrade later”, > it dumped me back into the graphical interface which, again, does > not read with Orca. Indeed, there's no way to interact with the Upgrader in a terminal :( > I’m just trying to figure out if this is an issue with Orca or the > way Tails is developed It's due to poor design decisions I made while developing some parts of Tails years ago. Cheers, -- intrigeri ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Kloak and Keyboard Biometrics
Hi Justin, Justin McAfee: > Regardless, I have been reading white papers on styleography and keystroke > biometrics and have found a fairly elegant solution from vmonaco's github > page. > Would like to propose that we include the "kloak" program as a feature in > the next Tails release. This software assists in combating keystoke > biometrics by inserting brief (100-200ms) delays between keystrokes, faking > out matching algorithms. Thank you for this suggestion. This project¹ seems pretty serious and points to actual research (that I didn't read yet). That's confidence inspiring. We'll need to discuss about the usability trade-off though. May you please get back to us once this project is not marked as experimental anymore and the most severe issues (e.g. #12²) are fixed? [1] https://github.com/vmonaco/kloak [2] https://github.com/vmonaco/kloak/issues/12 Cheers, -- intrigeri ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [review'n'merge] typo on unlock_veracrypt_volumes
Hi! On 29.04.19 18:21, intrigeri wrote: > sajolida: >> I've seen no answer to your email on tails-dev. > >> Foundations Team, should this be part of your mission? as per: >> « reviewing code contributions that are on nobody else's plate [...] » > > It definitely is part of our job. segfault asked me for guidance > a couple weeks ago wrt. how to handle this and I replies. I suspect > this fell through the cracks since. segfault, are you still on it? > > (As we can see, email is slightly suboptimal to track such things.) Maybe emmapeel can create a ticket on Redmine? Cheers! u. ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
