[Tails-dev] Server-side caching settings of IDF [Was: Dynamically changing ISO URL in DAVE]

[intrigeri]

Giorgio Maone wrote (13 Feb 2016 13:23:00 GMT) :
> Whenever a page matching the pattern for a possible UI page (i.e.
> "https://tails.boum.org/*;), DAVE currently fetches the IDF. This is
> basically the only way to fix https://labs.riseup.net/code/issues/10685,
> as noted in https://labs.riseup.net/code/issues/10685#note-5

> Of course you can and should limit the actual network activity by
> properly using Chache-Control and/or ETag headers.

By the way, did you IA+DAVE folks already check if the server-side
Cache-Control / ETag settings are OK for the IDF?  (I vaguely remember
sajolida noticing weird stats in the access logs, that might be caused
by suboptimal HTTP server settings.)

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] Dynamically changing ISO URL in DAVE

[intrigeri]

Hi,

[sorry for the delay...]

Giorgio Maone wrote (13 Feb 2016 13:23:00 GMT) :
> On 13/02/2016 13:49, sajolida wrote:
>> intrigeri:
 Beside that, I think the JSON should be fetched every time the UI page
 is reloaded (of course obeying to server-side caching directives), just
 like we currently do with the IDF.
>>> I'm afraid I don't know under which circumstances the UI page is
>>> reloaded, so I lack the background info to integrate this proposal
>>> into my mental representation of the problem.
>>>
>>> @sajolida + @Giorgio: is this done as part of the Installation
>>> Assistant or DAVE course of operation, or only due to external factors
>>> (e.g. the user manually reloading the page, or restarting their
>>> browser)?
>> I *think* that Giorgio is only referring to a possible manual refresh
>> from the user. Keep in mind that DAVE is supposed to follow up on
>> download in the background and a user coming back to the download page
>> after possibly closing the tab, or to survive a manual page refresh or
>> browser restart.
>>
> Whenever a page matching the pattern for a possible UI page (i.e.
> "https://tails.boum.org/*;), DAVE currently fetches the IDF. This is
> basically the only way to fix https://labs.riseup.net/code/issues/10685,
> as noted in https://labs.riseup.net/code/issues/10685#note-5

> Of course you can and should limit the actual network activity by
> properly using Chache-Control and/or ETag headers.

> The same should apply to mirrors, if you want to keep them
> up-to-date.

Thanks for clarifying! It totally makes sense to me, and I've updated
#11109 accordingly.

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] Fallback download URL outside of DAVE [Was: Dynamically changing ISO URL in DAVE]

[intrigeri]

Hi,

sajolida wrote (14 Feb 2016 15:01:17 GMT) :
> intrigeri:
>> sajolida wrote (13 Feb 2016 12:49:46 GMT) :
>>>  B. People with no JavaScript, wget, etc. It seems like we need the
>>> minimal DNS pool if we want to support these anyway.
>> 
>> Sure, we will need this pool anyway.
>> 
>> But the less we rely on that DNS pool, the better: the less load we
>> put on it (i.e. the less users we send to it), the more reliable it
>> is, and the less daily maintenance effort is required. This is
>> especially true until we have recruited very fast and reliable mirrors
>> to put into this pool.
>> 
>> Now, indeed it may be more worth our time to go after such new
>> mirrors, than writing code to workaround the lack thereof :)

> :) What would this be?

> A. Do stats on faster mirror as reported by check-mirrors.

Yes, we can do that for our current set of mirrors.

> B. Do stats on mirrors with less incidents in the mirrors Git repo.

Yes.

> or you are thinking about recruiting new mirrors we don't yet have in
> the pool?

Also this, yes. (This is why I've started the discussion about dropping
the requirement for OpenPGP communication with mirror operators.)

> To do this I can dig check-mirrors reports from my trash (1069!) and
> compile some stats over the last two years.

I don't think it's worth the effort to go back in the past: IMO for
(A) we can just check the _current_ state of our mirrors. But if
you're excited by this idea and wants to put extra effort into it,
well, the better :)

> I guess that, as time goes by, we will still be able to silently modify
> the DNS pool for example to add fast and reliable mirrors from the JS
> pool or to remove flaky ones. But we should be able to do this very
> rarely compare to the maintenance work we do nowadays.

That's what I hope too.

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] Detecting hidden partitions?

[Spencer]

Hi,



intrigeri:
Tails system partition is enough



Will you explain a bit more about this?



intrigeri:
whose type is "Hidden W95 FAT32"



It seems that any format type is optional.



is it any broader?



It could check the MBR partition table for any occupied bits.

But the specific thought was to check for extended partition entries.

[Tangential Thought]:

We could also check and flip the RMB bit for supporting UFD controllers, 
making the USB stick usable for Tails - Ignore this (:


Wordlife,
Spencer



___
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] Update: Porting tails bash scripts to python

[GoodCrypto Support]

> publish it as a Git branch, forked off our current devel branch

Happy to. It may be a few days.

Doug


GoodCrypto Warning: Anyone could have read this message. Use encryption, it 
works.
___
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] Detecting hidden partitions?

[intrigeri]

Hi,

Austin English wrote (24 Mar 2016 22:33:18 GMT) :
> On Sat, Mar 12, 2016 at 4:45 PM, intrigeri  wrote:
>> IMO for #11137, checking the content of the Tails system partition
>> is enough, so no need to check for "hidden" partitions. But if you
>> want to:
>>
>>> I used a hidden FAT32 partition for testing:
>>> 1g.img2 206848  227327   20480   10M 1b Hidden W95 FAT32
>>
>>> my other thought was checking the Partition ID, unless someone knows a
>>> better way.
>>
>> OK.
>>
>> Is this about detecting partitions whose type is "Hidden W95 FAT32"?
>>
>> Or is it any broader?

> It was not my original idea, it was originally proposed here:
> https://mailman.boum.org/pipermail/tails-dev/2016-February/010303.html

> Though I'm considering dropping that portion of the idea because there
> is a lot of confusion about it. I'm not sure what exactly is
> desired/requested,

Fully understood. I'm not sure either. Unless Spencer clarifies the
idea, someone else (you?) needs to research the topic and propose
something that translates "hidden partitions" into something that can
be implemented.

> or how to find the information needed to detect
> these partitions properly

FTR I'm happy to help with that, if we keep this idea, once it is
clearer what exactly we are trying to detect.

> and being put in a position to defend those
> decisions is not a place I like being.

My intention was not to attack what you were trying to do, but to try
and understand it, so I could help answer the specific technical
questions you were asking. Apparently I failed at that, and instead
I've contributed to create bad feelings. I'm sorry about that :/

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] Update: Porting tails bash scripts to python

[intrigeri]

Hi,

GoodCrypto Support wrote (25 Mar 2016 01:13:59 GMT) :
> Early .py versions of the following scripts are available at
> https://goodcrypto.com/special-downloads/bash2py-2016-03-24.tgz:

Thanks!

GoodCrypto Support: it will be immensely easier to review your work
(and especially the 2nd and further iterations) if you publish it as
a Git branch, forked off our current devel branch. Is it an option
for you?

anonym: can/will you take care of reviewing the proposed code?

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.