Re: [Tails-dev] Tails-greeter UI redesign

2012-10-06 Thread alan

> From: sajol...@pimienta.org
> Date: Fri, 5 Oct 2012 13:15:01 +0200

> On 04/10/12 21:21, a...@boum.org wrote:
> > 
[...]
> > 
> > or better clone the git, go to the directory and:
> > 
> > $ ./mockup.py [-v ] [-p]
> 
> I'm excited about see that!
> 
> I was not able to find the mockup.py script in Tails Greeter repository.
> Where is it?
> 
In amnesia's master:

   wiki/src/todo/tails-greeter:_revamp_UI/mockups/

Sorry for the unclearness,

Cheers


-- 


pgp4zat44AQBr.pgp
Description: PGP signature
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev


[Tails-dev] MAT

2012-10-06 Thread alan

To: tails-dev@boum.org, julien.voi...@dustri.org

Hi,

MAT[1] maintainer Julien Voisin didn't answer our emails since June.
This has until now prevented us to fix bugs and release improvements to
this application we ship in Tails.

I propose to carry on maintaining MAT in the interim. I propose the
following plan:

- ask boum.org for a mat-dev mailing list which would act as the point
  of contact for MAT development;
- ask boum.org (on behalf of the Tails team) to be able update the
  website;
- ask torproject.org (on behalf on the Tails team) to get write access
  to the git repository.

What do you think?

Cheers

[1]. https://mat.boum.org/


-- 


pgp4NCcQk0UDT.pgp
Description: PGP signature
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev


Re: [Tails-dev] MAT

2012-10-06 Thread intrigeri
a...@boum.org wrote (06 Oct 2012 13:25:20 GMT) :
> What do you think?

Full ACK.

Cheers,
-- 
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev


[Tails-dev] Please review and merge feature/usb_installer

2012-10-06 Thread intrigeri
Hi,

it brings that (mainly l10n + a bug discovered when testing with
64-bit kernel):

liveusb-creator (3.11.6-3) unstable; urgency=low

  * Update link to local documentation.
  * Update Qt resource files.
  * Update POT and PO files.
  * Imported updated pt_BR translation.
  * Use typed empty arrays when calling DBus methods

 -- Tails developers   Sat, 06 Oct 2012 19:06:45 +0200

Cheers,
-- 
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev


[Tails-dev] Please review and merge feature/multikernel

2012-10-06 Thread intrigeri
Hi,

please review, test and merge the feature/multikernel branch,
candidate for Tails 0.14.

Ticket: todo/nx_bit

This branch boots a 686-pae kernel on hardware that supports it, and
a 486 kernel else. It therefore brings to hardware that supports it:

  * NX bit
  * multiple CPU cores (usage and power-saving)
  * big memory support

(Yay.)

In case you wonder:

  * Shipping an amd64 kernel was postponed due to the VirtualBox guest
additions incompatibility with 32-bit userspace and 64-bit
kernel environments.

  * Wiping memory with kernel's memtest was postponed too, since it's
less efficient than our current sdmem setup as long as 32-bit
kernels are used (yeah, we could ship a 64-bit kernel dedicated to
be kexec'd for memtest use -- later).

  * The USB installer vs. non-486 kernel crashes are fixed by Ague's
patched python-dbus bindings (tested on various hardware today),
but another shiny new bug was discovered in the process, that
(most likely) used to be previously hidden by the crashes
(so basically, feature/usb_installer should be merged *first*:
see separate review & merge request).

I'll split that into individual tickets once the branch is merged.

Enjoy!

Cheers,
-- 
  intrigeri
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev


[Tails-dev] Please review the documentation of gpgApplet

2012-10-06 Thread sajolida

Today I worked on the documentation of the new Tails gpgApplet. (I
wondered whether giving it a name without camel case.)

You can find most of the work in commits 1c3c5bc..94e4fb4, but those are
a bit hardcore so you might rather look directly at the result on those
four pages:

[1] /doc/encryption_and_privacy/gpgapplet
[2] /doc/encryption_and_privacy/gpgapplet/passphrase_encryption
[3] /doc/encryption_and_privacy/gpgapplet/public-key_encryption
[4] /doc/encryption_and_privacy/gpgapplet/decrypt_verify

I have a couple of questions and bug reports, though.

First, I was wondering about the warning "message was not integrity
protected" when using passphrase encryption. Does it always appears? Is
there no way of providing integrity when using a passphrase? See what
I'm saying about it on line 73 of
/doc/encryption_and_privacy/gpgapplet/decrypt_verify.mdwn

Then, I'm still sticking to documenting Tails gpgApplet and not
documenting more generally OpenPGP or GnuPG in Tails (Seahorse, Claws
mail, etc.) so for example I'm not mentioning the “Manage keys” feature.
Tell me if I should and I will. By the way the menu item “Manage keys”
is not capitalized as the others.

And now the bug reports:

1. When decrypting a text encrypted using passphrase encryption, if you
enter a bad passphrase you have to select the text again to try another
passphrase. The encrypted text should be kept in the clipboard even if
the given passphrase is bad, no?

2. When encrypting using several public keys that are not trusted, the
warning message only mentions one. It should either mention each key in
a separate dialog box, or all of them in a single dialog box.

On the same topic, shall I explain that this message appears when keys
are not signed by the user, and how they can sign them? I would say this
is off-topic for now.

3. I found two phrases of the GUI that need to be rephrased.

“Here is the GnuPG output:” → “Output of GnuPG:”

See GDP [5]: 4.3 How to Write for Translation, Topic 13
« Replace the genitive construction with an of structure. »

“While it were at it, GnuPG also mentionned in passing:” → “Other
messages provided by GnuPG:”

See GDP [5]: 1.3 Tone
« Avoid colloquial language. Colloquial language is difficult to
translate and usually culture-specific. Stay neutral. »

[1]
http://git.immerda.ch/?p=amnesia.git;a=blob;f=wiki/src/doc/encryption_and_privacy/gpgapplet.mdwn;h=ab177237705a91849462cb82c21f55bd7bfe184b;hb=refs/heads/feature/assymetric_gpgApplet

[2]
http://git.immerda.ch/?p=amnesia.git;a=blob;f=wiki/src/doc/encryption_and_privacy/gpgapplet/passphrase_encryption.mdwn;h=0d27a7bf7a134d461744fe397f0cb0a4c78aa77d;hb=refs/heads/feature/assymetric_gpgApplet

[3]
http://git.immerda.ch/?p=amnesia.git;a=blob;f=wiki/src/doc/encryption_and_privacy/gpgapplet/public-key_encryption.mdwn;h=77f2edffcae8e9084472879aa6d1ea7aeed152f5;hb=refs/heads/feature/assymetric_gpgApplet

[4]
http://git.immerda.ch/?p=amnesia.git;a=blob;f=wiki/src/doc/encryption_and_privacy/gpgapplet/decrypt_verify.mdwn;h=33a6f7dc30f661ed9e0fbe4ae5e208e945518cb4;hb=refs/heads/feature/assymetric_gpgApplet

[5] http://developer.gnome.org/gdp-style-guide/stable/



signature.asc
Description: OpenPGP digital signature
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev