IRC Channel #tails Gateway Report
From: Mar. 22, 2014 To: Mar. 28, 2014

---------------------------------------------
*** Tor-dev BRAINSTORMING SESSION on #tails
---------------------------------------------

Developers/High value persons involved: alster, velope, isis, arma

Subject: obfs3 bridges, obtaining bridges, fingerprints and
how they relate to usability, other usability issues discussed

/!\ Tickets were written for Tor (not sure about Tails) /!\

A password *quality* monitor was proposed for the Tails greeter
set admin password dialog

Some kind of *notification* that bridge information wasn't input
correctly or was in error was proposed for the Tails greeter

------------------------------------
*** Documentation and Website:
------------------------------------

There where a few questions regarding using gpg and
seahorse and how to do email encryption in general,
users seem confused about creating keys, storing keys,
importing/exporting keys, etc. especially with seahorse 
since that's the most accessable user application for 
interacting with gpg

-----------------------------------
*** Call for testing:
-----------------------------------

<< no comments >>

-----------------------------------
*** Issues:
-----------------------------------

1 report Archive Manager in 0.23 doesn't open password
protected rar archives, which it did in 0.22.1 before
user upgraded to 0.23

----------------------------------
*** Known Issues:
----------------------------------

<< no comments >>

----------------------------------
*** Features:
----------------------------------

<< no comments >>

----------------------------------
*** Potential FAQ questions:
----------------------------------

<< no comments >>

----------------------------------
*** Miscellaneous:
----------------------------------

<< no comments >>




--Cheers!
_______________________________________________
tails-support mailing list
[email protected]
https://mailman.boum.org/listinfo/tails-support
To unsubscribe from this list, send an empty email to 
[email protected].

Reply via email to