[Tails-dev] Electrum doc wrt. avoiding the negative effects of DoS [was: Re: Article: Bitcoin over Tor isn't a good idea]

[Minoru]

sajolida,

I agree with your changes so far. The reason for the specific
explanation is that Electrum over Tor is extremely vulnerable to
attack. If you read the article  http://arxiv.org/pdf/1410.6079v2.pdf
it only takes 2500 USD and publicly available information to have
complete control over which Bitcoin blocks and transactions users are
aware of. Would you still be interested in the additional documentation
that I proposed? I wanted to add three subsections to the Electrum
documentation focused on Tor DoS on SPV:
1. Explain block confirmations (temporary fix for Electrum displaying
money that you actually do not have)
2. Explain watching-only wallets (temporary fix for Electrum not
displaying money that you actually do have)
3. Explain a possible long term solution to this problem by using
trusted Electrum servers accessed by a Tor hidden service (I might
remove this point because I'm not sure if it is currently possible
execute this solution since not many .onion Electrum servers exist and
it is difficult to trust centralized services)
I understand that you want to keep the documentation short and easy to
understand, but Electrum over Tor using SPV has a serious vulnerability
that needs a little more documentation to help users avoid the negative
effects of DoS.

Cheers,
Minoru
___
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] Jenkins build is back to normal : build_Tails_ISO_devel #889

[tails-sysadmins]

See 

___
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] Jenkins build is back to normal : build_Tails_ISO_experimental #2065

[anonym]

On 23/02/15 16:58, tails-sysadm...@boum.org wrote:
> See 

I think what happened was that I uploaded the new I2P packages after
they had been installed, and then they were upgraded by some very late
`apt-get update && apt-get dist-upgrade` after the mksquashfs stage.
Same for build_Tails_ISO_devel #888 that failed in the same way.

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] Jenkins build is back to normal : build_Tails_ISO_experimental #2065

[tails-sysadmins]

See 

___
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] Build failed in Jenkins: build_Tails_ISO_devel #888

[tails-sysadmins]

See 

--
[...truncated 13508 lines...]
path relative to the source directories
Cannot stat sortlist entry "usr/lib/python2.7/atexit.pyc"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry "usr/lib/python2.7/tempfile.pyc"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry "usr/lib/python2.7/subprocess.pyc"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry "usr/lib/python2.7/pickle.pyc"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry "usr/local/lib/tails-shell-library/tails_greeter.sh"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry 
"etc/xdg/autostart/add-bookmark-for-persistent-directory.desktop"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry 
"usr/local/bin/tails-add-bookmark-for-persistent-directory"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry "usr/lib/python2.7/fnmatch.pyc"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry "usr/lib/python2.7/glob.pyc"
This is probably because you're using the wrong file
path relative to the source directories
Parallel mksquashfs: Using 8 processors
Creating 4.0 filesystem on filesystem.squashfs, block size 1048576.

Exportable Squashfs 4.0 filesystem, xz compressed, data block size 1048576
compressed data, compressed metadata, compressed fragments, compressed 
xattrs
duplicates are removed
Filesystem size 895128.46 Kbytes (874.15 Mbytes)
28.38% of uncompressed filesystem size (3154590.06 Kbytes)
Inode table size 1109386 bytes (1083.38 Kbytes)
21.95% of uncompressed inode table size (5053149 bytes)
Directory table size 1305390 bytes (1274.79 Kbytes)
35.51% of uncompressed directory table size (3675959 bytes)
Number of duplicate files found 4712
Number of inodes 141902
Number of files 107926
Number of fragments 1940
Number of symbolic links  22169
Number of device nodes 38
Number of fifo nodes 1
Number of socket nodes 0
Number of directories 11768
Number of ids (unique uids + gids) 32
Number of uids 13
root (0)
unknown (105)
unknown (112)
unknown (122)
unknown (111)
man (6)
unknown (107)
unknown (106)
unknown (114)
unknown (121)
unknown (117)
unknown (113)
libuuid (100)
Number of gids 26
root (0)
utmp (43)
adm (4)
unknown (109)
unknown (105)
unknown (112)
unknown (129)
unknown (118)
disk (6)
dip (30)
tty (5)
mail (8)
unknown (107)
shadow (42)
crontab (102)
unknown (108)
unknown (106)
kmem (15)
unknown (121)
unknown (124)
unknown (128)
audio (29)
staff (50)
unknown (119)
unknown (120)
libuuid (101)
P: Deconfiguring file /etc/kernel-img.conf
P: Deconfiguring file /etc/apt/sources.list
P: Deconfiguring file /etc/apt/apt.conf
P: Deconfiguring file /etc/hostname
P: Deconfiguring file /bin/hostname
P: Deconfiguring file /etc/resolv.conf
P: Deconfiguring file /etc/hosts
P: Deconfiguring file /usr/sbin/policy-rc.d
P: Deconfiguring file /usr/sbin/initctl
P: Deconfiguring file /sbin/start-stop-daemon
P: Deconfiguring file /etc/debian_chroot
P: Begin unmounting /sys...
P: Begin unmounting /selinux...
P: Begin unmounting /proc...
P: Begin unmounting /dev/pts...
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 file /etc/resolv.conf
P: Configuring file /etc/hostname
P: Configuring file /bin/hostname
P: Configuring file /etc/apt/apt.conf
P: Configuring file /etc/apt/sources.list
OK
OK
Get:1 http://deb.tails.boum.org devel Release.gpg [836 B]
Get:2 http://deb.tails.boum.org devel Release [5840 B]
Get:3 http://deb.tails.boum.org devel/main i386 Packages [19.2 kB]
Hit http://ftp.us.debian.org wheezy Release.gpg
Hit http://deb.torproject.org obfs4proxy Release.gpg
Hit http://ftp.us.debian.org experimental Release.gpg
Hit http://ftp.us.debian.org unstable Release.gpg
Hit http://deb.torproject.org wheezy Release.gpg
Ign http://deb.tails.boum.org devel/main Translation-en
Hit http://ftp.us.debian.org testing Release.gpg
Hit http://security.debian.or

[Tails-dev] Build failed in Jenkins: build_Tails_ISO_experimental #2064

[tails-sysadmins]

See 

--
[...truncated 13630 lines...]
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry "usr/share/xul-ext/adblock-plus/lib/ui.js"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry "usr/share/xul-ext/adblock-plus/lib/keySelector.js"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry 
"usr/share/xul-ext/adblock-plus/chrome/content/ui/overlay.xul"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry "usr/share/xul-ext/adblock-plus/lib/appSupport.js"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry 
"usr/share/xul-ext/adblock-plus/chrome/locale/en-US/overlay.dtd"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry 
"usr/share/xul-ext/adblock-plus/chrome/locale/en-US/subscriptionSelection.dtd"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry 
"usr/share/xul-ext/adblock-plus/lib/windowObserver.js"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry 
"usr/share/xul-ext/adblock-plus/chrome/skin/overlay.css"
This is probably because you're using the wrong file
path relative to the source directories
Cannot stat sortlist entry 
"usr/share/xul-ext/adblock-plus/chrome/skin/abp-status-16.png"
This is probably because you're using the wrong file
path relative to the source directories
Parallel mksquashfs: Using 8 processors
Creating 4.0 filesystem on filesystem.squashfs, block size 1048576.

Exportable Squashfs 4.0 filesystem, xz compressed, data block size 1048576
compressed data, compressed metadata, compressed fragments, compressed 
xattrs
duplicates are removed
Filesystem size 891851.43 Kbytes (870.95 Mbytes)
28.45% of uncompressed filesystem size (3135193.45 Kbytes)
Inode table size 1104966 bytes (1079.07 Kbytes)
21.96% of uncompressed inode table size (5032764 bytes)
Directory table size 1303610 bytes (1273.06 Kbytes)
35.61% of uncompressed directory table size (3660697 bytes)
Number of duplicate files found 4676
Number of inodes 141230
Number of files 107314
Number of fragments 1932
Number of symbolic links  22183
Number of device nodes 38
Number of fifo nodes 1
Number of socket nodes 0
Number of directories 11694
Number of ids (unique uids + gids) 32
Number of uids 13
root (0)
unknown (105)
unknown (112)
unknown (122)
unknown (111)
man (6)
unknown (107)
unknown (106)
unknown (114)
unknown (121)
unknown (117)
unknown (113)
libuuid (100)
Number of gids 26
root (0)
utmp (43)
adm (4)
unknown (109)
unknown (105)
unknown (112)
unknown (129)
unknown (118)
disk (6)
dip (30)
tty (5)
mail (8)
unknown (107)
shadow (42)
crontab (102)
unknown (108)
unknown (106)
kmem (15)
unknown (121)
unknown (124)
unknown (128)
audio (29)
staff (50)
unknown (119)
unknown (120)
libuuid (101)
P: Deconfiguring file /etc/kernel-img.conf
P: Deconfiguring file /etc/apt/sources.list
P: Deconfiguring file /etc/apt/apt.conf
P: Deconfiguring file /etc/hostname
P: Deconfiguring file /bin/hostname
P: Deconfiguring file /etc/resolv.conf
P: Deconfiguring file /etc/hosts
P: Deconfiguring file /usr/sbin/policy-rc.d
P: Deconfiguring file /usr/sbin/initctl
P: Deconfiguring file /sbin/start-stop-daemon
P: Deconfiguring file /etc/debian_chroot
P: Begin unmounting /sys...
P: Begin unmounting /selinux...
P: Begin unmounting /proc...
P: Begin unmounting /dev/pts...
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 file /etc/resolv.conf
P: Configuring file /etc/hostname
P: Configuring file /bin/hostname
P: Configuring file /etc/apt/apt.conf
P: Configuring file /etc/apt/sources.list
OK
OK
Get:1 http://deb.tails.boum.org experimental Release.gpg [836 B]
Get:2 http://deb.tails.boum.org experimental Release [5861 B]
Get:3 http://deb.tails.boum.org experimental/main i386 Packages [19.2 kB]
Hit http://ftp.us.debian.org wheezy Release.gpg
Hit http://security.debian.org wheezy/updates Release.gpg
Hit http://deb.torproject.org obfs4pro

Re: [Tails-dev] Git branches to delete: review needed

[bertagaz]

Hi,

On Sat, Feb 21, 2015 at 05:24:51PM +0100, intrigeri wrote:
> Hi,
> 
> Please have a look and shout if there's something in there that we
> should keep.

Can't find something that doesn't seem in its place for what I can tell.

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

Done.

Awesome to see you tackle this.

bert.
___
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] Important tickets with milestone, but without assignee

[intrigeri]

Hi,

(stealing a bit of the RM's job, oh well.)

It happens that we flag important problems and regressions with some
upcoming target version, so that they stay on our radar. I think it's
fine in itself. However, given most of us are struggling to deal with
tickets assigned to them in time for freezes and releases, I'm pretty
sure that these tickets (that have a target version but no assignee)
see very little collective attention. And in the end, we often
silently postpone these tickets from a target version to the next one,
and then to the next one, etc.

E.g. we're going to postpone (again) these tickets that were not
resolved during the 1.3 cycle:

 * https://labs.riseup.net/code/issues/8720 ("Filesystems on external
   USB drives are sometimes automatically mounted")

 * https://labs.riseup.net/code/issues/8686 ("Desktop notifications are
   not always displayed"): postponed since 1.2.3

 * https://labs.riseup.net/code/issues/7912 ("Non-US keyboard layout
   selected with Greeter sometimes is not active when logged in"):
   postponed since 1.2.1

 * https://labs.riseup.net/code/issues/8433 ("Activate storeconfig on
   lizard's puppet master"): on our radar since two months

And we already have one such ticket for 1.3.1:

 * https://labs.riseup.net/code/issues/8524 ("Do statistics on whether
   bug reports come from a DVD or flash media")

And seven such tickets for 1.4:
https://labs.riseup.net/code/projects/tails/issues?utf8=%E2%9C%93&set_filter=1&f[]=fixed_version_id&op[fixed_version_id]=%3D&v[fixed_version_id][]=235&f[]=status_id&op[status_id]=o&f[]=assigned_to_id&op[assigned_to_id]=!*&f[]=&c[]=priority&c[]=subject&c[]=category&c[]=cf_15&c[]=assigned_to&c[]=cf_9&group_by=status

I'm not sure what we should do about it. We discussed that with anonym
a few days ago, and he agreed the RM should send heads up messages or
something about it, as part of their duty. Hopefully this will help us
keep in mind all these small things that need to be done, and formally
are on nobody's plate :)

Other ideas wrt. what we could do about it?

Cheers,
-- 
intrigeri
___
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 history rewrite

[bertagaz]

Hi,

On Sat, Feb 21, 2015 at 12:08:44PM +0100, Jurre van Bergen wrote:
> Hi folks,
> 
> I want to make you all aware that we will be rewriting the git history
> of tails.git, our main git repository. To make it easy for everybody and
> have less pain for us or for yourself in the future. I would like to ask
> you to push any local branches you might have laying around, even if the
> work isn't finished, to the git repo.
> 
> Please do not postpone! :-)

I'm good on this, please do not wait for me, and keep on the good work
you're doing!

bert.
___
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] Rewriting the Git repository

[sajolida]

intrigeri:
> sajolida wrote (22 Feb 2015 20:12:23 GMT) :
>> What if we need to publish an important workaround for a bug in 1.3?
> 
> On the website? As an emergency point-release? Anything else?

I meant on the website. Imagine the Tor Browser confinement breaks
something pretty badly for people using avian carriers and we need to
publish instructions to fix that.

An emergency point release would trigger something much bigger and we
might consider the whole plan maybe. But that won't happen.

> Anyway, good question, and probably it doesn't change much my answer
> below:
> 
>> Would "you" (the people locking the repo) be still able to do some
>> emergency commits to it?
> 
> I believe that something could be done, yes.

Cool.

___
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] Blueprint: delete obsolete Git branches (review)

[sajolida]

Jurre van Bergen:
> On 02/22/2015 05:47 PM, intrigeri wrote:
>> Looks good. Pushed a few minor rephrasing and formatting improvements.
> 
> Cheers!
> 
>> There's one confusing point, though: somewhere it is said that merged
>> branches can be deleted "After a new Tails release has been shipped",
>> while elsewhere I see "it can be done post-merge". This should be
>> clarified.
> 
> I have done so.
> 
>> I personally prefer if it's done after each release, and not after
>> each merge: we're in no hurry, and IMO it is not worth adding more
>> steps to the review'n'merge process.
> Ack!

I'm fine with that blueprint.

___
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/tor-browser-4.0.4 (#8938)

[intrigeri]

anonym wrote (22 Feb 2015 17:55:29 GMT) :
> Please review'n'merge into testing and devel.

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

[sajolida]

intrigeri:
> sajolida wrote (22 Feb 2015 17:14:20 GMT) :
>> intrigeri:
>>> Please have a look and shout if there's something in there that we
>>> should keep.
> 
>> All of mine can be deleted. Sorry for the mess.
> 
> Just to confirm, since what you're quoting is another, different
> question -- were you replying to that question of mine:
> 
> "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."
> 
> ?
> 
> If so, then I've just done it myself (04ec81a).

Ack, sorry for going to fast on this myself.

___
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] minor typo fix

[sajolida]

Kill Your TV:
> A minor typo fix (s/any way/anyway/)
> 
> http://repo.or.cz/tails/kytv.gitfeature/6739-electrum-typo-fix

Merge into feature/6739-install-electrum which is still pending for
review and merge.

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

Re: [Tails-dev] patch for anchor: access internal hard disk

[intrigeri]

BitingBird wrote (23 Feb 2015 03:20:52 GMT) :
> Subject: [PATCH 2/2] anchor for accessing internal hard disk

applied, 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.