Re: [Tails-dev] gimp-ufraw

[intrigeri]

Hi,

Eirik Rønneberg wrote (13 May 2014 10:55:49 GMT) :
> The following NEW packages will be installed:
>   gimp-ufraw libgtkimageview0
> 0 upgraded, 2 newly installed, 0 to remove and 3 not upgraded.
> Need to get 463 kB of archives.

IMO, looks small enough to install it, given the benefits.

Eirik: I suggest you create a new ticket called "Support UFRaw in the
Gimp" in our Redmine, with type of work = "Code". I think this would
be the perfect task for anyone willing to contribute their first patch
to Tails, in the "coding" area *and* who does not mind getting
themselves a Tails ISO build setup first.

If nobody catches this ball in the next few weeks, feel free to ping
us again and I'll just do it.

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
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] tor-launcher... without xulrunner

[intrigeri]

Hi,

xulrunner is being phased out. Iceweasel 30 betas in Debian don't ship
it anymore. We use it to run tor-launcher. We have to migrate away
from it before we move to Firefox 31 ESR.

Details: https://labs.riseup.net/code/issues/7236

Sorry for the bad news.

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
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] #5594: tails-greeter: better administration password UI

[Andres Gomez Ramirez]

Hi, 

oh I see, the part that asks for an obligatory password is not desirable, I got 
it.
But the patch is compound of two parts: one for obligatory password and other 
that checks for admin
password matching. I think this last part could be keep.

Cheers.

From: Tails-dev [tails-dev-boun...@boum.org] on behalf of intrigeri 
[intrig...@boum.org]
Sent: 13 May 2014 11:53
To: The Tails public development discussion list
Subject: Re: [Tails-dev] #5594: tails-greeter: better administration
password UI

anonym wrote (13 May 2014 09:45:43 GMT) :
> Given that the semantics of the fields are pretty different in the
> Greeter compared to in t-p-s, please provide a detailed description of
> how you think the Greeter should be changed in case you still think it's
> desirable.

I'll do this when I'm back, around May 24. So, I've dropped the 1.1
milestone from the ticket, reassigned to me, and marked as needing
more info.


___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] #5594: tails-greeter: better administration password UI

[anonym]

14/05/14 11:00, Andres Gomez Ramirez wrote:
> But the patch is compound of two parts: one for obligatory password
> and other that checks for admin password matching. I think this last
> part could be keep.

Sorry, but I don't get it. I've looked as best I can on the patch, and
the only other thing it does is to renaming the old "warning" stuff to
"warning_match", to be more consistent with the new "warning_empty". No
new functionality as far as I can see.

Am I mistaken?

Cheers!

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] #5594: tails-greeter: better administration password UI

[Andres Gomez Ramirez]

oh yes you are right, ok drop it all.

cheers.

From: Tails-dev [tails-dev-boun...@boum.org] on behalf of anonym 
[ano...@riseup.net]
Sent: 14 May 2014 13:01
To: The Tails public development discussion list
Subject: Re: [Tails-dev] #5594: tails-greeter: better administration
password UI

14/05/14 11:00, Andres Gomez Ramirez wrote:
> But the patch is compound of two parts: one for obligatory password
> and other that checks for admin password matching. I think this last
> part could be keep.

Sorry, but I don't get it. I've looked as best I can on the patch, and
the only other thing it does is to renaming the old "warning" stuff to
"warning_match", to be more consistent with the new "warning_empty". No
new functionality as far as I can see.

Am I mistaken?

Cheers!

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Manually Install Using Mac (without rEFInd)

[sajolida]

Scorpion:
> I just got off IRC with a problem, where noone seemed to be able to help
> me. However, people did ask me to email the way I created a bootable USB
> for Mac without having to install rEFInd on the host computer.
> 
> You will find the step-by-step instructions below. I will also post my
> problem, hoping someone involved in development and who is Mac savvy has a
> solution for me! At least, this may speed up problem solving a bit.
> 
> Currently, the only option provided on the website to manually install
> using Mac is here:
> https://tails.boum.org/doc/first_steps/installation/manual/mac/index.en.html-
> however, it requires rEFInd to be installed on the Mac computer,
> something people might not want. Instead, follow the steps below to create
> a bootable USB which can immediately be used. For this process, I used
> MacBook Air 6-1 (mid 2013).

Hi,

Thanks a lot for proposing those instructions.

Actually, the next version of Tails (1.1) will include support for UEFI,
and that will greatly improve the support for Mac, including without
having to install rEFInd.

See https://labs.riseup.net/code/issues/6242

Can you confirm that this would work?

If you want to test our experimental ISO images with UEFI support:

https://tails.boum.org/news/test_UEFI/

So the recommended workflow with Mac starting from 1.1 would be:

  - Bootstrap from DVD. This works without rEFInd, right?
  - Clone onto USB.
  - Enjoy.

Can you confirm this would work?

In that case, I'm tempted to move the instructions for manual
installation on Mac (/doc/first_steps/installation/manual/mac/) in the
"Advanced topics" section.

>- Download Tails ISO from the website, and copy it onto the desktop
>(keep the original somewhere safe).
> 
>- Download syslinux (
>
> http://ftp.debian.org/debian/pool/main/s/syslinux/syslinux_4.02+dfsg.orig.tar.gz),
>extract, and copy isohybrid.pl from the /utils folder to the desktop.
> 
>- Open Terminal (Applications > Utilities > Terminal.app)
> 
>- Change to desktop folder
> 
>- Type: cd desktop
> 
>- Type: perl isohybrid.pl *[tails.iso]*
> 
>- (replace *[tails.iso]* with the file name without [ ], or drag the
>file and drop on terminal window, to paste the path and file name)
> 
>- Convert ISO to Mac IMG
> 
>- Type: hdiutil convert -format UDRW -o *[target] [tails.iso]*
> 
>- (replace *[target]* with IMG name without [ ] (extension DMG will
>automatically be added), replace *[tails.iso]* with ISO name without [ ]
> 
>- If USB stick is plugged in, unplug it
> 
>- Type: diskutil list
> 
>- Plug in USB stick
> 
>- Type: diskutil list
> 
>- Determine the device node of the USB stick (e.g. /dev/disk2)
> 
>- Type: diskutil unmountDisk /dev/disk*N*
> 
>- (replace *N* with number of device node as seen after previous
>command, and don't remove USB stick after unmounting)
> 
>- Type: sudo dd if=*[target.dmg]* of=/dev/rdisk*N* bs=1m
> 
>- (Replace *[target.dmg]* with the image created earlier without [ ],
>replace *N* with number of device node -and note the rdisk- *ENTERING
>THE WRONG NUMBER MAY COMPROMISE YOUR MAC BOOT DISK!* You can also use
>disk instead of rdisk, but rdisk will be faster)
> 
>- If you see the error *dd: Invalid number '1m'* you are using GNU dd.
>Use the same command but replace *bs=1m* with *bs=1M*
> 
>- If you see the error *dd: /dev/diskN: Resource busy*, make sure the
>disk is not in use. Start the 'Disk Utility.app' and unmount (don't eject)
>the drive
> 
>- Wait until the prompt returns.
> 
>- Type: diskutil eject /dev/disk*N*
> 
>- (Replace *N* with number of device node. Remove USB stick, reboot Mac
>and hold alt/option key while the Mac is restarting. When you insert the
>USB stick, you should see a new disk which you can select and boot from it.
>However, on my computer it's called Windows for some reason (probably
>because I use BootCamp and have both Mac and Windows installed)

If I understand correctly, the main improvement in your instructions is
that you convert the ISO image to DMG using hdiutil, right? Then the
rest is basically the same (with some extra improvements), no?

So maybe we can add this as an option to the current instructions, once
we moved them to the "Advanced topics" section.

> The only problem I have is that WiFi won't work. Since the MacBook Air has
> no ethernet port, you can see how this poses a problem.

I'm not sure that's something we can solve. I think that some drivers
are not available in Linux yet.

> I tried installing drivers using the websites
> https://wiki.debian.org/InstallingDebianOn/Apple/MacBookAir/6-1 and
> https://wiki.debian.org/wl, but wireless-tools gives me an error regarding
> kernel headers not found, and on IRC people tell me I can't install any
> drivers. So if you have a solution to this little problem, that would be
> great! In the mean time, the links provi

Re: [Tails-dev] [review'n'merge:1.1] bugfix/7065-keyboard-localization

[anonym]

09/05/14 17:36, intrigeri wrote:
> Hi,
> 
> bugfix/7065-keyboard-localization fixes issue #7065 for me.
> Assigned to the RM (anonym) for review.
> 
> The solution I've found to this problem is partly implemented in the
> greeter, and partly in the main Git repo, so it'll require two Git
> merges + an APT merge (or, ideally, a new tails-greeter release
> uploaded to the devel suite).
> 
> I have successfully tested an ISO built from this branch with the
> French, French (alternative), Italian, English and Chinese
> keyboard layouts.

Code looks good and it certainly improves the situation. I'll merge the
current state, and upload a new Greeter package in a few minutes. But I
won't close the ticket...

>From the commit message:

> Note that we don't set layouts to [chosen one, US] anymore, as I
> could not make it work properly: in this case, regardless of the
> order in which we set it, the US layout wins and is applied by
> default in the session. Anyway, it's easy enough to either directly
> choose US in the greeter (when one wants the GUI in their preferred
> language, and a US keyboard layout), or to add the US layout in the
> GNOME settings (when using both layouts in the same session). So,
> this seems like an acceptable regression to me.

Isn't a US layout pretty much mandatory to have on switch for non-latin
based layouts? E.g. most of the Internet use ASCII URLs, many websites
only accept (a subset of) ASCII for credentials, terminal commands are
in ASCII, etc, etc.

It seems to me like having the US layout on switch is essential for
non-latin layouts. While adding the US layout via GNOME settings is a
workaround, it's incredible inconvenient, and AFAIK we haven't
documented it. Fixing either of these is a blocker for 1.1.

Luckily I think I have a (start for a) solution to get back what we had:


--- a/config/chroot_local-includes/usr/local/bin/tails-configure-keyboard
+++ b/config/chroot_local-includes/usr/local/bin/tails-configure-keyboard
@@ -8,3 +8,6 @@ set -eu
 dconf write /org/gnome/libgnomekbd/keyboard/model   "'$XKBMODEL'"
 dconf write /org/gnome/libgnomekbd/keyboard/layouts
"['$XKBLAYOUT\\t$XKBVARIANT']"
 dconf write /org/gnome/libgnomekbd/keyboard/options "['$XKBOPTIONS']"
+
+sleep 10
+dconf write /org/gnome/libgnomekbd/keyboard/layouts
"['$XKBLAYOUT\\t$XKBVARIANT', 'us']"


Applying this patch will enable the double layout, with the chosen one
as default. The `sleep` is necessary, so there's something racy here. Of
course, this "sleep fix" is racy too, e.g. sleeping for 10 seconds may
not be enough on slow hardware. The best would be if we could figure out
exactly what it is we need to wait for. Also, note that setting
"layouts" twice like that seems necessary (and it will ensure that the
correct layout is set while we `sleep`).

However, even if I'd prefer a solution without a static sleep, I prefer
shipping this in 1.1 compared to our other options.

Thoughts?

Cheers!
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] [PATCH] Feature #7009: Make the Greeter's help window, resolution-aware

[anonym]

Andres Gomez Ramirez wrote:
> I'm sending a patch for Feature #7009: Make the Greeter's help window
> resolution-aware, https://labs.riseup.net/code/issues/7009.

Looks good => merged and part of a newly uploaded tails-greeter. Thanks
for your contribution!

Cheers!
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] [review'n'merge:1.1] bugfix/7065-keyboard-localization

[anonym]

14/05/14 15:57, anonym wrote:
> However, even if I'd prefer a solution without a static sleep, I prefer
> shipping this in 1.1 compared to our other options.

Well, something also should be done so we don't get ['us', 'us'] when
'us' is the selected layout, which my current (simplistic) patch does.

Cheers!

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Please review and merge tails-greeter:bugfix/6959-persistent_printers

[anonym]

04/04/14 14:47, Alan wrote:
> Please review and merge into tails-greeter:master 
> tails-greeter:bugfix/6959-persistent_printers.
> 
> I believe it fixes https://labs.riseup.net/code/issues/6959 "Persistence
> of printer broken in Tails 0.23"
> 
> Please also merge bugfix/6959-persistent_printers-wheezy into
> tails-greeter:wheezy

Looks good! Merged into tails-greeter's master branch, since we've moved
full on to Wheezy now.

> I'm too lazy to build a package and upload it to experimental for such
> a tiny change. Dear RM, if you requires it just ask and I'll do it.

A new tails-greeter has been uploaded.

Cheers!

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] #7250 Bring back keyboard layout switch on presing Alt+Shift [Was: [review'n'merge:1.1] bugfix/7065-keyboard-localization]

[anonym]

09/05/14 17:36, intrigeri wrote:
> bugfix/7065-keyboard-localization fixes issue #7065 for me.

While testing this branch I noticed that Alt+Shift doesn't switch layout
any more. Apparently GNOME nowadays expects "grp\tgrp:alt_shift_toggle" so
that should be fixed in tails-greeter.

However, we already try (commit 0fe29f77) to set this in
`config/chroot_local-includes/etc/dconf/db/local.d/00_Tails_defaults`,
but that doesn't work. Of course, with your fix for #7065 it'd be
overwritten, but I tried booting an image with without the fix, and no
libgnomekbd value is set at all after a normal boot.

Optimistcally assigning this to you, intrigeri, since it'll be related
to fixing the rest of #7065.

Cheers!


___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Fwd: [tor-talk] Upcoming stable release: 0.2.4.22. Please test?

[intrigeri]

Hi,

anonym: I guess you'll want to get in touch with Nick and see if
there's any chance we can/want to pick tor 0.2.4.22 final for Tails
1.1.

--- Begin Message ---
Hi, all!

We're going to be releasing Tor 0.2.4.22 soon.  I have a candidate
source bundle at

  http://www.wangafu.net/~nickm/volatile/tor-0.2.4.22.tar.gz

This is not the final Tor 0.2.4.22 release.  It is a testing bundle
that I made today.  I'm not planning to add any more code to it,
though, unless we find new bugs.

It should have a signed SHA256 hash in the file:

  http://www.wangafu.net/~nickm/volatile/tor-0.2.4.22.txt.asc

I might upload new versions over the next several days if I find bugs
to fix.

There's a copy of the current 0.2.4.x changelog here:

  
https://gitweb.torproject.org/tor.git/blob_plain/refs/heads/release-0.2.4:/ChangeLog

Does it work for you?  (This is going to be a question for people who
build Tor from source.)  In particular, I'm most interested in any new
bugs in this version that were not in 0.2.4.21.

If you find a bug in this bundle that was not present in 0.2.4.21,
please let me know -- either by sending an email, or opening a ticket
on trac.

best wishes,
-- 
Nick Mathewson
-- 
tor-talk mailing list - tor-t...@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
--- End Message ---


-- 
  intrigeri
  | clé GnuPG @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | empreinte OTR @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] [tor-talk] Upcoming stable release: 0.2.4.22. Please test?

[anonym]

14/05/14 21:46, Nick Mathewson wrote:
> Hi, all!
> 
> We're going to be releasing Tor 0.2.4.22 soon.  I have a candidate
> source bundle at [...]

Unless there's a lot of unexpected problems, am I right to assume that
there's a good probability for 0.2.4.22 to be released before 8th of
June (the day the final image for Tails 1.1 is planned to be built)?
What's your hunch? I'm not asking for any promises, of course. :)

Cheers!

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Which I2P in Tails 1.1?

[Kill Your TV]

On Sun, 11 May 2014 09:20:59 + (UTC)
intrigeri  wrote:

> Hi Kill Your TV,
> 
> I'm wondering what version of I2P you want to see in Tails 1.1. In the
> devel branch, we're currently installing 0.9.12-1~deb7u+1 from your
> APT repo.
> 
> If you have no plans for shipping anything newer, then I'll just
> proceed with #6731 ("Import I2P packages for Wheezy").  

I'd like to have a newer one assuming we (on I2P's end) can meet the
1.1 deadline.

> If you have plans to ship a newer version, then: is there an ETA to
> get the new .deb's ready to be tested, and imported into Tails?  

The cut-off for check-ins for I2P 0.9.13 is May 16th. A release will
most likely happen early next week. If that's acceptable, excellent. :)
I'll send an email/update redmine with the "pull new packages please"
request.


-- 
GPG ID: 0x5BF72F42D0952C5A
Fingerprint: BD12 65FD 4954 C40A EBCB  F5D7 5BF7 2F42 D095 2C5A


signature.asc
Description: PGP signature
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Which I2P in Tails 1.1?

[anonym]

15/05/14 00:59, Kill Your TV wrote:
> On Sun, 11 May 2014 09:20:59 + (UTC)
> intrigeri  wrote:
> 
>> Hi Kill Your TV,
>>
>> I'm wondering what version of I2P you want to see in Tails 1.1. In the
>> devel branch, we're currently installing 0.9.12-1~deb7u+1 from your
>> APT repo.
>>
>> If you have no plans for shipping anything newer, then I'll just
>> proceed with #6731 ("Import I2P packages for Wheezy").  
> 
> I'd like to have a newer one assuming we (on I2P's end) can meet the
> 1.1 deadline.
> 
>> If you have plans to ship a newer version, then: is there an ETA to
>> get the new .deb's ready to be tested, and imported into Tails?  
> 
> The cut-off for check-ins for I2P 0.9.13 is May 16th. A release will
> most likely happen early next week. If that's acceptable, excellent. :)

The worst case I can handle would be if it's available early morning
(CEST) on 28th of May (same day I'm gonna build the 1.1-rc image), but
the earlier the better, of course.

> I'll send an email/update redmine with the "pull new packages please"
> request.

If on redmine, please set target version to 1.1 and assign the ticket to me.

Cheers!

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] General Comments on Download/Installation Documents

[John Olsen]

Gentlemen:

I regard myself as a power windows user and program in pascal, php, basic, a 
couple variations of assembly and write MySQL stored procedures. Yet, I have 
been unable to navigate through to the point where I have an operating USB 
stick. Why? Windows is different enough from Linux that the Linux terminology 
is incomprehensible. ISO Image, Signature, Signing Key, Gnome, Ubuntu, Debian, 
sudo, seahorse-plugins etc. are at best only vague notions to a Windows user. 
Further, we don't already have Linux running so all steps described for Linux 
are useless chatter. Yet, I think there are more windows users in the world 
than Linux and many of us would like to use Tails for simple things without 
first learning the Linux operating system. What is needed is a detailed step by 
step process for Windows users. Download these, plug in a blank USB stick, 
double click that put this data in the blank etc. all with screen shots.  
Alternately, how about selling operating USB sticks delivered by mail for say 
$50.00 each?

Dr. John H. Olsen
VP Operations
OMAX Corporation
21409 72nd Ave S.
Kent, WA 98032
253 872-2300
www.omax.com

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.