intrigeri wrote (17 Dec 2013 17:13:41 GMT) :
I've just released Tails-IUK 0.13, that fixes all coding tasks left
for phase three. I'm giving it a manual testing session as we speak.
Please use this version (or later) for any further testing,
documentation work and comments.
From now on,
On Tue, Dec 17, 2013 at 08:36:29PM +0100, intrigeri wrote:
Hi,
berta...@ptitcanardnoir.org wrote (17 Dec 2013 18:10:18 GMT) :
Congrats, I'm excited to see this coming in the wild!
:)
... and I'm scared to discover the remaining bugs we've missed :]
Next steps:
* bertagaz
On Tue, Dec 17, 2013 at 06:13:41PM +0100, intrigeri wrote:
Hi,
I've just released Tails-IUK 0.13, that fixes all coding tasks left
for phase three. I'm giving it a manual testing session as we speak.
Please use this version (or later) for any further testing,
documentation work and
Hi,
berta...@ptitcanardnoir.org wrote (17 Dec 2013 18:10:18 GMT) :
Congrats, I'm excited to see this coming in the wild!
:)
... and I'm scared to discover the remaining bugs we've missed :]
Next steps:
* bertagaz reviews feature/incremental-upgrades-integration (but does
not merge it
intrigeri:
Sounds good, did I miss anything?
I would suggest including a small shell script and one utility to test
the integrity of a tails release - something as simple as md5deep. Once
we start to change the Tails disk, we really want to ensure that an
attacker can't stick around past a
