Re: [Tails-dev] HTTPS-Everywhere missing config page!

[kytv]

On Fri, Dec 25, 2015 at 07:55:57AM +, Anonymous wrote:
> Since TAILS 1.7 the HTTPS-Everywhere addon only shows the
> Observatory settings and does not show the site list where
> the user may alter settings per site and more.
> 
> Please restore this option and if possible tell us how
> we may restore it manually in 1.8.1. TIA

I don't know what the rationale for removing it is/was but you can edit
$HOME/.tor-browser/profile.default/chrome/userChrome.css thusly to
restore the HTTPSEverywhere button:

@@ -21,7 +21,4 @@
 /* Hide the "Share this page" button in the Tool bar, which encourages
the use of social (= tracking) networks. Note that this one likely
will be removed upstream in the final Tor Browser 5.0 release. */
-#social-share-button,
-
-/* Hide HTTPS Everywhere button in the toolbar */
-#https-everywhere-button { display: none; }
+#social-share-button { display: none; }

If TorBrowser is open the changes won't be reflected until TBB is restarted.
___
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.8

[kytv]

On Mon, Nov 23, 2015 at 01:01:23PM +, anonym wrote:
> 
> Testers, please let me know:
> 
> * if you are available on 2015-12-14, late CET
> 
> * if you are available on 2015-12-15, morning to afternoon, CET.

I'll try to be around for both, but late on 2015-12-14 is most likely to
be doable, depending on how late "late" is.
___
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] Updated signing key - lack of notice on d/l page for 1.7

[kytv]

On Sat, Nov 07, 2015 at 09:23:40AM +, Anonymous wrote:
> on your TAILS download page it mentions:
> 
> "Tails transitioned to a new signing key in Tails 1.3.1."
> 
> But it fails to mention the new updated signing key for 1.7.
> I verified the 1.7 ISO with an older version of TAILS and
> followed this by importing the 1.7 signing key and it too
> verified the 1.7 ISO.
> 
> But, you should post somewhere about the new 1.7 signing key
> and recommend the download of it just in case for some
> users. TIA

I believe you are mistaken. If there was a new signing key it would definitely
have been mentioned. There isn't a new signing key for 1.7.

╰$ gpg --verify tails-i386-1.7.iso.sig tails-i386-1.7.iso
gpg: Signature made 2015-11-03T03:29:43 UTC
gpg:using RSA key 0x98FEC6BC752A3DB6  ←
gpg: Good signature from "Tails developers (offline long-term identity key) 
"
gpg: aka "Tails developers "


╰$ gpg -k 0x98FEC6BC752A3DB6
pub   4096R/0xDBB802B258ACD84F 2015-01-18 [expires: 2017-01-11]
uidTails developers (offline long-term identity 
key) 
uidTails developers 
sub   4096R/0x98FEC6BC752A3DB6 2015-01-18 [expires: 2017-01-11] ←
sub   4096R/0x3C83DCB52F699C56 2015-01-18 [expires: 2017-01-11]
sub   4096R/0xAA9E014656987A65 2015-01-18 [expires: 2016-01-11]

That is the key which was transitioned to for 1.3.1.
(https://tails.boum.org/news/signing_key_transition/index.en.html)

Or am I missing something?
___
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.7

[kytv]

On Thu, Oct 08, 2015 at 11:29:04AM +, anonym wrote:
> Testers, please let me know:
> 
> * if you are available on 2015-10-26, evening, CET.

Yes, depending on when the ISO is ready.

> * if you are available on 2015-10-27, morning to afternoon, CET.

Maybe.

> * if you are available on 2015-11-02, evening, CET.

Yes, depending on when the ISO is ready.

> * if you are available on 2015-11-03, morning to afternoon, CET.

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

[kytv]

On Thu, 27 Aug 2015 14:59:17 + (UTC)
anonym  wrote:

> Testers, please let me know:
> 
> * if you are available on 2015-09-21, and which times of that day.

In the middle of the night in Europe when most people are sleeping
might be best.

> * if you are available on 2015-09-22, morning to afternoon, CEST.

Will try.


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

Re: [Tails-dev] Automated tests specification

[kytv]

On Wed, 26 Aug 2015 13:38:40 + (UTC)
anonym  wrote:

> On 06/25/2015 11:41 AM, bertagaz wrote:
> > I've prepared a blueprint to start this discussion and take notes
> > of the decisions:
> > https://tails.boum.org/blueprint/automated_builds_and_tests/automated_tests_specs/
> >   
> 
> Looks great! For the record, I looked at the spec as of commit e70f8e7


I don't have anything to add that hasn't already been mentioned. 

+1 for the plan.


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

Re: [Tails-dev] Tor Monitor build fails

[kytv]

On Mon, 24 Aug 2015 12:59:35 + (UTC)
Alan  wrote:

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

There's no branch called `debian`.

❯ git branch -r
  origin/HEAD -> origin/master
  origin/master
  origin/pristine-tar
  origin/upstream

I suggest cloning all of the branches with 
`gbp clone https://github.com/satta/tor-monitor.git`. This command will
ensure that you get the pristine-tar branch.

The package built fine for me with sbuild and git-buildpackage.


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

Re: [Tails-dev] Creating a persistent volumn

[kytv]

On Sat, Aug 08, 2015 at 10:26:47PM -, chicc...@sigaint.org wrote:
> Problem in creating persistent volumn on usb drive
> 
> Installed and running tails on on usb drive. Now once in tails trying to
> create a persistent volumn on second usb drive. (Note the second drive had
> files which were copied to external drive and deleted from second drive)
> 
> Problem Choose Applications > Tails > Configure Persistent Volumn and then
> received Error message
> 
> Error
> Device /dev/sdb was not created using Tails Installer.
> 
> What do I do now? Thank you.

 • How was Tails installed to the USB stick? It seems it wasn't created
   with the Tails installer.
 • Follow-up to the support list
   (https://mailman.boum.org/listinfo/tails-support) and remove
   tails-dev from any future replies (user support is off-topic
   here).


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

Re: [Tails-dev] MFSA 2015-78 (aka. CVE-2015-4495) vs. Tails

[kytv]

On Fri, Aug 07, 2015 at 01:48:10PM +, Georg Koppen wrote:
> Jacob Appelbaum:
> > 
> > The current Tails Tor Browser is 4.5.3 (based on Mozilla Firefox
> > 31.8.0) - so the new alpha won't change anything and the current
> > browser shouldn't be impacted by it.
> > 
> > Did I understand that correctly?
> 
> The stable Tor Browser, which Tails is using, should not be affected,
> correct. The upcoming alpha fixes the problem for our current alpha,
> 5.0a4, which is already based on ESR 38.

Note that Tails 1.5~rc1 includes version 5.0a4-build3 of the Tor
Browser.


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

[Tails-dev] Automated test failure with automatically built feature-branch ISO; self-built works

[kytv]

On Mon,  3 Aug 2015 15:47:44 + (UTC)
intrigeri  wrote:

> Can this be reproduced, or was it a one-time error?
> Can you reproduce with an ISO built from devel on Jenkins?

No problems with tails-i386-devel-1.5-20150802T1356Z-8877514.iso

AND! today there's no problem with
tails-i386-bugfix_9748-revert-apt-amd64-1.5-20150801t1933z-ac29b77+de...@8877514.iso.

I'll try to figure out what the heck happened or what branch I was
testing from or whatever. Perhaps I was in a different branch while
running the test suite but if so, which one would work with a
self-built ISO but not a feature branch from Jenkins? 

*Sigh* :|


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

Re: [Tails-dev] Automated test failure with automatically built feature-branch ISO; self-built works

[kytv]

On Mon,  3 Aug 2015 15:47:44 + (UTC)
intrigeri  wrote:

> Hi,
> 
> kytv wrote (02 Aug 2015 20:12:11 GMT) :
> > I started a run with the test suite using
> > tails-i386-bugfix_9748-revert-apt-amd64-1.5-20150801t1933z-ac29b77+de...@8877514.iso
> > but tests which use bridges fail with something like
> > [...]
> > On the screen is "Tor Network Settings" window. Basically the
> > "Configure" button wasn't pressed.
> 
> Can this be reproduced, or was it a one-time error?

I tried 5-6 times with
tails-i386-bugfix_9748-revert-apt-amd64-1.5-20150801t1933z-ac29b77+de...@8877514.iso
and it failed consistently.

> Can you reproduce with an ISO built from devel on Jenkins?

To be determined.

> So in the end we should indeed have the same code in the Git tree used
> to build the ISO.

Yes.

> In Jenkins we merge the base branch into the topic one, not the
> opposite. No idea if it changes anything in this specific case, in
> general it should not.

I didn't think it should matter but I'll work on confirming it.

> I suspect that what you're seeing has little to do with what's in Git,
> and more to do with what's in Debian, or gzip vs. xz compression, or
> something else.

Admittedly I don't know what the problem is, only that there is a
problem somewhere.


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

[Tails-dev] Automated test failure with automatically built feature-branch ISO; self-built works

[kytv]

I started a run with the test suite using
tails-i386-bugfix_9748-revert-apt-amd64-1.5-20150801t1933z-ac29b77+de...@8877514.iso
but tests which use bridges fail with something like

And Tor is ready # 
features/step_definitions/common_steps.rb:335
  try_for() timeout expired (Timeout::Error)
  ./features/support/helpers/misc_helpers.rb:66:in `rescue in try_for'
  ./features/support/helpers/misc_helpers.rb:24:in `try_for'
  ./features/support/helpers/misc_helpers.rb:70:in 
`wait_until_tor_is_working'
  ./features/step_definitions/common_steps.rb:343:in `/^Tor has built a 
circuit$/'
  ./features/step_definitions/common_steps.rb:337:in `/^Tor is ready$/'
  features/time_syncing.feature:14:in `And Tor is ready'
Then Tails clock is less than 5 minutes incorrect# 
features/step_definitions/time_syncing.rb:42

On the screen is "Tor Network Settings" window. Basically the
"Configure" button wasn't pressed.

These same tests with my ISO with bugfix/9748-revert-apt-amd64 merged
into devel will pass. The log looks like the following:
  f5c0695 Merge remote-tracking branch 'origin/bugfix/9748-revert-apt-amd64' 
into devel
  ac29b77 Revert inclusion of syslinux:amd64 in the ISO.
  8877514 Merge branch 'stable' into devel

Note that the commits (other than the merge commit) match what jenkins
used for its ISO (ac29b77+devel@8877514)


My experience seems to differ from the intention outlined at
https://tails.boum.org/blueprint/automated_builds_and_tests/autobuild_specs/#index2h2

> A topic branch may be lagging behind the base branch it's based upon.
> What we're interested in is generally not whether a (possibly
> outdated) topic branch builds fine, but whether it would build fine
> once merged into its base branch

In this case the ISO was indeed successfully built by jenkins but
the end result was very different from what I got I merged the branches
locally and built an ISO.


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

[Tails-dev] Opensearch plugins for Mozilla-based (and other?) browsers

[kytv]

I recently told a couple of people about search plugins that I made for
mozilla based browsers (Firefox, TBB, Seamonkey, etc) and was advised
that those at tails-dev@ may be interested. They work for my needs;
perhaps someone else will also find them to have some sort of merit.

So...here they are. Attached are three search plugins:

* Tails ticket search. This is the same as a search that you'd
  perform on Tails' Redmine page with the default options
  selected
* Tails ticket search by number: It simply opens a url like
  
* Tails home page search: Uses the xapian search engine on the
  Tails homepage.

To use any of these, copy the desired search plugin to
`MOZILLA_BROWSER_PROFILE/searchplugins`. The search plugin will be
available upon the next browser start.

Default locations for `$[MOZILLA_BROWSER_PROFILE}/searchplugins`


When using the torbrowser-launcher package in Debian or Ubuntu:
`$HOME/.local/share/torbrowser/tbb/${arch}/tor-browser_en-US/Browser/TorBrowser/Data/Browser/profile.default/searchplugins`

In Iceweasel (and perhaps Firefox) in Linux:
`$HOME/.mozilla/firefox/RANDOMSTRING.default/searchplugins`

In Firefox in Windows:
`%APPDATA%\Mozilla\Firefox\Profiles\RANDOMSTRING.default\searchplugins`

In Torbrowser in Tails:
`$HOME/.tor-browser/profile.default/searchplugins`
Note: This directory does not exist by default and would need to be.
  created. These plugins will disappear after a reboot unless
  persistence is manually enabled.


tails-ticket-search.xml
Description: XML document


tails-ticket-search-by-number.xml
Description: XML document


tails-homepage.xml
Description: XML document


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

Re: [Tails-dev] Git repositories at immerda: downtime

[kytv]

On Thu,  9 Jul 2015 15:16:39 + (UTC)
intrigeri  wrote:

> It's back up.

FWIW I'm not seeing updates when pulling from the git repo over
https. For example, this shows my branch for #9709 was merged into stable:


But

$ git remote show origin |grep URL 
  Fetch URL: https://git-tails.immerda.ch/tails
  Push  URL: https://git-tails.immerda.ch/tails
$ git pull origin
Already up-to-date.
$ GIT_PAGER=cat git log --name-status origin/stable -1
commit 5776b0d6cdc9fdde80be7627fa7cad42a7c85a3e
Merge: 2878fdf 7591ae4
Author: intrigeri 
Date:   Fri Jul 3 10:38:14 2015 +

Merge remote-tracking branch 'origin/master'


It may be that I just have a misunderstanding of how the Redmine
repository works.






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

Re: [Tails-dev] monthly meeting

[kytv]

On Sat,  4 Jul 2015 09:06:24 + (UTC)
intrigeri  wrote:

> BitingBird wrote (03 Jul 2015 20:15:34 GMT) :
> > oftc was not cooperating tonight, so we didn't have the meeting.
> > Let's have it monday 6th evening, if that's ok with others ?
> 
> Works for me. I'll try to connect to OFTC at least one hour in
> advance, to maximize the chances I'm in when the meeting is supposed
> to start. And I encourage everyone else to do the same :)

I'd recommend trying *at least* an hour before, maybe even two if you
want to get on OFTC via Tor. My bouncer has been unable to reconnect for
the last 2 hours. Granted, I'm not bothering to try to get a new
identity; it'll connect when it connects.

I try to stay connected 24/7 but this hasn't been possible for few
weeks to a month. A few times I haven't been able to connect for more
than 30 hours.

Perhaps we should use indymedia as a fallback for this meeting? (You
need to use SASL to connect via their hidden service at
h7gf2ha3hefoj5ls.onion but if you don't have an account you can
register using https://irc.indymedia.nl/ via Tor). 



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

Re: [Tails-dev] [review'n'merge:1.4.1] feature/9649-tor-browser-4.5.3

[kytv]

On Sun, 28 Jun 2015 15:09:34 + (UTC)
intrigeri  wrote:

> this branch updates Tor Browser to 4.5.3 (-build2, hopefully the
> final one). It passes a great part of our test suite, details on
> the ticket.

The new TBB looks good from my vantage point. All of the corresponding
automated tests behaved as expected.


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

Re: [Tails-dev] Logjam: Tor Browser 4.5.2, and... Tails 1.4.x?

[kytv]

On Thu,  4 Jun 2015 13:55:08 + (UTC)
intrigeri  wrote:

> Has anyone here a strong opinion wrt. putting out an emergency Tails
> 1.4.x release? What are you folks motivation and availability to make
> it happen?

No strong opinion but, as always, I'd be willing and available for the
test sessions.


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

Re: [Tails-dev] Release versioning

[kytv]

On Fri, 29 May 2015 15:19:43 + (UTC)
intrigeri  wrote:

> Perhaps we should call all our expected releases a.b.c, and "bonus"
> intermediary releases a.b.c.d? In the case at hand, instead of 1.3,
> 1.3.1 and 1.3.2, this would have given 1.3.0, 1.3.0.1, and 1.3.1.

As long as Tails doesn't decide to switch to Firefox or Chrome
versioning, I'm good. :)

What you're suggesting is completely sensible.

"Which version of Tails are you seeing that in?" 
"Tails 61.0.25223978297"


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

Re: [Tails-dev] TOR browser addon Adblock Plus vs. uBlock

[kytv]

"L.R. D.S."  wrote:

> I should interpret better these 'sjw' guideline before enter here.

It's all about ethics in talking about what to ship with Tails?

> it's not on debian repo too, maybe should not
> be used on Tails...]),

Someone already pointed out that it _is_ in Debian:



As has been pointed out, things included in Tails come from Debian. Two
notable exceptions are I2P and TBB. There had been plans to remove
adblock from Tails but that plan was scrapped at hour 11½.
()

The fact is that until ublock is packaged for Debian it's rather
unlikely that it will be included in Tails for reasons already
mentioned by a previous poster.

> ps: A pf firewall or dns filtering would be more effective and
> efficient then a addon.

That all websites in Tails are accessed via Tor (via 127.0.0.1) makes
this point false.


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

Re: [Tails-dev] Release schedule for Tails 1.5

[kytv]

On Fri, 15 May 2015 13:29:21 + (UTC)
intrigeri  wrote:

>  * please let me know if you are available on 2015-08-01

Almost certainly yes if in the evening/during the night.

>  * please let anonym know if you are available on 2015-08-10 (late
>evening, CEST) and/or 2015-08-11 (whole day)

Same (nights are best)


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

Re: [Tails-dev] Release schedule for Tails 1.4.1

[kytv]

On Thu, 14 May 2015 14:28:43 + (UTC)
intrigeri  wrote:

>  * 2015-06-29, late evening, CEST.

Almost certainly yes.

>  * 2015-06-30, morning to afternoon, CEST.

*Maybe*. I may do a fair amount of testing while normal people
are sleeping, as I did for 1.4.


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

Re: [Tails-dev] [review'n'merge: 1.4] bugfix/9309-default-disconnect-search

[kytv]

On Thu,  7 May 2015 15:10:43 + (UTC)
anonym  wrote:

> I won't say much here; read the ticket, especially for the convenient
> testing instructions.

I'll test this soon.


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

Re: [Tails-dev] Release schedule for Tails 1.4

[kytv]

On Thu,  9 Apr 2015 21:11:06 + (UTC)
anonym  wrote:

> So, testers, please let me know if you are available on:
> 
> * 2015-05-03, morning to afternoon, CEST.
> 
> * 2015-05-12, morning to afternoon, CEST.

*Maybe*


> As a bonus, please let me know if you are available for testing on the
> following times *if* the respective builds went smoothly:
> 
> * 2015-05-02, late CEST.
> 
> * 2015-05-11, late CEST.

Almost certainly yes.


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

Re: [Tails-dev] [review'n'merge: 1.3.2] feature/tor-browser-4.0.6

[kytv]

On Sat, 28 Mar 2015 16:31:02 + (UTC)
bertagaz  wrote:

> Everything works fine, except that I can't connect to eepsites when
> testing i2p. It does seem to be the case with 1.3.1 too though, so
> that's not really a regression.

I've not had any problems in neither this branch, stable, nor 1.3.


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

Re: [Tails-dev] 1.2.1 broken for install/upgrade?

[kytv]

On Thu,  4 Dec 2014 16:29:14 + (UTC)
intrigeri  wrote:

> Jacob Appelbaum wrote (04 Dec 2014 15:51:07 GMT) :
> > Is anyone else experiencing this issue?
> 
> At least our automated test suite didn't see any such problem.
> FWIW, what we're testing is:
> https://git-tails.immerda.ch/tails/tree/features/usb_install.feature

FWIW,

* I didn't see any issues writing to an SD card. I booted the ISO
  in kvm and wrote to the sdcard using the USB-passthrough option in
  virt-viewer.
* I also successfully wrote to a standard Kingston USB flash drive
  from a DVD on 'bare metal'.
___
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] bugfix/tbb-via-https

[kytv]

intrigeri wrote:
> kytv wrote (21 Nov 2014 00:46:23 GMT) :
>> The build is currently broken for me when fetching TBB. The original
>> URLs are redirected to https.
> 
> I can't reproduce that: our Jenkins has been successfully building
> from the stable and devel branches 15 hours ago.
> What's happening exactly?

I tried it a few times before changing the source and it consistently
failed each time. The log snippet below is from the 3rd or 4th attempt.

Build session log:


Install the Tor Browser^M
Fetching
http://archive.torproject.org/tor-package-archive/torbrowser//4.0/tor-browser-linux32-4.0_ar.tar.xz
...^M
  % Total% Received % Xferd  Average Speed   TimeTime Time
Current^M
 Dload  Upload   Total   SpentLeft
Speed^M
^M  0 00 00 0  0  0 --:--:-- --:--:--
--:--:-- 0^M100   380  100   3800 0   1081  0 --:--:--
--:--:-- --:--:--  2638^M
SHA256 mismatch for tor-browser-linux32-4.0_ar.tar.xz^M
E: config/chroot_local-hooks/10-tbb failed (exit non-zero). You should
check for errors.^M
P: Begin unmounting filesystems...^M
^M
real6m5.990s^M
user3m50.920s^M
sys 0m55.940s^M
lb build failed (1).^M
root@tailsbuilder:/build# find . -name tor-browser-linux32-4.0_ar.tar.xz ^M
./chroot/tmp/tmp.7e0yW4OCCe/tor-browser-linux32-4.0_ar.tar.xz^M
root@tailsbuilder:/build# cd chroot/tmp/tmp.7e0yW4OCCe/^M
root@tailsbuilder:/build/chroot/tmp/tmp.7e0yW4OCCe# ls^M
tor-browser-linux32-4.0_ar.tar.xz^M
root@tailsbuilder:/build/chroot/tmp/tmp.7e0yW4OCCe# ls -lh^M
total 4.0K^M
-rw-r--r-- 1 root root 380 Nov 21 00:01 tor-browser-linux32-4.0_ar.tar.xz^M
root@tailsbuilder:/build/chroot/tmp/tmp.7e0yW4OCCe# cat
tor-browser-linux32-4.0_ar.tar.xz ^M
^M
^M
301 Moved Permanently^M
^M
Moved Permanently^M
The document has moved https://archive.torproject.org/tor-package-archive/torbrowser//4.0/tor-browser-linux32-4.0_ar.tar.xz";>here.^M
^M
Apache Server at archive.torproject.org Port 80^M



>> This completely trivial change fixes the build by eliminating the
>> need for the redirect.
> 
> Apparently, using https:// URLs breaks things with apt-cacher-ng.
> Are you using apt-cacher-ng or another HTTP proxy? If yes, which
> version?

s/trivial/useless/

I'm using apt-cacher-ng, 0.8.0-1 but the time of my change I disabled
acng to rule it out as being the culprit for the failures (this was a
completely new build environment). When I made my change it was used
without re-enabling acng.

I re-enabled acng and *now* the build works without this change and
without any other changes to my environment. Was someone at t.p.o
perhaps tinkering with the server config at the same time I was trying
to build?

>> git://repo.or.cz/tails/kytv.gitbugfix/tbb-via-https
> 
> Please base bugfix branches on top of stable.

Oops. Obvious and stupid mistake there. Sorry.





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

[Tails-dev] [review'n'merge] bugfix/tbb-via-https

[kytv]

The build is currently broken for me when fetching TBB. The original
URLs are redirected to https. This completely trivial change fixes the
build by eliminating the need for the redirect.

git://repo.or.cz/tails/kytv.gitbugfix/tbb-via-https



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

Re: [Tails-dev] certificate error for immerda.ch

[kytv]

intrigeri wrote:
> kytv wrote (20 Nov 2014 12:43:07 GMT) :
>> Are there official--and publicly accessible--mirrors of
>> the repository?
> 
> Do you mean, a HTTPS one with a "valid" certificate? Then I don't
> think so.

I just meant any "trusted" place the code can be pulled from as a
fallback when the primary is down, e.g. perhaps there's a .onion mirror.

> Possible alternatives:
> 
>   * git:// access to git.tails.b.o and/or git-tails.immerda.ch,
> if that's still available.

git://git-tails.immerda.ch does not work (I tried this before sending
the email). One gets

  fatal: Could not read from remote repository.

  Please make sure you have the correct access rights



git://git.tails.b.o works (I didn't know about this location).



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

Re: [Tails-dev] certificate error for immerda.ch

[kytv]

Kill Your TV wrote:
> This may already be known by those that can fix it, but I'm getting an
> error when accessing git-tails.immerda.ch.

Are there official--and publicly accessible--mirrors of the repository?



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