[Tails-dev] Can help me?

2016-05-17 Thread 东湖海
hello dear friend!


I am in china tor and tor Bridge can not use,ordinary proxy  can not use too,I 
want use shadowsocks as tor proxy,but tails can not direct networking,I don‘t 
know how can I do?




 thanks!


 china tails amateur___
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] [Reproducible-builds] tails binary and source packages lists URL has changed…

2016-05-17 Thread intrigeri
Hi Holger,

Holger Levsen wrote (17 May 2016 11:29:56 GMT) :
> On Tue, May 17, 2016 at 01:16:28PM +0200, intrigeri wrote:
>> I'm working on it and hope to fix it today.

Repaired!

> I'll gladly merge this whenever you tell me I should.

Please go ahead :)

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] https://labs.riseup.net/ is unreachable (certificate error)

2016-05-17 Thread sajolida
Austin English:
> On 05/17/2016 01:40 AM, Austin English wrote:
>> In both Iceweasel and Chromium, I get a certificate error. Another
>> user on #tails-dev has the same issue.
>>
>> I'm not sure where to report this, could someone do so / tell me where t
>> o?
> 
> Either a very fast response, or great coincidence, working now. Also
> confirmed on #tails-dev.

They have a Let's Encrypt certificate from 2016-04-04. Maybe they are
still playing around with their configuration...
___
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] [Reproducible-builds] tails binary and source packages lists URL has changed…

2016-05-17 Thread Holger Levsen
Hi intrigeri,

On Tue, May 17, 2016 at 01:16:28PM +0200, intrigeri wrote:
> The ISO build from our feature/stretch branch, that generates these
> files, has been broken for a while, and after some weeks our Jenkins
> set up deletes artifacts it considers to be obsolete… so these files
> have indeed disappeared. Sorry for the inconvenience, and thanks for
> the heads up: I didn't consciously realize that such breakage would
> impact you folks :/
> 
> I'm working on it and hope to fix it today.

ah, cool! (and don't worry, this didnt cause much inconvenience, just
some warning emails (and the tails pkg set didnt get updated)…)
 
> > https://tests.reproducible-builds.org/unstable/amd64/pkg_set_tails.html
> > https://tests.reproducible-builds.org/unstable/amd64/pkg_set_tails_build-depends.html
> Right, it's lovely that we have these, thank you! :)

:) thanks for these kind words!

> And by the way, once the above is fixed, I want to quickly switch our
> pkgset generation process from our (very hackish and inaccurate)
> .binpkgs/.srcpkgs files, to our new (accurate) .build-manifest one.
> 
> I've prepared a branch that does this switch and adjusts
> bin/reproducible_create_meta_pkg_sets.sh accordingly:

great, thanks!

>  * I used explicit argument passing to the function this branch
>introduces, instead of global variables; if you prefer, I can of
>course adjust this to use global variables, to match the current
>code's style more closely, regardless of whatever my personal taste
>in such matters is.

Actually I prefer your coding style over the one I used… I'd probably made
the tmpfile and packages variables local variables though.

>  * I really didn't want to parse YAML by hand, hence the inline Python
>script. I've seen a Perl one in the same file already, so I've
>assumed it would be OK. If you prefer I can certainly move that
>function into its own, dedicated script.

hehe, I actually like those 10 lines in-line, they serve as a nice
example.

I'll gladly merge this whenever you tell me I should. Thanks again!


-- 
cheers,
Holger


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] tails binary and source packages lists URL has changed…

2016-05-17 Thread intrigeri
Hi,

Holger Levsen wrote (11 May 2016 10:22:11 GMT) :
> once again these two URLs have changed:

> http://nightly.tails.boum.org/build_Tails_ISO_feature-stretch/lastSuccessful/archive/latest.iso.binpkgs
> http://nightly.tails.boum.org/build_Tails_ISO_feature-stretch/lastSuccessful/archive/latest.iso.srcpkg

The ISO build from our feature/stretch branch, that generates these
files, has been broken for a while, and after some weeks our Jenkins
set up deletes artifacts it considers to be obsolete… so these files
have indeed disappeared. Sorry for the inconvenience, and thanks for
the heads up: I didn't consciously realize that such breakage would
impact you folks :/

I'm working on it and hope to fix it today.

> We need to them to create the package lists for:

> https://tests.reproducible-builds.org/unstable/amd64/pkg_set_tails.html
> https://tests.reproducible-builds.org/unstable/amd64/pkg_set_tails_build-depends.html

Right, it's lovely that we have these, thank you! :)

And by the way, once the above is fixed, I want to quickly switch our
pkgset generation process from our (very hackish and inaccurate)
.binpkgs/.srcpkgs files, to our new (accurate) .build-manifest one.

I've prepared a branch that does this switch and adjusts
bin/reproducible_create_meta_pkg_sets.sh accordingly:

 * repo: https://git-tails.immerda.ch/jenkins.debian.net.git
 * branch: support-tails-build-manifest

I'll notify you once the above has been fixed and this can be merged
and deployed to production, but IMO this branch is ready for a code
review. Note that:

 * I used explicit argument passing to the function this branch
   introduces, instead of global variables; if you prefer, I can of
   course adjust this to use global variables, to match the current
   code's style more closely, regardless of whatever my personal taste
   in such matters is.

 * I really didn't want to parse YAML by hand, hence the inline Python
   script. I've seen a Perl one in the same file already, so I've
   assumed it would be OK. If you prefer I can certainly move that
   function into its own, dedicated script.

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.

[Tails-dev] Buggy Let's Encrypt setup on labs.riseup.net?

2016-05-17 Thread intrigeri
Hi Micah & Matt,

today we see https://labs.riseup.net/ sometimes use an expired
certificate, and sometimes a valid one. We believed it was fixed at
some point, but the problem just reappeared. Perhaps something is
buggy in the Let's Encrypt setup on that box?

(It seems that the corresponding Puppet bits are not in the manifests
repo I have access to, so I guess there's nothing that I can
personally and cleanly do about it. Still, while I was at it I've
manually deleted the renew_letsencrypt_bugs_otr cronjob, since it has
been removed from Puppet but not cleaned up on the system.)

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.

[Tails-dev] https://labs.riseup.net/ is unreachable (certificate error)

2016-05-17 Thread Austin English
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

In both Iceweasel and Chromium, I get a certificate error. Another
user on #tails-dev has the same issue.

I'm not sure where to report this, could someone do so / tell me where t
o?

- -- 
- -Austin
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXOrzKAAoJEBT71+qgQZN7fEQQALwuoy1A0pcVeD08ApVM2Ee4
PaccOeFDUZFe6mNnWZ7CvpFDH3/DLVvvqpv0IN0qLmg6fYe0XZZIVjIBbD7Ao7ly
L4kw8Rjo4SIjlN7MA6m0oi6nCswZFpZpkC6BXMzK0aeEt+Q2iFfWEgUr4801ICwr
CHh03FzillRvm1UUx7j9uq0wlyknyoQfoyv7KhFAAyQE4lsbNIMOMEENYO8cAeH0
/FKeeHTjdMuRoOpfuOtlZpSsR8qQPhAS4VC9VMiJkUbyv4wapWJedIYLJyceItzO
1gStixX9UO7PdqGSwUHvOk4YNuQpfUDzRMyJLEKtiCVf1nExl64nrmD2QKmDhd2Q
0XWfW9/j9CTBF1fSFMEaD/p51ZzLZrvreZdv/eEMlCsDD5gyCR/yriEozsZqJK1Z
5FOkvkkxzkqPN1ndm11zF93hfRiKg0YB4dl7L0mWvSWVqH9KVwd1OdNzPHZ+krN6
vgFgotYHi1dnIJ69q43NArsj3PPJ5Bp7Q3x0s/aTx11ftIOpWiX0GhZ1r1xuF8wB
cmKoKdsVDMfSk/Pf6Mkwd8ErdZY4a+qbEZcN1ctkMMcPnD9VUoUW6YlFU3pC3fyY
kM4r8B9LTmMV2+n5AH86Aezg91XAYTy6utKZYC8btbfvqe1qsKze+/S1Wq9758VR
N0qb/5H9hesqR+Y60WgW
=Vs7X
-END PGP SIGNATURE-
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.