[Tails-dev] ASP offline issue: advice needed

[Alan]

Hi,

A bug was found in Additional Software Packages (ASP) that make the
install fail if APT lists are updated outside ASP and they reference new
version of ASP installed packages. This is likely to happen every new
Tails release. This is now solved when the user is connecting to the
network after the failed installation (#16566).

I think the remaining issue (#16567) is for this scenario: I'm online
preparing Tails ASP for a specific task. I'm running apt update or
starting Synaptic and there are new versions of packages that I already
configured as ASP. At this point everything looks good.

Then I restart my Tails offline, and some of my ASP fail to install.

Note that of I go online at some point, the situation would be solved by
case C (#16567).

I don't know if we consider this as a corner case or not, and thus if we
want to solve it at at what priority.

Thanks by advance for your input,

Cheers
___
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.

[Tails-dev] RFC: Additional Software Packages plan

[Alan]

Hi,

As you might already know, we are working on a user interface for
Additional Software Packages:

https://tails.boum.org/doc/advanced_topics/additional_software/

We summed up our findings in the blueprint at:

https://tails.boum.org/blueprint/additional_software_packages/gui/

If you're interested, this is the righ time to go throught it and
comment in this thread.

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] *Modified* release schedule for 2018, take 3

[Alan]

Hi,

intrigeri:
> So I'll update our calendar, Redmine etc. right away :)
> 

It's OK for me te have Additional Software Packages improvements ready
for 2018-08-28.

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] Replacing Florence with GNOME's own on-screen keyboard?

[Alan]

Hi,

intrigeri:
> We have issues with Florence design, implementation, and its poor 
> integration into GNOME; it's not getting any better over time. One
> option we have is to simply drop it and instead rely on GNOME's own
> on-screen keyboard. 

I've starting looking at GNOME OSK at GUADEC, and updated the ticket with my
findings and opinions so far.

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] Tails Greeter Accessability

[Alan]

Hi,

Justin:
> I was wondering is anyone researching or working on making an option
> to enable Orca in Tails Greeter or the boot splash screen?  

I don't think it is anyhow easy to make the boot splash screen
accessible, but it's not so useful anymore. However, we plan to make te
new greeter we are currently working on accessible.

> Ticket
> 7500 was updated about a year ago, so I just thought I’d check on
> this. I’m visually impaired, so this would be a nice feature.

Sorry to be so slow on that.

> If this gets implemented at some point, I’d be happy to test it out.

Hopefully there will be some testing ISO available this summer. I'll
stay you tuned and your testing would be much appreciated.

Cheers,

Alan
___
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] Tails Greeter Accessability

[Alan]

Hi,

Justin:
> I was wondering is anyone researching or working on making an option 
> to enable Orca in Tails Greeter 

We have plans to make the new greeter we are currently working on
accessible.

> or the boot splash screen?

I don't think it is anyhow easy to make the boot splash screen
accessible because there is very few components loaded at this stage,
but this screen is not so useful anymore.

> Ticket 7500 was updated about a year ago, so I just thought I’d check
> on this. I’m visually impaired, so this would be a nice feature.

Sorry to be so slow on that.

> If this gets implemented at some point, I’d be happy to test it out.

Hopefully there will be some testing ISO available this summer. I'll
stay you tuned and your testing would be much appreciated.

Cheers,

Alan
___
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] Onion Circuits upstream maintenance

[Alan]

intrigeri:
> I agree that Tails' Redmine feels like the right place to handle
> this.
> 
Me too, and thanks Sascha for your patch !

> Now I'll let Alan comment on this, and more importantly perhaps on
> the "who" question.
> 
I'm happy to partcicpate to maintain Onion Circuits. However, I can't
promise to be responsive within a few weeks sometimes (and I don't even
speek about a few days...) so if people want more responsiveness and
have time to participate on the maintenance, I would love them joining!

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] Help! JavaScript / GNOME Shell extension problem || removing topIcons

[Alan]

Hi,

intrigeri:
> one the remaining issues that make me a bit sad about the current
> state of Tails/Jessie (scheduled to be released in two weeks) is:
> 
>   https://labs.riseup.net/code/issues/10576
> 
> Anyone at ease with JavaScript and/or the GNOME Shell extensions
> system, who has time to give a hand?
> 
I'm going to have a look next weekend, but no result warranty...

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] Windows 10 theme for Tails/Jessie

[Alan]

Hi,

On Tue, 27 Oct 2015 15:59:38 -0400
Christian Medel  wrote:

> I got it to work shortly, and this is the result :

Congrats!

If you need changes in the extension to change the
position/color of some thinks that you can't change in a theme, feel
free to ask me (no promise, but I'll try)

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] Windows 10 theme for Tails/Jessie

[Alan]

Hi,

Christian Medel  wrote:
> I guess I just booted in a normal Cinnamon session altogether.

I don't think that it's a good idea to ship cinnamon on Tails. It's a
*fork* of GNOME and would make the user experience under the camouflage
too different than under the standard GNOME I think.

> The bad thing with SHELL is that it doesn't look at all like windows. 

I think that this is a very bold assumption. You can do basically
everything with shell extensions. 

> Even with window list and bottom panels activated, there's no way to get 
> a decent taskbar 

What do you mean by "a decent taskbar"?

> or hide the top bar.

> No system tray either.

Suse Entreprise Desktop made a GNOME desktop with only one panel:

http://videos.guadec.org/2015/Challenge%20of%20Enterprise%20Desktop%20with%20GNOME%203/

They have litte patches to GNOME shell JS, which I think we could
apply if needed, as well as their own extension.

> I successfully have tested Windows 10 v0.6.7 in SHELL. It looks just 
> like on 3.18, since the theme was originally built for Linux Mint 17.1. 
> To answer a previous question, if corrections are needed I will gladly 
> do my best to correct them.
> 
> This is how Debian looked while in a GNOME 3.14 session :
> 
> http://i.imgur.com/wPq01XH.png
> 
Great! Would you try thin under Tails Jessie? You can find the latest
ISO here:

http://nightly.tails.boum.org/build_Tails_ISO_feature-jessie/lastSuccessful/archive/latest.iso

> some bugs :
>
> - terminal background color & text color
>

See
https://git-tails.immerda.ch/gnome-theme-windows8/tree/gtk/gtk-3.0/apps/gnome-applications.css#n173

> - metacity only for GTK 2.0 apps
>
I'm not sure I understand, but see:
https://git-tails.immerda.ch/gnome-theme-windows8/tree/metacity-1

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] Greeter revamp: prototype time?

[Alan]

Hi,

[please answer to tails...@boum.org]

As you might now, we are working on revamping the greeter interface
since more than one year. We came to a proposal, which is summarized in
this blueprint:

https://tails.boum.org/blueprint/greeter_revamp_UI/design_rationale_phase1/

I think it's mature enough, and it's now time to implement a prototype
including at least a working UI (https://labs.riseup.net/code/issues/7550)
so that we can do UI tests (https://labs.riseup.net/code/issues/8238).

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.

[Tails-dev] Tor Monitor: don't show duplicate streams with the same destination in the same circuit

[Alan]

Hi,

sajolida  wrote:
> Done in #10183.
> 
After checking how this could be done, I'm really unsure. I currently
display the stream Tor has. Deduplicating streams would mean to create
another list of streams, which would not ma to Tor streams. Then, how
should we update the status of the stream group? A stream (with the
same destination) could be "Succeeded" while another is "Sentconnect"
and another "Closing". This proposal means we should invent another
concept, that Tor dosn't provide, and that makes few sense.

I checked also what vidalia does, and it does not deduplicate streams
with the same destination. So I don't think this should be a
requirement to replace Vidalia.

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] Reminder: help porting Windows camouflage to GNOME 3.14

[Alan]

Hi everybody!

Long story short: we send a call for participation on porting
"Windows camouflage" to GNOME 3.14. We got not serious answer. If
nobody volunteers to do the job, next Tails major version will *not*
include camouflage mode.

Find below the full call.

Cheers

* * * 


Call for participation!
---

Are you into GNOME development and want to participate to Tails? Do you
want to improve your GTK or GNOME Shell theming skills while supporting
users needing privacy and stealth? Consider porting the "Windows
camouflage" of Tails to GNOME 3.14. What is the Windows camouflage?

Tails documentation reads "if you are using a computer in public you
may want to avoid attracting unwanted attention by changing the way
Tails looks into something that resembles Microsoft Windows 8." This is
what we call the "Windows camouflage".

Why is it useful?
-

We got reports that users have been arrested while using a
privacy-enhancing distribution because their screen looked very
different from others, which raised suspicion. It's why a Windows
camouflage has been added to Tails. What should be done?

Current Tails is based on GNOME 3.8 in "Fallback" mode. We are
currently upgrading Tails on top of the upcoming version on Debian
("Jessie") which is based on GNOME 3.14. The Windows camouflage should
be upgraded to the last version of GTK and ported from GNOME Panel to
GNOME shell. That includes GTK and GNOME Shell theming through CSS as
well as writing a custom GNOME Shell extension.

Why do we need you?
---

The team currently working on Tails is very busy and decided to focus
on the core or the upgrade rather than on the Windows camouflage. We
currently plan to go ahead with the initial Tails Jessie release even
if the Windows camouflage is missing. However, we would love to ship a
proper Windows camouflage and think it's a good occasion for you to
give a hand. We'll provide support to anybody volunteering and work
together on integrating the new theme to upcoming Tails Jessie
snapshots.

Where should you start?
---

Please read
https://tails.boum.org/blueprint/update_camouflage_for_jessie/, then
write to tails-dev@boum.org. This is a public mailing list:
https://mailman.boum.org/listinfo/tails-dev/. Please subscribe!
___
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 Monitor build fails

[Alan]

Hi,

Sascha Steinbiss  wrote:
> I can build everything perfectly directly after cloning:
> 
> [vagrant@debian-8:~] $ git clone https://github.com/satta/tor-monitor.git
> Cloning into 'tor-monitor'...
> remote: Counting objects: 153, done.
> remote: Compressing objects: 100% (74/74), done.
> remote: Total 153 (delta 78), reused 145 (delta 70), pack-reused 0
> Receiving objects: 100% (153/153), 32.71 KiB | 0 bytes/s, done.
> Resolving deltas: 100% (78/78), done.
> Checking connectivity... done.
> [vagrant@debian-8:~] $ cd tor-monitor
> [vagrant@debian-8:~/tor-monitor] $ gbp buildpackage --git-pbuilder -uc -us
> gbp:info: tor-monitor_0.1.orig.tar.gz does not exist, creating from 
> 'upstream/0.1'
> Building with cowbuilder for distribution sid
> I: using cowbuilder as pbuilder
> […]
> 
> As you can see, the tarball is created if it does not exist. Does this work 
> for you?
> 
No, it doesn't work under Tails (based on wheezy), but I tried under
jessie and the build starts... but then I hit:

$ gbp buildpackage --git-dist=jessie --git-arch=i386 --git-pbuilder -uc -us
gbp:info: Building with pbuilder for jessie
Building with pbuilder for distribution jessie, architecture i386
I: using pbuilder as pbuilder
dpkg-buildpackage: source package tor-monitor
dpkg-buildpackage: source version 0.1-1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Sascha Steinbiss 
 dpkg-source --before-build tor-monitor-packaging
 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
   dh_testdir -O--buildsystem=pybuild
   debian/rules override_dh_auto_clean
make[1]: Entering directory 'XXX/tor-monitor-packaging'
rm -f po/tormonitor.pot
rm -rf build
make[1]: Leaving directory 'XXX/tor-monitor-packaging'
   dh_clean -O--buildsystem=pybuild
 dpkg-source -b tor-monitor-packaging
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building tor-monitor using existing 
./tor-monitor_0.1.orig.tar.gz
dpkg-source: warning: file tor-monitor-packaging/tormonitor.desktop has no 
final newline (either original or modified version)
dpkg-source: info: local changes detected, the modified files are:
 tor-monitor-packaging/tormonitor.desktop
dpkg-source: error: aborting due to unexpected upstream changes, see 
/tmp/tor-monitor_0.1-1.diff.3aQP6Q
dpkg-source: info: you can integrate the local changes with dpkg-source --commit
dpkg-buildpackage: error: dpkg-source -b tor-monitor-packaging gave error exit 
status 2
gbp:error: 'git-pbuilder -uc -us' failed: it exited with 2


Thanks for your support,

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] Tor Monitor: don't show duplicate streams with the same destination in the same circuit

[Alan]

Hi,

sajolida <sajol...@pimienta.org> wrote:
> Alan:
> > intrigeri <intrig...@boum.org> wrote:
> >> sajolida wrote (27 Aug 2015 16:48:14 GMT) :
> >>> C. Duplicate information
> >>
> >>> In the list of circuits I sometimes see duplicated lines.
> >>
> >> Technical nitpicking: these are streams, not circuits :)
> >>
> >>> For example when connecting to heavy websites like YouTube.
> >>> See duplicates.png in attachment. Why not deduplicate these lines?
> >>
> >> I'm not sure what's the value of the "there are multiple streams to
> >> this IP:PORT going on that circuit" information. At first glance,
> >> I would say let's deduplicate, but perhaps I'm missing a use case
> >> or three?
> >>
> > If I display duplicates, either I have a bug or there are multiple
> > streams to this IP:port in that circuit... I can deduplicate them if
> > requested but I fail to see the interest to complexify the
> > code to simplify the reality.
> 
> The interest is to have a more compact view displayed to the user and
> reduce noise. Did you see my screenshot? To me it looks pretty awful. I
> fail to see the interest in complexifying so much the interface to
> simplify a bit the code :)

Please file a ticket for that then. I'd suggest we don't consider it as
a blocker thought.

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] Adding laptops which don't shutdown properly

[Alan]

Hi,

sajolida  wrote:
> > But I was wondering how relevant it is to add computers there, as that
> > list might never ends, wrt. to UEFI hardware?
> 
> I think it's fine.

In the current state of Tails, it is impossible for an hardware boot
in UEFI mode to shutdown properly. Perhaps saying this like that is
easier, as the same hardware can boot in several modes. For instance,
most MacBookPro will boot in BIOS-emulation mode from DVD (and shutdown
properly), but in EFI mode from USB and fail to shutdown. In some PCs
there is a firmware menu setting.

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] Tor Monitor build fails

[Alan]

Hi,

Sascha Steinbiss sa...@tetrinetsucht.de wrote:
 Long story short, there’s a first version of a tor-monitor package in:
 https://github.com/satta/tor-monitor
 
I just tried to build the package and failed:

$ git-buildpackage --git-debian-branch=debian
dh clean --with python3 --buildsystem=pybuild
   dh_testdir -O--buildsystem=pybuild
   debian/rules override_dh_auto_clean
make[1]: Entering directory `/home/amnesia/Persistent/dev/tor-monitor'
rm -f po/tormonitor.pot
rm -rf build
make[1]: Leaving directory `/home/amnesia/Persistent/dev/tor-monitor'
   dh_clean -O--buildsystem=pybuild
gbp:error: Couldn't checkout tor-monitor_0.1.orig.tar.gz: Execution 
failed: [Errno 2] No such file or directory

What am I doing wrong? I'm doing exactly what works for our other python
packages.

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] Tor Monitor build fails

[Alan]

Hi,

u u...@451f.org wrote:
 Alan:
  I just tried to build the package and failed:
  
  $ git-buildpackage --git-debian-branch=debian
  gbp:error: Couldn't checkout tor-monitor_0.1.orig.tar.gz: Execution 
  failed: [Errno 2] No such file or directory
  
  What am I doing wrong? I'm doing exactly what works for our other python
  packages.
 
 I could build the package successfully. Please make sure to fetch all
 the branches, namely pristine-tar

I do have pristine-tar following satta/pristine-tar

 and build from debian/sid.
 
debian/sid is a tag. When I try to build from it, I get:

gbp.git.repository.GitRepositoryError: Currently not on a branch

I also tried to clone https://github.com/satta/tor-monitor.git to a new
empty repo, create the branches, and got the same result.

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] Package Tor Monitor

[Alan]

Hi,

bertagaz berta...@ptitcanardnoir.org wrote:
 Reading http://www.glatzor.de/projects/python-distutils-extra/, it seems
 you can configure distutils-extra to disable the build_l18n target with
 such a setup.cfg. Not sure that it's the one responsible of your problem
 though.
 
No, because it will not build the .mo files anymore. Look at the code:
https://bazaar.launchpad.net/~python-distutils-extra-hackers/python-distutils-extra/debian/view/head:/DistUtilsExtra/command/build_i18n.py#L89

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] Package Tor Monitor

[Alan]

Hi,

Sascha Steinbiss sa...@tetrinetsucht.de wrote:
 You are definitely more familiar with the internals of the Python distutils 
 steps.
 I am happy with any solution you propose as long as ‘setup.py build’ does not
 generate a new POT file on each build (hence updating the timestamp)
 but reuses a version that is pregenerated by you and committed in your
 upstream repo.
 
After reading the documentation and the code of the build system
extensions I use to support python desktop applications
(python-distutils-extra), I came to the conclusion that your request is
not supported. I looked for other similar build systems and fails to
find one with similar functionalities. Not as easy as I though...

I can whishlist this feature upstream, but that won't solve your short
term problem.

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] Testing with openqa?

[Alan]

Hi,

At GUADEC I talked with SuSE people about testing. They use something
called OpenQA[1] that looks like a software that does basically what our
automated test suite does[2]: test installers, live isos and
applications integrations by clicking on UI images in VMs. They are
trying to convince other distributions to take benefit on the work they
did on it.

Too bad we did develop two solutions in parallel... but I encourage the
people working on the test suite to have a look at OpenQA and consider
wether it would make sense to use it. It has a nice web interface to
update screenshots, and we would share maintenance with other distros.

Cheers

1. https://os-autoinst.github.io/openQA/
2. https://en.opensuse.org/openSUSE:OpenQA
___
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] Package Tor Monitor

[Alan]

Hi,

Clement Hermann nod...@nodens.org wrote:
 Le 19/08/2015 23:42, Sascha Steinbiss a écrit :
 Hi Sascha, welcome !
  Long story short, there’s a first version of a tor-monitor package in:
  https://github.com/satta/tor-monitor
 
First, thanks a lot!

 I just I a look at it, and I was wondering : the pot file gets generated
 at build time, so it would'nt be reproducible without some patches to
 the build system (change date of potfile generation for the last
 changelog entry's, or maybe change the upstream work to generate it
 along with the tarball, and bypass this at debian build time).
 
I'm upstream, so I can do anything you want to ease packaging. Do you
want the POT file to be included in 'sdist' tarball?

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] [Tails-ux] Tails 1.5 - USB boot from Macbook Polycarbonate A1342 Late 2009

[Alan]

Hi,

I'm forwarding you this feedback on 32-bits UEFI received on tails-ux:

On Tue, 11 Aug 2015 20:34:20 +0200
aka pseudonym rock...@gmx.com wrote:
 USB boot from Macbook Polycarbonate A1342 Late 2009 now works with Tails 1.5. 
  (It sort of sometimes did with 1.4.1 and never with 1.4.)  Well done adding 
 32-bit GRUB. Should hopefully be the same with all the other Macbooks needing 
 a 32-bit boot.
  
 Important tip:  if the option key is held down when power is pushed the EFI 
 icon appears and can be selected but does zilch.  If option isn't pressed 
 until the screen has turned grey then all is fine.

___
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] Package Tor Monitor

[Alan]

Hi,

Would someone knowledgeable please package:
https://git-tails.immerda.ch/alan/tor-monitor/tag/?id=0.1

Thanks by advance
___
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] OpenHelp documentation conference in September

[Alan]

Hi,

I learned at GUADEC that there will be an open source documentation
conference in September that may be very interesting for the people
working on documentation. It is called OpenHelp and is from Sept 26
to Sept 30: http://conf.openhelp.cc

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] Package Tor Monitor

[Alan]

Hi,

intrigeri intrig...@boum.org wrote:
 Alan wrote (17 Aug 2015 23:42:12 GMT) :
  Would someone knowledgeable please package:
  https://git-tails.immerda.ch/alan/tor-monitor/tag/?id=0.1
 
 Some more bits of info that might help people raise their hand:
 
[...]
 
Please note that I was looking for somebody to prepare a package
for Tails, not for Debian, but why not?

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] Package Tor Monitor

[Alan]

Hi,

sajolida sajol...@pimienta.org wrote:
 Alan:
  Would someone knowledgeable please package:
  https://git-tails.immerda.ch/alan/tor-monitor/tag/?id=0.1
 
 I don't have the skills to package this but I would be happy to test it
 in Tails or elsewhere. How can I do that?

Clone the git, then follow the instructions in README. Don't hesitate
to ask if something is unclear.

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] Heads up: changed ways to track review'n'merge requests

[Alan]

Hi!

On Mon, 13 Jul 2015 09:51:38 +0200
intrigeri intrig...@boum.org wrote:
 in the [Tails-dev] Getting rid of review'n'merge email on this list
 thread, we've decided to stop requiring review'n'merge email on this
 list. Alternate ways to track such requests have been found and set
 up, and are documented there:
 
 https://tails.boum.org/contribute/working_together/Redmine/#atom
 
Does anyone knows if it's possible to get this by email?

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] RFC: persistent Tor state

[Alan]

Hi,

 anonym and I have made great progress on this front, and we would like
 feedback from you folks regarding the state of our current reasoning
 and preferred design:
 
   https://labs.riseup.net/code/issues/5462
   https://tails.boum.org/blueprint/persistent_Tor_state/
 
I've read through this. Congrats for this!

 In particular, the Drawbacks of persistent Tor state section is
 important, and because of it the proposed design will require some
 project-wide decision:
 
   https://tails.boum.org/blueprint/persistent_Tor_state/#drawbacks
 
 = added to the summit's agenda, but we can certainly start discussing
 it earlier.
 
The 1st drawback: If the attacker records that someone has been
using a given Entry Guard at a given location in the past, and then
someone uses the same Entry Guard at the same location, then there are
chances that it's the same person who is back to that location. looks
quite concerning to me, as I believe this kind of data can easily be
recorded automatically and used afterwards: 

- what about a delay after which not to reuse an old location? Would
  that be a major problem for mitigating the attacks against anonymity
  via stable Entry Guard(s)?
- what about prompting the user, when they reconnect to an old location
  after having connected to other, if they want to reuse the data or
  not? It's not very clear to me the implications of not reusing these
  data however.

The 2nd drawback If the attacker records what guard a Tails user is
using at home, and then configures the routers, in other chosen places, to use
the same MAC address. Then, the attacker can confirm whether the user
is visiting those places looks less serious to me as:

- it's a more active and targetted attack;
- it looks likely to me that if the attacker takes the energy to access
  the routers, they could do other confirmation attacks based on the
  traffic and browsing habits of the user

To mitigate this 2nd drawback, I see no other way than to ask the user
where they connects from (eg with a codename by location), which seems
complicated to explain.

Hope it helps
___
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] Fwd: Python 2, Python 3, Stretch Buster

[Alan]

Hi!

On Thu, 16 Apr 2015 20:44:07 +0200
intrigeri intrig...@debian.org wrote:
 The largest bits of our Python stuff is being ported to Python 3
 already, but it looks like it's time to stop writing new Python
 2 code, for good. Anyone wanting to refresh our blueprint about
 remaining Python 2 stuff? Alan, perhaps?
 
Yes I can do it, but I'm not highly available currenlty, so if someone
is quicker that me, do it!
___
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] underlay for UX or blueprints

[Alan]

Hi,

intrigeri intrig...@boum.org wrote:
 Perhaps we should instead have:
 
 * An entirely different ikiwiki at https://blueprints.tails.b.o/.
   I believe it would fulfill the needs you described, without the most
   important drawbacks identified above. Also, it may allow us to fully
   disable the web interface on our website, which I've been longing
   for since years.
 
We would then push files related to a blueprint, even big ones there?

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] How to replace the green onion [was: What do we miss to replace Vidalia]

[Alan]

Hi,

On Sun, 15 Mar 2015 23:29:55 +0100
intrigeri intrig...@boum.org wrote:
 sajolida wrote (15 Mar 2015 19:46:47 GMT) :
  I'm personally undecided wrt. which one of these two is the best.
 
  Neither am I :)
 
 Then I'm all for those who do the work decide — in this case, that
 would be Alan.
 
Then there will be a menu I think.

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] How to replace the green onion

[Alan]

Hi,

On Sun, 15 Mar 2015 18:15:22 +0100
intrigeri intrig...@boum.org wrote:
  Do you want me to file whatever tickets are needed about it?
  
  I'd appreciate it.
 
 I've updated #9002 to reflect what I believe is the consensus we've
 reached, and I've assigned it to you.

Thanks!
___
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] How to replace the green onion

[Alan]

Hi,

sajolida sajol...@pimienta.org wrote:
 Regarding whether the onion turns red when Tor is not usable anymore
 (for whatever reason that we still need to specify). This I can't tell
 either.
 
To avoid regressions, let's just implement a very simple 1 bit
extension (Tor/no Tor).

 If you think that you need more UX design to be done before deciding on
 the right infrastructure for those tools, then we should start a thread
 on tails-ux. The bad thing to do would be to take technical decisions in
 this thread (which is dense and probably not read by anyone else than
 us) that would, later on, limit what we ca propose as UX for the big
 picture of #7438 and frustrate both the people designing and the people
 coding.
 
I don't we need more design to implement the basic mechanism that would
avoid regressions.

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] State of TAILS accessibility with Orca

[Alan]

Hi,

sajolida sajol...@pimienta.org wrote:
 Hadi Rezaee:
  except the fact that i cannot start orca in  the greeter
 
 Yeah, unfortunately that's a known issue:
 https://labs.riseup.net/code/issues/7500
 
What do you think about the proposed solution (from the above ticket):

Easy solution: Add gnome-standard hotkeys to launch
accessibility tools.

Example: Orca, the screen-reader for blind users.
Simply add a hotkey, (alt+super+S) to launch it. in the greeter.

  apparently there is no sound when the greeter starts up, or something
  like that. beside that, I can work with orca and tails' apps well.

We could add basic greeter accessibility as a requirement of the
revamp (setting #7500 as a subtask of #8230). Thoughs?

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 and merge feature/6999-compress-png

[Alan]

Hi,

intrigeri intrig...@boum.org wrote:
  Of course, this only make sense if we get a compression rate that is
  worth doing all that stuff... so maybe we should investigate c) before
  deciding on this and seem how the result affects the final ISO size.
 
 Exactly. I bet a couple doc branch reviews that the test results will
 tell us that mksquashfs is simply good enough.
 
In my opinion, all this was a nice attempt, but unfortunately these
compression things doesn't seem me worth it given the energy involved
vs the expected gain.

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] How to replace the green onion [was: What do we miss to replace Vidalia]

[Alan]

Hi,

sajolida sajol...@pimienta.org wrote:
 Following-up on the ideas of:
 
 - Keeping the green onion as a permanent visual feedback on the desktop.
 - Not breaking too much of what people have been used to unless we
   have a good (UX) reason to do so (keeping what works in Vidalia).
 - Integrating Tor Monitor nicely on the desktop.
 - Considering the green onion and the list of circuits as part of the
   same user task of monitoring tool.
 
 I hereby propose to have the list of circuits accessible directly from
 the green onion as it is the case now in Vidalia. But I'm not sure how
 this fits with your architectural plans and related security implications.
 
What I see is :
 Top shell bar   Onion
|  |
v  v
[_Applications_Places__O_o_o_o_]
   A___
  |Tor is ready|
  |Open Tor Monitor|
  ++
Disconnected: striked onion

X  X
 XX_./\._XX
  /XX  XX\
 /   XX   \
 | XX  XX |
 XX__XX
X  X

Bootstraping: onion with dots (as when network is connecting)

   _./\._
  /  \
 //\ /\ /\\
 |\/ \/ \/|
 \/

Connected: full onion

   _./\._
  /  \
 /\
 ||
 \/

Would this address your requirements?

By the way, I'm not sure the onion should be green. For better
integration into GNOME Shell I think it should perhaps be monochromatic.

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] Macbook Air EFI fixed

[Alan Kubiak]

There is supposedly a bug with booting Tails on Macbook Air or Macbook 
Pro due to an EFI issue.  According to your support channel, you 
recommend a program to install the Tails ISO on a USB drive.  The 
recommended program does create a Tails/USB drive but it wont boot on a 
Macbook.


The solution is to use a different program called Rufus 2.0 to create 
the bootable USB drive from the Tails ISO.  Simply format as FAT32 and 
install the ISO from RUFUS.   When booting from the Mac, just boot the 
Tails USB drive from the BIOS.
___
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] Tails contributors meeting: Tuesday March 03

[Alan]

Hi,

sajolida sajol...@pimienta.org wrote:
 The next Tails contributors meeting is scheduled for:
 
   Tuesday 03 March
   #tails-dev on irc.oftc.net
9 pm in Paris
8 pm in London
3 pm in New-York
   12 pm in San Francisco
  
 Everyone interested in contributing to Tails is welcome!
 
I'll unfortunately not be able to attend, but I'd like to report on
some things I'm working on currently:

- discussions on the greeter revamp[1] are going on with good energy
  on tails-ux[2]
- I worked on Tor Monitor [3] a replacement for vidalia[4] in
  tails/jessie. This is discussed on tails-dev[5]
  
[1]: https://labs.riseup.net/code/issues/5464
[2]: https://mailman.boum.org/pipermail/tails-ux/
[3]: http://git.tails.boum.org/alan/tor-monitor
[4]: https://labs.riseup.net/code/issues/6841
[5]: https://mailman.boum.org/pipermail/tails-dev/2015-February/thread.html#8038

I plan to be moderately available next month, but to keep on working on
the greeter revamp and on replacing vidalia. I'm up for taking some
review and merges too.

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] Git branches to delete: review needed

[Alan]

Hi,

intrigeri intrig...@boum.org wrote:
 Alan wrote (22 Feb 2015 02:10:26 GMT) :
  * feature/edit-additional-software-conffile: this branch adds a
subcommand to tails-additionnal software to ease creation/edition of
its configuration. I don't remember why it never got merged.
 
 The question is: should we keep it?
 
Let's say yes.

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] Git branches to delete: review needed

[Alan]

Hi,

intrigeri intrig...@boum.org wrote:
 Please have a look and shout if there's something in there that we
 should keep.
 
Looks good to me.

 Also, if you're Alan, anonym, bertagaz or sajolida, look for your name
 on that blueprint: there are a few branches I need your opinion about
 = please move them to the appropriate section.
 
* feature/edit-additional-software-conffile: this branch adds a
  subcommand to tails-additionnal software to ease creation/edition of
  its configuration. I don't remember why it never got merged.
* feature/fix_additional_software_escalation: this branch is not useful
  anymore as it addresses a problem that has been solve another way.
* feature/update_whisperback_help: I don't understand why this branch
  got lost, but we should really merge it, so don't delete it!

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] Automated builds specification

[Alan]

Hi,

intrigeri intrig...@boum.org wrote:
 bertagaz wrote (16 Feb 2015 14:32:57 GMT) :
  On Wed, Feb 11, 2015 at 11:49:02PM +0100, intrigeri wrote:
  I have a few concerns, though:
  
* Scenario 2 : developer doesn't make it clear if branch T is
  build *after being locally merged into branch B*, or not.
  Given that's what we're really interested in, and given
  Scenario 1 : reviewer is clearer (answer is: yes), I guess the
  answer is yes here too, but this should be clarified.
 
  IIRC that was something Alan had troubles with, as not being the way she
  usually work on a feature branch, which I think was more close to Work
  work work on the branch, and then when the feature is ready, merge the base
  branch in it. So she usually do not merge the base branch very often.
 
 Most of us (including me) do the same as Alan, but IMO that's almost
 irrelevant to the topic at hand. This same scenario reads:
 
And I need to know if my branch build is broken by something else
   possibly weeks after my last commit (by e.g Debian changes,
   changes in branch B, ...)
   ^^^
 
 ... and we cannot possibly get this without locally merging the topic
 branch F into B before building.
 
 The important point here may be the *locally* word. This merge would
 only be done in Jenkins own temporary Git checkout, and wouldn't
 affect how we're handling our branches' Git history.
 
  But I agree this is not the best way to go, so if Alan doesn't come up with
  a block on this, I agree to add the clarification.
 
 OK. But apparently, either I misunderstood why Alan had trouble with
 this idea, or Alan has misunderstood the idea, so IMO it would be good
 to have his opinion now that I've clarified what I think we should do,
 and why. Alan?
 
I do not see any issue with this local merge by our autobuilder. Looks
to me like the right thing to do.

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] What do we miss to replace Vidalia [was: Getting rid of Vidalia]

[Alan]

Hi again,

On Thu, 19 Feb 2015 14:23:03 +
sajolida sajol...@pimienta.org wrote:
 intrigeri:
  sajolida wrote (18 Feb 2015 11:32:17 GMT) :
  intrigeri:
  Alan wrote (12 Feb 2015 15:32:15 GMT) :
- Ability to close a circuit manually.
 
[...]
  = seems like we can address this corner case in a good-enough way
  without compromising security nor spending large amounts of energy on
  this topic.
 
 Fine with me. Still, we would need to have arm documented in the first
 place. And since I propose it to go in Advanced topics anyway we can
 explain the workaround there for now and create the upstream ticket that
 you mentioned as well.
 
+1

[About the green onion]

  Now... does Vidalia really do that? In other words, does Vidalia's
  green onion really turn yellow or red or something whenever this
  happens? I don't think so: I *believe* that Vidalia's onion indicator,
  once it has turned green, only reflects the state of Vidalia's
  connection to the Tor control port, not the state of the tor daemon's
  connection to the Tor network. I don't remember seeing it change
  colors unless I e.g. restarted Tor. I'd be happy to be proven wrong,
  though :)
 
 Same for me, I'm pretty sure that Vidalia stays green forever once Tor
 is started.

...until Vidalia loose connection to the Tor daemon.

 And I'm fine with mimicking this behavior for a start if
 that's easier to implement (no regression), but I think this is buggy
 (the onion shouldn't be green if Tor is not in a working state anymore).
 I want to replace Vidalia to get rid of its bugs not to reimplement them :)
 
  but would it be conceivable to have Tor Monitor
  appear as green onion on the desktop as Vidalia does until now?
  
I don't think it's the way to go:

- I'd like Tor Monitor to stay a generic application, with a clear
  focus on being a monitor for Tor and showing whatever icon on the
  desktop doesn't look like the same task for me.
- System Tray Icons were deprecated in Gtk since 3.14. A proper
  implementation of this green onion for GNOME 3 desktop would be a
  (very simple) Shell extension, to which we (the NetworkManager
  hook) should send a DBus signal (or the opposite). That might be a
  tiny funny project.

[...]

 Yes, and if I understood correctly Tor Monitor currently needs Tails
 Jessie. So an obvious roadmap would be to have a working replacement of
 Vidalia with Tor Monitor (without regressions) in Tails Jessie. Does
 that sound realistic? Then only we can work on making it better (eg.
 smarter onion status icon, progress bar while starting Tor, etc.).
 
  And if Tor Monitor is always running in the background, then maybe it
  could also provide information while Tor is starting and be the right
  tool to solve #7437 in the future?
  
  That's what I had hidden in the back of my head when asking this
  question initially :)
  
I'm not opposed to exposing a DBus interface in a future version of
TorMonitor to provide the green onion or other applications more
information that our hooks could. But I'm not sure it is the right
place to do it yet.

  The main problem I see with this approach is: if we go this way, then
  either Tor Monitor stops being a generic tool, but becomes yet another
  Tails-specific thing, which would make me sad.
 
 Let's try to make it generic straight away! I'd love to have it on my
 regular Debian as well.
 
Me too! I'm not really into solving all the issues we have in this
application.

  I thought about it
  a bit harder, and now it's not obvious to me what we would gain by
  merging the two tools we need into a single one:
  
   * Tails could start the Tor bootstrap and time sync progress monitor.
 Upon completion, this piece of software would either just
 terminate, or (if we need a permanent indicator that's tight to the
 actual Tor status) start Tor Monitor --hide-in-taskbar, that would
 display some onion.
  
   * Anyone else would just use Tor Monitor.
  
  And then this topic becomes mostly orthogonal to the current
  discussion, I think :)
 
For the reasons I exposed before, I don't think it's the right
solution. But you can try to convince 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.

Re: [Tails-dev] What do we miss to replace Vidalia [was: Getting rid of Vidalia]

[Alan]

Hi,

sajolida sajol...@pimienta.org wrote:
 I cloned your repo, installed python-stem, tried to run setup.py and
 tormonitor.py and got errors for both.
 
 How can I test this from Tails?
 
 $ python setup.py
   File setup.py, line 10
 requires=['stem','gi']
^
 SyntaxError: invalid syntax
 
Sorry I messed up the initial commit. Please clone the repo again, and
from Tails/Jessie:

sudo apt-get install python-stem python-pysocks
sudo ./setup.py install
sudo iptables -I OUTPUT 1 -p tcp --dport 9050 -d 127.0.0.1 -m owner
\ --uid-owner vidalia -j ACCEPT
sudo -u vidalia tormonitor

For the rest of the questions see my other email in this thread.

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] What do we miss to replace Vidalia [was: Getting rid of Vidalia]

[Alan]

Hi,

intrigeri intrig...@boum.org wrote:
 sajolida wrote (11 Feb 2015 15:12:02 GMT) :
  $ python tormonitor.py
  [Errno 13] Permission denied
  Traceback (most recent call last):
File tormonitor.py, line 346, in module
  app = TorMonitorApplication()
File tormonitor.py, line 316, in __init__
  message_format=_(Unable to connect to Tor daemon.))
 
 Seems that there's a bug in this code path.
 
I don't think that there is a bug in this code path. You need Gtk =
3.14 (basically Jessie). Please clone the repository again as I messed
up the initial commit.

 And/or maybe you're hitting this bug because you're running the code
 as the `amnesia' user, who cannot talk to the Tor control port. Try as
 the vidalia user?
 
The user running tormonitor must have access to Tor control socket
*and* to Tor SOCKS port. In Tails/Jessie:

sudo iptables -I OUTPUT 1 -p tcp --dport 9050 -d 127.0.0.1 -m owner
\ --uid-owner vidalia -j ACCEPT
sudo -u vidalia tormonitor

  Do we miss something else to replace Vidalia ?
 
[...]

- Info about relays in the circuits.
 
 Would be useful, but not a blocker IMO, since that's an advanced
 feature and is already provided by arm.
 
Tor Monitor provides this info.

- Ability to close a circuit manually.
 
 No idea what are the use case for this feature that we would want to
 support. If someone really wants it, better add it to arm IMO.
 
Tor Monitor doesn't provide this feature yet. It would be very easy to
add, even though I'm not sure I find it desirable: currently we only
*monitor* Tor. Do we also really want to *control* it?

- Ability to view logs from Tor without an
  administration password.
 
 Not sure what action one can easily take based on the info found in
 these logs, without an administration password. I say we can forget
 that one too. If someone really wants it, better add it to arm IMO.
 
That would be quite easy to add it there is a consensus that it is
useful.

- New identity (the one we have in Tor Browser does something
  different).
 
 We had plans (#5716) to hide this Vidalia feature, so I don't think we
 should add it to this new GUI. This feature is available in arm
 already anyway, for advanced users who know what they're doing, and
 for people who insist on shooting themselves in the foot.
 
Easy to add, even though I'm not convinced for the same reason as
Close circuit

- Bandwidth Graph.
 
 Advanced feature IMO, already present in arm. If we care much about
 getting this info graphically, then I think some GNOME system monitor
 would be a better tool to satisfy the need (it would be a suitable
 replacement in the context of Tails, since we're routing almost
 everything through Tor).
 
It would be possible (and I think desirable) to add a bandwidth graph to
Tor Monitor and I already thought about it. But I don't know how to
implement that in Gtk yet, and I'd better see this as a fun item than
as a required feature. Patches are welcome though, and if there is a
consensus that it is required I'll do it.

  Which one of those are you covering already or did you consider?
 
 IMO we should focus on the basic features we would strongly miss if we
 drop Vidalia, and leave anything more advanced to arm. This way, we
 keep our maintenance workload to the bare minimum, and provide
 a simpler GUI.
 
I agree on that. Currently Tor Monitor provides circuit and associated
streams, and infos on relays in a circuit. We could add the logs easily
and the bandwidth graph less easily to provide a nice monitor. I'm not
sure that the other features are desirable.

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] What do we miss to replace Vidalia [was: Getting rid of Vidalia]

[Alan]

Hi,

Vidalia is unmaintained and we were looking for solutions to get rid of
it[1]. It turned out that the main missing piece was a replacement to
its Network Map[2].

I'm working on an GTK application that shows circuits and the streams
that are attached to then, basically as the bottom left part of Vidalia's
network map[3]. It is now usable so I propose that we get rid of Vidalia for
tails/jessie.

The network status would be provided by this new Tor Monitor.

Do we miss something else to replace Vidalia ?

Cheers

[1]: https://labs.riseup.net/code/issues/6841
[2]: https://labs.riseup.net/code/issues/6842
[3]: http://git.tails.boum.org/alan/tor-monitor/
___
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.3] bugfix/8756-repair-local-packages

[Alan]

On Wed, 21 Jan 2015 18:32:39 +0100
intrigeri intrig...@boum.org wrote:
 this fixes a bug identified by Alan on
 https://labs.riseup.net/code/issues/8724#note-12
 
I'm giving up on this, which remains to be tested. See
https://labs.riseup.net/code/issues/8756#note-4.
___
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.3] bugfix/7450-too_easy_to_exit (on openpgp applet repository)

[Alan]

Hi,

On Wed, 26 Nov 2014 23:19:43 +0100
Clement Hermann nod...@nodens.org wrote:
 I fixed #7450 in my Tails OpenPGP Applet repository, in the
 bugfix/7450-too_easy_to_exit branch. It should apply cleanly on the
 version currently in Tails :
 https://git-tails.immerda.ch/nodens/openpgp-applet/commit/?h=bugfix/7450-too_easy_to_exitid=a3aa1b67fce5ce25b726beeb4c2b7b7e87736c59
 
 For now it's a simple workaround (invert about and exit buttons).
 
Merged, thanks!
___
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] Greeter mockups

[Alan]

Hi,

On Tue, 03 Feb 2015 21:19:22 +0100
intrigeri intrig...@boum.org wrote:
 FYI I'm told the blueprint is now out-of-date comparing to the current
 state of discussion and mockups.
 
Thanks for pointing this out.

 See e.g.
 https://labs.riseup.net/code/attachments/download/651/greeter1.png
 
 = likely those of us who haven't commented yet now need to wait for
 an updated blueprint etc. before commenting.
 
I'll update the blueprint once I get enough feedback on
https://labs.riseup.net/code/issues/7550

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] Hybrid ISOs: need to reconsider the plan (#8510)

[Alan]

Hi,

On Mon, 26 Jan 2015 12:38:07 +0100
intrigeri intrig...@boum.org wrote:
 Alan wrote (18 Jan 2015 13:40:37 GMT) :
  I'll do that within the week to all computers I have access to.
 
 Any regression detected?
 
No, but all the computers with a working DVD reader were fairly new.

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] [review'n'merge:jessie] feature/7756-reintroduce-whisperback

[Alan]

Hi,

Please review feature/7756-reintroduce-whisperback, which should fix
#7756 - Reintroduce WhisperBack in Jessie ISOs
(https://labs.riseup.net/code/issues/7756).

More info on the ticket.

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.3] feature/6992-whisperback-email-address

[Alan]

On Fri, 16 Jan 2015 20:19:45 +0100
intrigeri intrig...@boum.org wrote:
 please review'n'merge into devel for 1.3.
 Details are in the commit message and on the ticket.
 
Merged thanks!
___
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] [review'n'merge:jessie] whisperback:feature/python3

[Alan]

Hi,

Please review whisperback:feature/python3, which should fix
#7755 - Migrate WhisperBack to Python 3
(https://labs.riseup.net/code/issues/7755).

More info on the ticket.

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] Hybrid ISOs: need to reconsider the plan (#8510)

[Alan]

Hi,

 I prefer option C: #8524 won't tell us much anyway, it's merely here
 to evaluate the size of the subset of Tails users who will have risks
 of regressions a) they boot Tails from DVD; and b) their BIOS is buggy
 enough to not boot properly from a DVD burnt from a ISO image.
 It won't actually reduce that risk in any way, but will merely give us
 more confidence that we're not potentially impacting to
 many people.
 
 Thoughts?
 
I'm fine with option C especially if as much people as possible try
booting isohybrid DVDs on various computers. I'll do that within the
week to all computers I have access to.

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.2.2] bugfix/6538-Tails-Installer-tries-to-install-to-too-small-devices

[Alan]

Hi!

  I reviewed the new patch but had a few concerns with it. Please
  have a look at https://labs.riseup.net/code/issues/6538
 
 Ok I have made the required changes.
 
 
Thanks! I'm not sure to have time to take care of that in the next few
days thought. If someone else feels like it, don't hesitate.
___
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.2.1] bugfix/7678-Tails-Installer-crashes-on-upgrade

[Alan]

Hi!

On Wed, 7 Jan 2015 18:58:22 +0100
kurono andres.go...@cern.ch wrote:
   
  pre -toplevels = config['liveos_toplevel_files'] -
  for f in toplevels: +for f in
  config['liveos_toplevel_files']: /pre
  
 
 Ok the new version is in
 http://git.tails.boum.org/kurono/liveusb-creator/ the branch is the
 same bugfix/7678-Tails-Installer-crashes-on-upgrade.
 
Thanks! I'm not sure to have time to take care of that in the next few
days thought. If someone else feels like it, don't hesitate.

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] Windows camouflage for Jessie/GNOME shell

[Alan]

Hi!

On Sat, 03 Jan 2015 17:17:08 +
sajolida sajol...@pimienta.org wrote:
 [...] Then I also think that it is important to request them
 to send regular updates on their progress. Because if we have 5-10
 answers and they all start exploring the basics in parallel, then it's
 important to be able to identify quickly who is really capable and
 dedicated to do the work, so we can maybe assign them complementary
 tasks instead of having them duplicate the same work in parallel. In
 GSOC they ask for weekly reports, right? Maybe that's a bit too much
 but every two weeks sounds good, no?
 
Let's try that.

 So feel free to merge news/windows_camouflage_jessie into master
 whenever you want. Then I'll do a bit of Twitter.
 
Done. Please proceed.
___
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] Windows camouflage for Jessie/GNOME shell

[Alan]

Hi,

On Thu, 01 Jan 2015 13:06:04 +
sajolida sajol...@pimienta.org wrote:
 Alan:
  % Call for participation : port windows camouflage to GNOME 3.14
 
 I added this to a branch. See the current version of the call here:
 
 http://git.tails.boum.org/tails/tree/wiki/src/news/windows_camouflage_jessie.mdwn?h=news/windows_camouflage_jessie
 
Thanks!

 I was wondering whether we should use a shorter title. We use a big
 font for titles (that could be fixed) but I'd like to see if we can
 avoid wrapping titles. That's why I did a731b9f. Feel free to revert
 it if you don't like it as I'm not 100% convinced either.
 
A shorter title looks fine indeed, but I'm a bit concerned about
loosing the call or help idea. What about Help porting Windows
camouflage to GNOME 3.14?

  # Where should you start?
 
  Please read
  https://tails.boum.org/blueprint/update_camouflage_for_jessie/, then
  write to tails-dev@boum.org. This is a public mailing list:
  https://mailman.boum.org/listinfo/tails-dev/ Please subscribe!
 
 I'm a bit concerned about what will happen once we sent out the call.
 Hopefully we will have between 5 and 10 answers from random people who
 will write to the list saying hello, I'm interested in this. What
 are you going to answer them?
 
Thanks for pointing this out. My rought idea: if they have questions,
answer them, else, tell them to DL and start tails/jessie and hack, and
see what they produce. If there are several motivated answers then I
think it's possible to split the work (e.g. icons/gtk/shell). I guess
more than half of the people won't produce anything, but if someone has
a convincing theme that would be a good start.  I hope we would then
do the integration and polishing together but I'm not that confident on
that part.

 Because if we're interested in their past experience on GNOME before
 we spend time mentoring them, then we might as well ask this upfront.
 
I thought that the first sentences made quite clear that we'd like some
experience in theming of GTK/GNOME. But I'd rather not set some strict
requirement as somebody motivated enough can do a good job even if they
have no passed GNOME experience I think. e.g. perhaps experience in web
development with JS and CSS forks perfectly.

 You also silently ignored my concern about money. If giving out money
 can help us recruiting more qualified people and do less filtering and
 mentoring, them I'm all for it. But then I'm not sure whether you like
 the idea of being mentoring someone else who is being paid and I'm not
 sure how to put it in the announcement in the first place so I'm ok to
 try without mentioning money at all first.
 
I'm not interested in dealing with this money issue, but I'm not
against it if you or someone else wants to take care of it. However, I
think that we should not promise anything before being sure there is
real good work behind. So if you think we could have money for this and
want to take care of it, I'd propose not to mention it on the 1st
place, but:

- if someone asks, answer than that we can give them money;
- additionally, if someone comes up with a convincing POC, propose them
  money to work on the shitty details fixing;
- make very clear the requirements before money arrives: if we pay
  somebody who only does the funny parts and then let me do the shitty
  fixing, I'd feel tricked.

What do you think?

 We might as well delay those questions for once the call is passed,
 but our past experience with the bounty program proved that getting
 external people to do work for us definitely doesn't come for free
 (as in free time)!
 
Indeed thanks for sharing your experience. I'm a bit afraid of that
too, but let's see what happens...

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] error

[Alan]

Hi,

This is the public mailing list for Tails development. I forwarded your
email to the public support list tails-supp...@boum.org.

Cheers

On Wed, 31 Dec 2014 17:24:55 +0100
oraj o...@onet.com.pl wrote:

 Dear Sir
 Yours new wersion of Tails 1.2.2 probably has an error.I tried create
 iso on usb when this information show me. 
 ERROR REPORT ( 12/31/2014 16:57:06 )
 Please submit this error report to developer.
 Operating System version  :Microsoft Windows NT 6.2.9200.0
 .NET Framework version    :4.0.30319.18449
 Error Message            :
 Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0,
 Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its
 dependencies. Nie można odnaleźć określonego pliku. StackTrace
         : at A.V.D() at A.V.D(ImageItemBase , ProcessLog )
    at A.KB.D()
    at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
    at System.Threading.ExecutionContext.RunInternal(ExecutionContext
 executionContext, ContextCallback callback, Object state, Boolean
 preserveSyncCtx) at
 System.Threading.ExecutionContext.Run(ExecutionContext
 executionContext, ContextCallback callback, Object state, Boolean
 preserveSyncCtx) at
 System.Threading.ExecutionContext.Run(ExecutionContext
 executionContext, ContextCallback callback, Object state) at
 System.Threading.ThreadHelper.ThreadStart() I am sorry for my basic
 english but I suppose this information is important. Yours faithfully 
  

___
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] Windows camouflage for Jessie/GNOME shell

[Alan]

Hi,

On Wed, 31 Dec 2014 10:57:00 -0500
Daniel Kahn Gillmor d...@fifthhorseman.net wrote:
 On 12/28/2014 07:03 PM, Alan wrote:
 
  Please find below a blog post proposal.
 
 Thanks for this, Alan.  I would be happy to see it published.  A
 couple native-english-speaker suggestions below:
 
Thanks for your corrections and explanations.

Please find below an hopefully corrected version

I'd like to publish it on tails.boum.org/news/ next week.
I don't know where we want to post links to it: twitter? Anybody knows
where to contact the GNOME community with such a post?

Cheers

* * *

% Call for participation : port windows camouflage to GNOME 3.14

Are you into GNOME development and want to participate to Tails?
Do you want to improve your GTK and/or GNOME Shell theming skills while
supporting users needing privacy and stealth? Consider porting Tails's
Windows camouflage to GNOME 3.14

# What is Windows camouflage?

Tails documentation reads if you are using a computer in public you
may want to avoid attracting unwanted attention by changing the way
Tails looks into something that resembles Microsoft Windows 8. This is
what we call the Windows camouflage.

# Why is it useful?

We got reports that users have been arrested while using a
privacy-enhancing distribution because their screen looked very
different from others, which raised suspicion. It's why Windows
camouflage has been added to Tails.

# What should be done?

Current Tails is based on GNOME 3.8 in Fallback mode. We are
currently upgrading Tails on top of the upcoming version on Debian
(Jessie) which is based on GNOME 3.14. Windows Camouflage should be
upgraded to the last version of GTK and ported from GNOME Panel to
GNOME shell. That includes GTK and GNOME Shell theming through CSS as
well as writing a custom GNOME Shell extension.

# Why do we need you?

The team currently working on Tails is very busy and
decided to focus on the core or the upgrade rather than on Windows
Camouflage. We currently plan to go ahead with the initial Tails/Jessie
release even if the Windows Camouflage is missing. However,
we would love to ship Windows camouflage and think it's a good occasion
for you to give a hand. We'll provide support to anybody volunteering
and work together on integrating the new theme to upcoming Tails/Jessie
snapshots.

# Where should you start?

Please read
https://tails.boum.org/blueprint/update_camouflage_for_jessie/, then
write to tails-dev@boum.org. This is a public mailing list:
https://mailman.boum.org/listinfo/tails-dev/ Please subscribe!

___
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] Windows camouflage for Jessie/GNOME shell

[Alan]

Hi,

Please find below a blog post proposal.

Cheers

---

% Call for participation : port windows camouflage to GNOME 3.14

You are into GNOME development and want to participate to Tails? You
improve your GTK and/or GNOME Shell theming skills and want to support
users needing privacy and stealth? Consider porting Tails's Windows
camouflage to GNOME 3.14

# What is Windows camouflage?

Tails documentation reads if you are using a computer in public you
may want to avoid attracting unwanted attention by changing the way
Tails looks into something that resembles Microsoft Windows 8. This is
what we call the Windows camouflage.

# Why is it useful?

We got reports that users has been arrested while using a
privacy-enhancing distribution because their screen looked very
different from others, which raised suspicion. It's why Windows
camouflage has been added to Tails.

# What should be done?

Current Tails is based on GNOME 3.8 in Fallback mode. We are
currently upgrading Tails on top of the upcoming version on Debian
(Jessie) which is based on GNOME 3.14. Windows Camouflage should be
upgraded to the last version of GTK and ported from GNOME Panel to
GNOME shell. That includes GTK and GNOME Shell theming though CSS as
well as writing a custom GNOME Shell extension.

# Why do we need you?

The team currently working on Tails on the long run is very busy and
decided to focus on the core or the upgrade rather than on Windows
Camouflage. We thus decided to consider the possible lack of Windows
Camouflage as NOT blocking the initial Tails/Jessie release. However,
we would love to ship Windows camouflage and think it's a good occasion
for you to give a hand. We'll provide support to anybody volunteering
and work together on integrating the new theme to upcoming Tails/Jessie
snapshots.

# Where should you start?

Please read
https://tails.boum.org/blueprint/update_camouflage_for_jessie/, then
write to tails-dev@boum.org. This is a public mailing list which you
are welcome to subscribe: https://mailman.boum.org/listinfo/tails-dev/.
___
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] quto; qted testing [was: feature/6880-torsocks-2, aka. drop Polipo and install torsocks 2.0]

[Alan]

Hi,

intrigeri:
 Alan wrote (25 Dec 2014 16:39:02 GMT) :
  I only did manual test of the modified applications
  and random other internet applications as I still don't have a
  reliable automated testing setup. If someone wants to run the
  automated test suite on current devel taht would be awesome.
 
 Tails 1.3 is scheduled to be released on 2015-02-24. Maybe you'll find
 time to get yourself an automated testing setup by then?
 
I's not a matter of time: as we had the occasion to see earlier, I
have a working setup but I get more or less random failures and I have
no idea what to change to solve them. So my setup is useless.

If one of the test suite experts have time to try to debug that I'd be
glad to work on it but honestly I have no idea where to start.

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.3] feature/6880-torsocks-2, aka. drop Polipo and install torsocks 2.0

[Alan]

Hi,

 Alan wrote (23 Dec 2014 16:45:22 GMT) :
  I checked the diff and tested wget, APT, Totem and GnuPG that all
  work fine under experimental. Tickets and design doc liiks fine too.
 
 Cool, thanks for the review!
 
 Please test the branch once merged into devel before pushing the final
 merge, as various unrelated stuff has started accumulating
 in experimental.
 
Done and pushed.

I only did manual test of the modified applications
and random other internet applications as I still don't have a reliable
automated testing setup. If someone wants to run the automated test
suite on current devel taht would be awesome.

  The only issue blocking the merge are useless unset lines in wget
  wrapper: [...]
 
 Answered on the ticket, reassigned to you.
 
 [Please don't start the very same discussion in two places at the same
 time, it becomes really confusing as soon as someone replies in one
 place, and someone (possibly else) replies in the other. Thanks!]
 
Do you prefer email or the ticket?
___
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] fix-committed issues [was: Git/Redmine integration: fixing a regression with new goodies?]

[Alan]

Hi,

  * fix-committed: # will flag # as Fix committed
 
This keyword MAY be used in the commit message when merging
a branch with --no-ff. It MUST not be used anywhere else. If the
reviewer+merger chooses not to use it, then they MUST manually flag
the ticket as Fix committed, just like we've been doing
until now.
 
I tried this for #5379 and found a few annoying things:

 - it doesn't remove me from assignee
 - it doesn't mark subtickets as fix-committed. Should I add the
   fix-commited keyword with every subticket id?

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] fix-committed issues [was: Git/Redmine integration: fixing a regression with new goodies?]

[Alan]

   * fix-committed: # will flag # as Fix committed
  
 This keyword MAY be used in the commit message when merging
 a branch with --no-ff. It MUST not be used anywhere else. If the
 reviewer+merger chooses not to use it, then they MUST manually
  flag the ticket as Fix committed, just like we've been doing
 until now.
  
 I tried this for #5379 and found a few annoying things:
 
  - it doesn't remove me from assignee
  - it doesn't mark subtickets as fix-committed. Should I add the
fix-commited keyword with every subticket id?
 
and QA Check should be set to fix committed.

I'm excited to get this!
___
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.3] bugfix/8470-clean-up-apt-pinning

[Alan]

 this branch removes obsolete APT pinning config for XUL extensions
 we're now taking from the Tor Browser tarball, instead of from Debian.
 
Merged thanks!
___
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] Release schedule for Tails 1.2.2

[Alan]

Hi,

 Me and intrigeri are going to work together on the final image
 building, starting early (CET) on 2015-01-13, and if we're efficient,
 we may even try to release 1.2.2 on the same day. This may depend on
 testers being on call late (CET) that day.
 
 So, testers, please let me know if you are available on:
 
 * 2015-01-13, late (CET)?
 
I can commit to several hours of testing during the evening e.g my
favorite activity or reviewing changes.

 * 2015-01-14, early and afternoon (CET)?
 
Unfortunately not.

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] Meeting: our Tails/Jessie progress and plans

[Alan]

Hi,

 intrigeri wrote (17 Dec 2014 17:07:26 GMT) :
  I say let's do that, cover what we can, and if it doesn't fit or if
  we need Alan and he's not here, then we can still schedule another
  meeting. Let's keep this thing rolling!
 
I'm very sorry I missed the meeting. That was an organisation problem
of mine. Please accept my apologies.

 It has happened. anonym and I went through the list of non-doc open
 tickets, and set priority + assignee:
 
   * low prio = no blocker for the initial Tails/Jessie release
   * elevated prio = regression, or similar
   * high prio = blocks other important work
   * normal prio = anything else
 
Thanks for your work.

 I propose we have another meeting in a month, shortly after the next
 release, e.g. on January 16. As I see it, the main goal, this time,
 would be to see how we're doing wrt. getting the fixes we need into
 Jessie, and re-prioritize anything that is lagging behind on
 that front.
 
 anonym, Alan, others?
 
That should work for me and this time is clearly written in my agenda.
However I missed the time. 8:30PM CET?

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] Windows camouflage for Jessie/GNOME shell

[Alan]

Hi,

 * let's specify how Tails/Jessie's Windows Camouflage should
   look like, and put the implementation ideas and pointers we have
   into a blueprint
 
  I can do a blueprint specifying the must and extras.
 
 Awesome!
 
Please review
https://tails.boum.org/blueprint/update_camouflage_for_jessie/.
Once it is agreed next step is to issue a blog post about this.

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.3] feature/6880-torsocks-2, aka. drop Polipo and install torsocks 2.0

[Alan]

Hi,

I checked the diff and tested wget, APT, Totem and GnuPG that all
work fine under experimental. Tickets and design doc liiks fine too. The
only issue blocking the merge are useless unset lines in wget wrapper:

/usr/local/bin/wget includes

unset http_proxy
unset HTTP_PROXY
unset https_proxy
unset HTTPS_PROX

while these variables are not set anymore (see 32897af7). Why? Please
provide a reason or remove these lines.

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.2.1] bugfix/7678-Tails-Installer-crashes-on-upgrade

[Alan]

Hi,

 Ticket: https://labs.riseup.net/code/issues/7678
 
 I don't have yet a liveusb-creator repo yet, (If I remember correctly
 already sent the requirement). So I am attaching the patch.
 
Thanks for the patch which I imported into liveusb-creator repository
in the feature branch.

I confirm the patch fixes the issue.

A tiny comment though: as @toplevels@ is only used once, so why not to
write one less line:

pre
-toplevels = config['liveos_toplevel_files']
-for f in toplevels:
+for f in config['liveos_toplevel_files']:
/pre

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] Build failed in Jenkins: build_Tails_ISO_experimental #1457

[Alan]

These are the result of review and merges that built fine on my machine.
I don't understand where is the problem...

On Tue, 23 Dec 2014 10:15:18 -0800 (PST)
tails-sysadm...@boum.org wrote:

 See
 https://jenkins.tails.boum.org/job/build_Tails_ISO_experimental/1457/changes
 
 Changes:
 
 [amnesia] Invert Exit and About in gpgApplet context menu
 
 --
 [...truncated 3957 lines...]
 I: Unpacking apt...
 I: Unpacking apt-utils...
 I: Unpacking libapt-inst1.5:i386...
 I: Unpacking libapt-pkg4.12:i386...
 I: Unpacking aptitude...
 I: Unpacking aptitude-common...
 I: Unpacking libboost-iostreams1.49.0...
 I: Unpacking bsdmainutils...
 I: Unpacking cpio...
 I: Unpacking cron...
 I: Unpacking libcwidget3...
 I: Unpacking debian-archive-keyring...
 I: Unpacking dmidecode...
 I: Unpacking libstdc++6:i386...
 I: Unpacking libgdbm3:i386...
 I: Unpacking gnupg...
 I: Unpacking gpgv...
 I: Unpacking libgnutls26:i386...
 I: Unpacking groff-base...
 I: Unpacking ifupdown...
 I: Unpacking iproute...
 I: Unpacking iptables...
 I: Unpacking iputils-ping...
 I: Unpacking isc-dhcp-client...
 I: Unpacking isc-dhcp-common...
 I: Unpacking kmod...
 I: Unpacking libkmod2:i386...
 I: Unpacking libept1.4.12...
 I: Unpacking libgcrypt11:i386...
 I: Unpacking libgpg-error0:i386...
 I: Unpacking libidn11:i386...
 I: Unpacking libnfnetlink0...
 I: Unpacking libpipeline1:i386...
 I: Unpacking libsigc++-2.0-0c2a:i386...
 I: Unpacking libtasn1-3:i386...
 I: Unpacking libusb-0.1-4:i386...
 I: Unpacking logrotate...
 I: Unpacking man-db...
 I: Unpacking manpages...
 I: Unpacking nano...
 I: Unpacking libncursesw5:i386...
 I: Unpacking net-tools...
 I: Unpacking netbase...
 I: Unpacking netcat-traditional...
 I: Unpacking libnewt0.52...
 I: Unpacking whiptail...
 I: Unpacking libssl1.0.0:i386...
 I: Unpacking libp11-kit0:i386...
 I: Unpacking libpopt0:i386...
 I: Unpacking libprocps0:i386...
 I: Unpacking procps...
 I: Unpacking libreadline6:i386...
 I: Unpacking readline-common...
 I: Unpacking rsyslog...
 I: Unpacking libsqlite3-0:i386...
 I: Unpacking tasksel...
 I: Unpacking tasksel-data...
 I: Unpacking info...
 I: Unpacking install-info...
 I: Unpacking traceroute...
 I: Unpacking libudev0:i386...
 I: Unpacking udev...
 I: Unpacking vim-common...
 I: Unpacking vim-tiny...
 I: Unpacking wget...
 I: Unpacking libxapian22...
 I: Configuring the base system...
 I: Configuring gpgv...
 I: Configuring libssl1.0.0:i386...
 I: Configuring libgdbm3:i386...
 I: Configuring isc-dhcp-common...
 I: Configuring libtasn1-3:i386...
 I: Configuring libpopt0:i386...
 I: Configuring libusb-0.1-4:i386...
 I: Configuring libgpg-error0:i386...
 I: Configuring install-info...
 I: Configuring vim-common...
 I: Configuring libprocps0:i386...
 I: Configuring netbase...
 I: Configuring dmidecode...
 I: Configuring libudev0:i386...
 I: Configuring libkmod2:i386...
 I: Configuring adduser...
 I: Configuring traceroute...
 I: Configuring manpages...
 I: Configuring libsqlite3-0:i386...
 I: Configuring iproute...
 I: Configuring libidn11:i386...
 I: Configuring libnewt0.52...
 I: Configuring net-tools...
 I: Configuring libpipeline1:i386...
 I: Configuring bsdmainutils...
 I: Configuring netcat-traditional...
 I: Configuring debian-archive-keyring...
 I: Configuring libncursesw5:i386...
 I: Configuring info...
 I: Configuring iputils-ping...
 I: Configuring aptitude-common...
 I: Configuring cron...
 I: Configuring nano...
 I: Configuring libp11-kit0:i386...
 I: Configuring rsyslog...
 I: Configuring cpio...
 I: Configuring libstdc++6:i386...
 I: Configuring isc-dhcp-client...
 I: Configuring vim-tiny...
 I: Configuring readline-common...
 I: Configuring libnfnetlink0...
 I: Configuring libgcrypt11:i386...
 I: Configuring procps...
 I: Configuring libxapian22...
 I: Configuring whiptail...
 I: Configuring ifupdown...
 I: Configuring kmod...
 I: Configuring libapt-pkg4.12:i386...
 I: Configuring libept1.4.12...
 I: Configuring libapt-inst1.5:i386...
 I: Configuring libreadline6:i386...
 I: Configuring logrotate...
 I: Configuring libboost-iostreams1.49.0...
 I: Configuring groff-base...
 I: Configuring gnupg...
 I: Configuring libsigc++-2.0-0c2a:i386...
 I: Configuring libgnutls26:i386...
 I: Configuring apt-utils...
 I: Configuring udev...
 I: Configuring iptables...
 I: Configuring man-db...
 I: Configuring apt...
 I: Configuring wget...
 I: Configuring libcwidget3...
 I: Configuring aptitude...
 I: Configuring tasksel...
 I: Configuring tasksel-data...
 I: Base system installed successfully.
 P: Begin caching bootstrap stage...
 P: Begin unmounting filesystems...
 P: Setting up cleanup function
 P: Begin caching chroot stage...
 P: Begin mounting /dev/pts...
 P: Begin mounting /proc...
 P: Begin mounting /sys...
 P: Configuring file /etc/debian_chroot
 P: Configuring file /sbin/start-stop-daemon
 P: Configuring file /usr/sbin/policy-rc.d
 P: Configuring file /usr/sbin/initctl
 P: Configuring file /etc/hosts
 P: Configuring 

Re: [Tails-dev] Windows camouflage for Jessie/GNOME shell

[Alan]

sajolida sajol...@pimienta.org wrote:
 intrigeri:
  Alan wrote (02 Dec 2014 14:24:35 GMT) :
  Do we still want to provide Windows Camouflage? How much energy do
  we want to put in it and who wants to participate?
  
  My current position is:
  
* let's focus on everything else that's on our way towards
  releasing Tails/Jessie
* let's not consider the possible lack of Windows Camouflage as
  blocking the initial Tails/Jessie release

I agree on not having camouflage blocking for Tails/Jessie.

* let's specify how Tails/Jessie's Windows Camouflage should look
  like, and put the implementation ideas and pointers we have into
  a blueprint

I can do a blueprint specifying the must and extras. Do you agree on
what I proposed ? (desktop interface looking like Win 8/8.1, no
requirement for metro-like interface in activities overview).

* let's make the two first above points clear, e.g. in a blog post
  calling for help and pointing to the blueprint = if volunteers
  show up, then awesome, Alan can give them a hand while focussing
  primarily on other Tails/Jessie -related tasks
 
 Same here. I would try to make this problem more public and see if we
 can find people or money to do that externally or only once we sorted
 out the rest of Tails Jessie.
 
I would accept to give people a hand but don't see myself do a full
mentoring of volunteers  alone without participating in the funny
tasks.

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] Git/Redmine integration: fixing a regression with new goodies?

[Alan]

Hi,

  * will-fix: # will flag # as In Progress
 
  * fix-committed: # will flag # as Fix committed
 
 It seems to work, see e.g. https://labs.riseup.net/code/issues/8359.
 
 So, if you folks are happy enough with that, I can encode this into
 [[contribute/*]] (merge policy, Redmine doc, whatever).

Looks very nice! I'll test it next time I do a review. I propose we
don't change the doc until at least one other person than you tries it.

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] Release schedule for Tails 1.2.1

[Alan]

Hi,

 Mozilla broke TBB's deterministic build setup with ESR 33.3.0, and
 while we may have linux32 builds of TBB 4.0.2 ready later today,
 they'll be without QA. Therefore I think we should delay Tails 1.2.1
 with one day, so we test and release on 2014-12-03. Any objections to
 this new plan?
 
As I said earlier in this thread I won't be available tomorrow.

Good luck!

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] Meeting: our Tails/Jessie progress and plans

[Alan]

Hi,

  I think it's time to meet, talk and adjust our plans. I hereby
  propose a dedicated meeting at 4pm CET on December 18, 19 or 20.
 
 I do not expect to make it any of these dates. What about December 15,
 16, or 17? Worst case, if your proposed dates are the only ones that
 work for you, I may be able to make it on the 18th, but then it has to
 be earlier, maybe at 12:00 CET.
 
I'm interested to attend. I'm available the 15th, 16th and 18th.

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] Release schedule for Tails 1.2.1

[Alan]

Hi,

 Who's available for testing the final 1.2.1 image on 2013-12-02?

Me.

 In case there's a delay, who's available the day after, on 2013-12-03?
 
No sorry.

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] setxkbmap under tails [was: Please test l10n status of Tails/Jessie]

[Alan]

Hi,

On Wed, 08 Oct 2014 11:04:41 +0200
intrigeri intrig...@boum.org wrote:
  setxkbmap de does not work. no error, but it simply stays in
  english.
 
 Both `setxkbmap us' and `setxkbmap de' seem to work here. The layout
 indicator in GNOME's top panel isn't updated, but the active
 layout is.
 
Using setxkbmap under GNOME is not supported ias far as I know. Please
use System Settings or gsettings (org.gnome.desktop.input-sources).

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] On keeping Tails running with the laptop lid shut

[Alan]

Hi,

 sajol...@pimienta.org wrote (06 Oct 2014 22:57:12 GMT) :
  exit-1 wrote:
  gsettings set org.gnome.settings-daemon.plugins.power
  lid-close-ac-action nothing
 
 Does this blank the screen to prevent overheating?

No. This is lid-close-ac-action=blank which is current Tails
default.

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] Release schedule for Tails 1.2

[Alan]

Hi,
 
   2014-10-07   Tag 1.2-rc1 in Git
Build and upload 1.2-rc1 ISO/IUKs
   2014-10-08   Test and release 1.2-rc1
 
   2014-10-15   TBB 4.0 is hopefully officially released
Tag 1.2 in Git
Build and upload 1.2 ISO and IUKs
   2014-10-16   Test and release Tails 1.2
 
 What do you think? Who would be available for testing?

I can definitely participate to test the rc.

I can arrange to be available to test the final ISO but I'd prefer not
to.

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] Release schedule for Tails 1.2

[Alan]

Hi,

 So, I wonder if, maybe, it would be a good idea to postpone the RC
 a bit, say:
 
2014-10-05   Import the new Tor Browser 4.0-something based on
 Firefox ESR31; adjust what needs to be adjusted (I can
 commit to be available and help with testing,
 identifying issues, review'n'merging)
2014-10-06   Finish the above, build and upload RC ISO/IUKs
2014-10-07   Test and release 1.2~rc1 (I can commit to help with
 the test suite and some bits of the release process,
 e.g. translating the changelog into the end-user
 announce)

[...]

 Thoughts?

Looks good. Having the wrong firefox/tor browser in the RC seems not
so good.
___
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.2] feature/5373-replace-truecrypt

[Alan]

Hi,

On Mon, 22 Sep 2014 09:58:59 -0700
intrigeri intrig...@boum.org wrote:
 sajol...@pimienta.org wrote (20 Sep 2014 14:36:55 GMT) :
  See 6c266c5.
 
 I think you forgot to push = reassigning the ticket to you.

I assigned https://labs.riseup.net/code/issues/5932 and
https://labs.riseup.net/code/issues/7739 to me *but* it looks they are
not actually ready to review as they depend
on https://labs.riseup.net/code/issues/6052 (the documentation) which
doens't look ready yet.

I few comments however, as of commit 82722e8:

- code looks good to me ;
- the part about setting up a loopback device in the documentation is
  useless, it works well without it as of my tests ;
- I tested feature and the warning and it works well.

Please ping me when the doc is ready so that I can actually merge the
branch.

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] Jessie session localization (#7897)

[Alan]

Hi,

I'm giving up on https://labs.riseup.net/code/issues/7897: Fix
localization of GNOME session. We have a working workaround but I can't
find a proper fix after hours of research and tests.

Would someone please have a look? Should we ask GNOME developers?
Consider the fix good enough?

Thanks by advance,

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] Jessie!

[Alan]

Hi,

On Mon, 08 Sep 2014 23:36:16 +0200
anonym ano...@riseup.net wrote:
 [...]
* #7560 - Have Tails based on Jessie starting [anonym] = ETA?
  (blocked by #7561 [alan]; otherwise, the only remaining sub-task
  seems to be #7633 Session fails to load in Jessie... until we
  discover other blockers)
 
 After two full days of parsing debug logs of all possible GNOME
 components and looking at all the wrong things, I've now solved
 #7633/#7673 with a one byte patch in Tails Greeter (commit 1189bd4)...
 
Congrats!

However with current tails jessie I hit a new bug: it displays Oh no!
Something had gone wrong instead of the greeter. Filed as
https://labs.riseup.net/code/issues/7890. I'll investigate this later
today, but any hind is appreciated.

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] Release schedule for Tails 1.2

[Alan]

Hi,

 I'll be the release manager for Tails 1.2, scheduled to be released
 on
 2014-10-14.
 
 Here's the preliminary release schedule:
 
Thanks!

 Tails contributors, please let me know which of you are available for
 testing the RC image and final image on 2014-09-30 and 2014-10-13,
 respectively.
 
I should be available on both dates but would rather only engage for
one. So let's see other's availabliliy.

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] Jessie!

[Alan]

Hi,

 at the summit, we have decided a timeline for getting our stuff ready
 to be tested on Jessie. We're far from being there yet, and given the
 Jessie freeze is on November 5th, in practice packages MUST have
 reached testing by October ~25th. That gives us less than two months
 to discover bugs and have them fixed and uploaded. I don't feel like
 it's a lot of time.
 
Thanks for the reminder.

 The parent ticket that tracks what we need to do ASAP is:
 
   https://labs.riseup.net/code/issues/7423
 
 Below, I'll list the tasks I'm the most concerned about, because they
 are blocking other things we should do way before the freeze, and then
 should *really* be completed *soon*. Most of these tasks are on Alan's
 and anonym's plate (Cc'd), but I guess they wouldn't mind some help:
 
   * #7568 - Write instructions to access the localized desktop without
 a working Greeter [alan] = ETA?
 
It turned out that what worked before the migration of GTK 3.12
doesn't work anymore. So it's more work that I thought, but I'll try
to get something working by the 14th. Help is welcome though.

   * #7561 - Update the Greeter for Jessie [alan] = ETA?
 (note that fixing #7568 is enough to unblock some of the other
 tasks that are not listed here, but *not* enough for some others,
 e.g. the test suite update)
 
It was also broken by the migration of 3.12. I'll fix it (or report why
I can't...) the 14th.

   * #7564 - Test Jessie's GNOME Shell with llvmpipe on old-ish
 hardware (e.g. ThinkPad X32, ThinkPad X60) = I can't do that before
 early October, so it would be great if someone else did.
 
I can try to do that depending on how much time the greeter things take.

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 test Tails ISO with updated syslinux

[Alan]

Hi,

Please find below test results on the following system:

Handle 0x001B, DMI type 1, 27 bytes
System Information
Manufacturer: Apple Inc.
Product Name: MacBookPro9,2
Version: 1.0
Family: MacBook Pro

My apologies for the delay.

On Mon, 28 Jul 2014 22:31:59 +0200
intrigeri intrig...@boum.org wrote:
 So, here's what I need you to do:
 
   1. Take notes about how the hardware you have supports Tails 1.1, in
  terms of does it boot at all:
  - using a DVD

Boots fine. The DVD is labeled Windows. Compatibility mode is used
(the kernel use BIOS boot). Shutdown works.

  - using a USB device installed the good old manual (isohybrid +
cat) way

Boots fine. The USB is labeled Windows. Compatibility mode is used
(the kernel use BIOS boot). Shutdown works.

  - using a USB device installed with Tails Installer

Boots fine. The USB is labeled EFI Boot. Actual EFI is used. Shutdown
fails.

  - using a USB device installed with the Universal USB Installer

There are two entries in the apple boot menu:

- one labeled Windows that boots fine. Compatibility mode is used
  (the kernel use BIOS boot). Shutdown works.
- one labeled EFI Boot that does NOT boot. The display freezes on
  the apple boot menu as soon as the entry is selected. There is no
  syslinux menu displayed and kernel never starts.

  - all of the above, but switching from Legacy mode (MBR) to UEFI,
or vice-versa
 
This system cannot be configured to use MBR instead of UEFI as far as
I know.

   2. Download the latest ISO built from the experimental branch:
  http://nightly.tails.boum.org/build_Tails_ISO_experimental/
 
I used the following tails experimental ISO:

1.2 - 20140814
c183ad91bce6c0fa4a95c387c8f5c8387acf9a0c

   3. Try starting Tails with a device created using this ISO, and take
  detailed notes of any regression or improvement compared to
  Tails 1.1:
  - using a DVD

Same as with Tails 1.1.

  - using a USB device installed the good old manual (isohybrid +
cat) way

Same as with Tails 1.1.

  - using a USB device installed with Tails Installer

Same as with Tails 1.1.

  - using a USB device installed with the Universal USB Installer

Same as with Tails 1.1.

  - all of the above, but switching from Legacy mode (MBR) to UEFI,
or vice-versa
 
This system cannot be configured to use MBR instead of UEFI as far as
I know.

 What I am *particularly* interested about is:
 
   * Regressions.
 
None on this hardware.

   * Improvements.
 
None on this hardware.

   * Tests with our boot menu background image re-enabled, especially
 on Mac. Uncomment this line in EFI/BOOT/stdmenu.cfg on the Tails
 USB stick:
 
   menu background splash.png
 
Fails to boot. The display freezes on
the apple boot menu as soon as the entry is selected. There is no
syslinux menu displayed and kernel never starts.

   * Especially on Mac, same as above, but also add this line to
 EFI/BOOT/tails.cfg on the Tails USB stick:
 
   MENU RESOLUTION 1024 768
 
Boots fine. The USB is labeled EFI Boot. Actual EFI is used. Shutdown
fails. Theres is however no change on the syslinux menu resolution.

I also tried adding both menu background splash.png and MENU
RESOLUTION 1024 768. It fails to boot. The display
freezes on the apple boot menu as soon as the entry is selected. There
is no syslinux menu displayed and kernel never starts.

   * Tests in QEMU with OVMF (if you don't know what I'm talking
 about, don't bother).

- Boots fine. Fails to shutdown (hangs at Starting new kernel).
- with menu background splash.png: boots fine. The syslinux menu is
  as beautiful as when booting in MBR mode.
- with MENU RESOLUTION 1024 768: boots fine. The menu is smaller.
- with menu background splash.png and MENU RESOLUTION 1024 768:
  boots fine. The menu is smaller and the background gets tiled
  (repeated as 2x2 tiles) which is ugly.
___
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.1] bugfix/7691-fix-ftbfs-with-apt-get-source-syslinux [Was: dpkg-dev / libdpkg-perl errors during build]

[Alan]

Hi,

On Thu, 31 Jul 2014 11:46:35 +0200
intrigeri intrig...@boum.org wrote:
 Kill Your TV wrote (30 Jul 2014 21:58:27 GMT) :
  Your suggested changes seem to have worked. (without apt-cacher-ng 
  privoxy it passed. If I back out your suggested change, it fails)
 
 Thanks for confirming!
 
 Please review'n'merge
 bugfix/7691-fix-ftbfs-with-apt-get-source-syslinux into stable and
 devel. Candidate for 1.1.1.
 
The code and APT review passes, but:

- I don't know how to reproduce the bug that this is supposed to fix. I
  thus trust Kill Your TV's test
- the branch was actually already merged in stable by 554c3c3 Merge
  remote-tracking branch 'kytv/feature/i2p-bootparam' into stable
  because that branch was based on the one I'm supposed to merge. Dear
  reviewer of kytv/feature/i2p-bootparam, please check twice what you
  merge next time!

Anyway, it's merged and I see no reason to unmerge it.

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/7688-no-dhcp-send-hostname and test/7712-hostname-leaks

[Alan]

Hi,

On Mon, 04 Aug 2014 18:01:51 +0200
intrigeri intrig...@boum.org wrote:
 bugfix/7688-no-dhcp-send-hostname fixes a regression in Tails 1.1,
 that is we're now leaking the hostname via DHCP requests.
 Details about the implemented solution can be found in commit messages
 and in the design doc, as updated by that branch.
 
Merged in stable and devel, thanks!

 test/7712-hostname-leaks validates the solution brought by the
 aforementioned: it fails on Tails 1.1, and passes on an ISO with my
 bugfix branch merged in. Should be a useful regression test for the
 future, by the way.
 
NOT merged as if I can now run the test suite, I don't feel confident
enough to review it yet.

 Both are candidate for 1.1. Please review'n'merge into stable, devel
 and experimental. Nothing to do in the APT repo.

Why should *I* merge into experimental?

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] Test suite fails on experimental

[Alan]

Hi,

When trying to run the test suite on experimental, I get the following
error. Running it on stable works with the same setup, which is the one
documented on
https://tails.boum.org/contribute/release_process/test/setup/

Any pointer?

Cheers

Virtual X framebuffer started on display :12
[info] Sikuli vision engine loaded.
/home/test/tails/features/step_definitions/usb.rb:7: syntax error,
unexpected tSTRING_BEG, expecting '}' gnome-keyrings =
/home/#{$live_user}/.gnome2/keyrings, ^
/home/test/tails/features/step_definitions/usb.rb:7: syntax error,
unexpected tASSOC, expecting keyword_end gnome-keyrings =
/home/#{$live_user}/.gnome2/keyrings, ^
/home/test/tails/features/step_definitions/usb.rb:7: syntax error,
unexpected ',', expecting
keyword_end /home/test/tails/features/step_definitions/usb.rb:8: syntax
error, unexpected tASSOC, expecting keyword_end gnupg =
/home/#{$live_user}/.gnupg,
^ /home/test/tails/features/step_definitions/usb.rb:8: syntax error,
unexpected ',', expecting
keyword_end /home/test/tails/features/step_definitions/usb.rb:9: syntax
error, unexpected tASSOC, expecting keyword_end bookmarks =
/home/#{$live_user}/.mozilla/firefox/bookmarks,
^ /home/test/tails/features/step_definitions/usb.rb:9: syntax error,
unexpected ',', expecting
keyword_end /home/test/tails/features/step_definitions/usb.rb:10:
syntax error, unexpected tASSOC, expecting keyword_end pidgin =
/home/#{$live_user}/.purple,
^ /home/test/tails/features/step_definitions/usb.rb:10: syntax error,
unexpected ',', expecting
keyword_end /home/test/tails/features/step_definitions/usb.rb:11:
syntax error, unexpected tASSOC, expecting keyword_end openssh-client
= /home/#{$live_user}/.ssh,
^ /home/test/tails/features/step_definitions/usb.rb:11: syntax error,
unexpected ',', expecting
keyword_end /home/test/tails/features/step_definitions/usb.rb:12:
syntax error, unexpected tASSOC, expecting keyword_end Persistent =
/home/#{$live_user}/Persistent,
^ /home/test/tails/features/step_definitions/usb.rb:12: syntax error,
unexpected ',', expecting
keyword_end /home/test/tails/features/step_definitions/usb.rb:13:
syntax error, unexpected tASSOC, expecting keyword_end apt/cache =
/var/cache/apt/archives,
^ /home/test/tails/features/step_definitions/usb.rb:13: syntax error,
unexpected ',', expecting
keyword_end /home/test/tails/features/step_definitions/usb.rb:14:
syntax error, unexpected tASSOC, expecting keyword_end apt/lists =
/var/lib/apt/lists,
^ /home/test/tails/features/step_definitions/usb.rb:14: syntax error,
unexpected ',', expecting
keyword_end /home/test/tails/features/step_definitions/usb.rb:42: class
definition in method
body /home/test/tails/features/step_definitions/usb.rb:501: syntax
error, unexpected $end, expecting keyword_end
(SyntaxError) 
/usr/lib/ruby/vendor_ruby/cucumber/rb_support/rb_language.rb:122:in
`load' /usr/lib/ruby/vendor_ruby/cucumber/rb_support/rb_language.rb:122:in
`load_code_file' 
/usr/lib/ruby/vendor_ruby/cucumber/runtime/support_code.rb:180:in
`load_file' /usr/lib/ruby/vendor_ruby/cucumber/runtime/support_code.rb:83:in
`block in
load_files!' /usr/lib/ruby/vendor_ruby/cucumber/runtime/support_code.rb:82:in
`each' /usr/lib/ruby/vendor_ruby/cucumber/runtime/support_code.rb:82:in
`load_files!' /usr/lib/ruby/vendor_ruby/cucumber/runtime.rb:183:in
`load_step_definitions' /usr/lib/ruby/vendor_ruby/cucumber/runtime.rb:42:in
`run!' /usr/lib/ruby/vendor_ruby/cucumber/cli/main.rb:42:in
`execute!' /usr/bin/cucumber:13:in `main'

___
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.1] feature/torbutton-1.6.11.1 (#7662, #6377)

[Alan]

Hi,

On Sun, 03 Aug 2014 19:18:51 +0200
intrigeri intrig...@boum.org wrote:
 Alan wrote (03 Aug 2014 17:00:34 GMT) :
  I started testing for the review and hit a potential issue:
 
  - there is no click-to-play barrier anymore.
http://www.youtube.com/watch?v=8LsxmQV8AXk (HTML5 test video
  Switch to Linux) Will have a NoScript click-to-play barrier, but
  should play after clicking it.
 
 Replied on the ticket (in short: same in current TBB and Tails 1.1;
 I call this a feature).
 
OK, then please update documentation now or create a ticket not to
forget it, preferably assigned to you, else to me.

Else, it's fine, thus merged, thanks!
___
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.1] bugfix/7636-printers-configuration

[Alan]

Hi,

  bugfix/7636-printers-configuration fixes #7636 by installing the
  missing cups-pk-helper package. Regression against Tails/Squeeze
  = candidate for 1.1.1. Please merge into stable and devel.
  As usual, details can be found on the ticket.
  
 Tested and reviewed OK unless the APT repository: I'm blocked by
 https://labs.riseup.net/code/issues/7733 Reprepro claim its database
 is locked and fails.
 
Merged, thanks!
___
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.1] bugfix/7618-gnome-help

[Alan]

On Sun, 03 Aug 2014 19:18:10 +0200
intrigeri intrig...@boum.org wrote:
 Alan wrote (03 Aug 2014 16:51:52 GMT) :
  Tested and reviewed OK unless the APT repository:
 
 Good.
 
Merged, thanks.

  I'm blocked by https://labs.riseup.net/code/issues/7733 Reprepro
  claim its database is locked and fails.
 
 Fixed.
 
Thanks.

___
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.1] feature/torbutton-1.6.11.1 (#7662, #6377)

[Alan]

Hi,

  1. anyone else could give this stuff a try; merged into experimental,
 so *future* autobuilt ISO from that branch should have it:
   http://nightly.tails.boum.org/build_Tails_ISO_experimental/
 I just triggered a Jenkins build, so a new ISO should be available
 in ~25 minutes there.
 
Anyone tried?

  2. Alan, bertagaz or sajolida could do the review'n'merge.
 
 Thanks in advance!
 
 No commit on the branch, only Git changes are in our torbutton repo,
 so the only merge needed is at the APT level. After merging, please
 mark the two relevant tickets (see subject) as Fix committed.
 
I started testing for the review and hit a potential issue:

- there is no click-to-play barrier anymore.
  http://www.youtube.com/watch?v=8LsxmQV8AXk (HTML5 test video Switch
  to Linux) Will have a NoScript click-to-play barrier, but should
  play after clicking it.

The actual merge is anyway blocked by
https://labs.riseup.net/code/issues/7733 Reprepro claim its database
is locked and fails.

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.1] bugfix/7636-printers-configuration

[Alan]

Hi,

On Sun, 27 Jul 2014 18:59:09 +0200
intrigeri intrig...@boum.org wrote:
 bugfix/7636-printers-configuration fixes #7636 by installing the
 missing cups-pk-helper package. Regression against Tails/Squeeze
 = candidate for 1.1.1. Please merge into stable and devel.
 As usual, details can be found on the ticket.
 
Tested and reviewed OK unless the APT repository: I'm blocked by
https://labs.riseup.net/code/issues/7733 Reprepro claim its database
is locked and fails.

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.1] bugfix/7618-gnome-help

[Alan]

Hi,

On Sun, 27 Jul 2014 18:57:19 +0200
intrigeri intrig...@boum.org wrote:
 bugfix/7618-gnome-help fixes #7618 by installing gnome-user-guide.
 That's a regression against Tails/Squeeze, so candidate for 1.1.1
 = please review'n'merge into stable and devel.
 
Tested and reviewed OK unless the APT repository: I'm blocked by
https://labs.riseup.net/code/issues/7733 Reprepro claim its database
is locked and fails.

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] Replacing TrueCrypt with cryptsetup 1.6 + documentation?

[Alan]

Hi,

  I'd rather do it faster, since we've been announcing it for a year,
  but I can live with your proposed timing too.
 
 Other thoughts, feelings, opinions?
 
I probably do it faster, but the proposed timing doesn't seem me bad 
either. As/if the people taking care of user support think it's better I
would listen to them.

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.1] feature/torbutton-1.6.11.1 (#7662, #6377)

[Alan]

Hi,

  1. anyone else could give this stuff a try; merged into experimental,
 so *future* autobuilt ISO from that branch should have it:
   http://nightly.tails.boum.org/build_Tails_ISO_experimental/
 I just triggered a Jenkins build, so a new ISO should be available
 in ~25 minutes there.
 
  2. Alan, bertagaz or sajolida could do the review'n'merge.
 
 Thanks in advance!
 
I'm taking it.
___
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.1] bugfix/7636-printers-configuration

[Alan]

 bugfix/7636-printers-configuration fixes #7636 by installing the
 missing cups-pk-helper package. Regression against Tails/Squeeze
 = candidate for 1.1.1. Please merge into stable and devel.
 As usual, details can be found on the ticket.
 
 (yeah, so much for disabling APT recommends etc..)
 
I'm taking it.

___
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.1] bugfix/7618-gnome-help

[Alan]

On Sun, 27 Jul 2014 18:57:19 +0200
intrigeri intrig...@boum.org wrote:
 bugfix/7618-gnome-help fixes #7618 by installing gnome-user-guide.
 That's a regression against Tails/Squeeze, so candidate for 1.1.1
 = please review'n'merge into stable and devel.
 
I'm taking it.

___
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.