[DONE]Remove flash from the Live ISO

hhh · 2016-01-22 03:01:43

I just realized that this decision was done more-or-less behind closed doors... there was a thread recommending moving flash to bl-welcome due to the constant security issues and we've done that, but how do people feel about not having it when using the BL ISO in Live mode? More secure? 8o

johnraff · 2016-01-22 03:34:01

hhh wrote:

there was a thread recommending moving flash to bl-welcome due to the constant security issues and we've done that

Doesn't moving flash to bl-welcome immediately imply removing it from the iso?

hhh · 2016-01-22 03:38:55

Yes, I guess this post is half announcement/half last-minute user-feedback request. Is that OK?

johnraff · 2016-01-22 04:28:33

...sure

I was just wondering if the decision might get reversed again, after rewriting bl-welcome...

hhh · 2016-01-22 04:48:38

Not unless there's a lot of noise in this thread all of a sudden, I'd say no. The opinions at the time were decidedly one-sided against flash as I recall.

-edit- You can always install flash from Adobe or Debian during the Live session, anyway.

KrunchTime · 2016-02-06 05:34:01

The only issue I could see is if someone needed to logon to a site that requires flash.

dolly · 2016-02-06 06:33:43

hhh wrote:

You can always install flash from Adobe or Debian during the Live session, anyway.

Solved

hhh · 2016-02-06 07:00:17

dolly wrote:

Solved

Solved and done.

ohnonot · 2016-02-06 12:57:03

johnraff wrote:

Doesn't moving flash to bl-welcome immediately imply removing it from the iso?

will the new bl-welcome also include a choice between adobe vanilla flash and the pepperflash script for iceweasel?
i'm just asking; it would make a lot of sense to me.

damo · 2016-02-06 13:43:41

ohnonot wrote:

...
will the new bl-welcome also include a choice between adobe vanilla flash and the pepperflash script for iceweasel?
i'm just asking....

Not at the moment...may be something to consider though.

Head_on_a_Stick · 2016-02-06 13:48:49

Tricky to implement because the freshplayer package is only in jessie-backports so those would have to be added first.

johnraff · 2016-02-07 01:59:01

We are thinking of adding a pepperflash option to bl-welcome, but because it would need more than just an extra line or two of code it would probably not arrive till after the first BL release.

Last edited by johnraff (2016-02-07 02:00:18)

pvsage · 2016-02-07 04:10:30

^ Sounds good. I assume that will arrive via $(apt upgrade) and will have a hook to run immediately after install?

johnraff · 2016-02-07 04:59:33

pvsage wrote:

I assume that will arrive via $(apt upgrade)

Yes

and will have a hook to run immediately after install?

That's an interesting idea. All upgrades of bunsen-welcome to trigger a run of bl-welcome. Not easy to implement, though, because bl-welcome is a user command, and it's rude for package maintainers to modify users' settings...

(A reminder in the upgrade terminal window would be easy enough, however.)

ohnonot · 2016-02-07 08:33:20

johnraff wrote:

(A reminder in the upgrade terminal window would be easy enough, however.)

this.
for a fragile installation process like this pepperflash-backporting a howto is a good solution.

pvsage · 2016-02-07 12:46:34

^^ - I meant just a stub script for installing the freshplayer pepperflash plugin; could add a call to this stub in the bl-welcome script in anticipation of a point release after stable.

johnraff · 2016-02-08 02:27:13

@pv all the sub-scripts in bl-welcome are separate files. The main script calls them in turn. Adding a non-existent file to the list would be quite trivial - although a test for non-existent files would be needed, with suitable evasive action like not incrementing the page count etc. The main work would be in the "stub script" itself of course, but since they both arrive in the same package, would there be anything gained by editing the main script in advance of adding the stub?

Actually, it wouldn't be such a huge amount of work because the code for such user choices/tests is already in place, along with that for adding the backports repo. It would mostly be copy/paste and a bit of tweaking, plus a suitable user message. I just thought it was a bit late to push a change like that before the RC2 release. Maybe during the bug-fixing phase before the Big Release there will be time...

ohnonot · 2016-02-08 07:59:31

pvsage wrote:

I meant just a stub script

a stub script that just points to a howto here on the forums (HoaS wrote one iirc), until developed further?

johnraff wrote:

I just thought it was a bit late to push a change like that before the RC2 release.

no hurries, no worries!
just thinking out loud.

you know flash is always the first thing people complain about after $DISTRO is installed, even in 2016, and for many people pepperflash is the sole reason they use chrome on linux and allow themselves to be datamined by big G.

johnraff · 2016-02-09 05:10:32

BTW would it be necessary to make sure flashplugin-nonfree is uninstalled before installing browser-plugin-freshplayer-pepperflash and pepperflashplugin-nonfree? (or vice versa)

Also, pepperflashplugin-nonfree says "This package will download Chrome from Google, and unpack it to make the included Pepper Flash Player available for use with Chromium." Does that mean it installs Google Chrome (with possible privacy considerations for some users) or just extracts the pepperflash player and discards the rest?

Anyway, first off I have to actually try this out!

Last edited by johnraff (2016-02-09 05:11:28)

ohnonot · 2016-02-09 06:40:40

johnraff wrote:

Also, pepperflashplugin-nonfree says "This package will download Chrome from Google, and unpack it to make the included Pepper Flash Player available for use with Chromium." Does that mean it installs Google Chrome (with possible privacy considerations for some users) or just extracts the pepperflash player and discards the rest?

i think it picks out the flashplugin and discards the rest.
but, inside the flashplugin, privacy concerns are still in place, i guess.

#1 2016-01-22 03:01:43

[DONE]Remove flash from the Live ISO

#2 2016-01-22 03:34:01

Re: [DONE]Remove flash from the Live ISO

#3 2016-01-22 03:38:55

Re: [DONE]Remove flash from the Live ISO

#4 2016-01-22 04:28:33

Re: [DONE]Remove flash from the Live ISO

#5 2016-01-22 04:48:38

Re: [DONE]Remove flash from the Live ISO

#6 2016-02-06 05:34:01

Re: [DONE]Remove flash from the Live ISO

#7 2016-02-06 06:33:43

Re: [DONE]Remove flash from the Live ISO

#8 2016-02-06 07:00:17

Re: [DONE]Remove flash from the Live ISO

#9 2016-02-06 12:57:03

Re: [DONE]Remove flash from the Live ISO

#10 2016-02-06 13:43:41

Re: [DONE]Remove flash from the Live ISO

#11 2016-02-06 13:48:49

Re: [DONE]Remove flash from the Live ISO

#12 2016-02-07 01:59:01

Re: [DONE]Remove flash from the Live ISO

#13 2016-02-07 04:10:30

Re: [DONE]Remove flash from the Live ISO

#14 2016-02-07 04:59:33

Re: [DONE]Remove flash from the Live ISO

#15 2016-02-07 08:33:20

Re: [DONE]Remove flash from the Live ISO

#16 2016-02-07 12:46:34

Re: [DONE]Remove flash from the Live ISO

#17 2016-02-08 02:27:13

Re: [DONE]Remove flash from the Live ISO

#18 2016-02-08 07:59:31

Re: [DONE]Remove flash from the Live ISO

#19 2016-02-09 05:10:32

Re: [DONE]Remove flash from the Live ISO

#20 2016-02-09 06:40:40

Re: [DONE]Remove flash from the Live ISO

Board footer