Fatdog64-700 beta1

[Bindee]

Thanks James

[JustGreg]

@Bindee

I read at the article. Under the comments, there was a way to test for the bug. Here is the code I used to test:

Code: Select all

#!/bin/sh
env X="() { :;} ; echo busted" /bin/sh -c "echo completed"
env X="() { :;} ; echo busted" `which bash` -c "echo completed"

Here are the results from running the code:

busted
completed
busted
completed

Both Fatdog64 version 631 and 700b1 produced the same results. I would not panic. Usually, a fix will be available in a short time. The issue will be with the devices that have embedded Linux that required update from the manufacturer.

@jamebond,

The my thunderbird package was in the /var/log/packages directory. The text file is a listing of the components installed. I tied "slapt-get --list | grep thunderbird" command. The thunderbird package was not there. I also tried "slapt-get --update". It did not work with a reported error. I was able to remove the package with "removepkg -warn thunderbird-package-name". I did encounter an error on my part. The -warn option gave me a warning on /spot/.thunderbird directory. I did not give a correct answer to remove or not remove. I had to use control c to stop the process. But, the package was removed.

I also tried several different permission levels for the /spot/.thunderbird directory used by thunderbird. I did know about making sure the ownership/group of the directory was spot. I found the suggested value of 660 did not work. The lowest value was 760, which allowed thunderbird to find the user profile and use it.

I will try a few more things to see what happens.

[Bindee]

I was reading that the bash update is only a partial fix until they patch it correctly.

[Q5sys]

I got some time to tinker today, got it installed on one of my netbooks, and she's running well.
http://q5sys.sh/fatdog/fatdog700b1-acer.png

I was able to build a few packages which I will be uploading soon. Have a long list to work my way down. I tried to fire it up on my workstation but ran into a problem with my nvidia cards. That system has dual GTX660ti cards. If I allow nouveau to load I get a running system, just with all six screens displaying the same thing. However if I try to boot and blacklist the nouveau module, I still get the 'Loading nouveau module early' line and then it tries to start X. Unfortunately, I cant get into X... system just locks up and the framebuffer on the screen will jump back about 5 lines so I cant see if Im getting an error or not.

Couple other things that stood out to me. In the install tool, anyway you can put the drive size or something next to the device name? I have 12 drives attached to that system, so just seeing a list of sda devices doesnt help explain whats what. It's not a biggie since I just opened gparted to figure out what drive was what... but more novice users may not be able to figure out which hard drive is which in their system since there is no identification of any kind given.

For some reason on my board I have to wait a super long time to get my ethernet to connect after boot, it takes like 2 minutes. I can only assume there's something going on with the multiple nics on my board. Again, not something most people will ever have to deal with, and I reboot so infrequently that its probably not worth anyone worrying about.

EDIT:

So I was being an idiot, I remembered that I need to add the kernel option 'nomodeset' in addition to 'blacklist=nouveau' If anyone else experiences a blank screen when trying to blacklist the nouveau module use the following when you are booting:

Code: Select all

fatdog nomodeset blacklist=nouveau

After you have done that you should auto boot with the vesa driver. You can try the following package but I am not promising that it will work for you. http://q5sys.sh/fatdog/Nvidia-343.22-x86_64-1.txz

As fatdog itself is still beta, there will probably be issues. As it is I am already aware of a libvdpau issue with it. See: http://q5sys.sh/fatdog/nvidia-beta-driver-package.png
That image will also show you the driver package size compressed and installed. So please make sure your save file is large enough for you to install it.
Again, no promises that this will work for you, you will still need to edit your /etc/X11/xorg.conf. I have included mine in the package so that you can have something to start with. Keep in mind that if your system tries to load my xorg.conf file it will fail. You will need to alter it to work on your system. the nvidia package can generate a default file using the 'nvidia-xconfig' binary, but again... no promises. Once you get X to start using the Nvidia driver, open a terminal window and use 'nvidia-settings' to fine tune your display.

[Billtoo]

One more time

New install of fatdog64 beta 1 to a 32gb flash drive:

video-info-glx 1.5.3 Thu 25 Sep 2014 on Fatdog64 700 Linux 3.16.2 x86_64
0.0 VGA compatible controller: NVIDIA Corporation GF110 [GeForce GTX 560 Ti OEM] (rev a1)
oem: NVIDIA
product: GF110 Board - 12630002 Chip Rev

X Server: Xorg Driver: nvidia
X.Org version: 1.15.2
dimensions: 3840x1080 pixels (1204x343 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 560 Ti/PCIe/SSE2
OpenGL core profile version string: 4.3.0 NVIDIA 343.22

Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Core 0: @1607 1: @1600 2: @1599 3: @1661 4: @1749 5: @1878 6: @1598 7: @1600 MHz

I added xfce4-4.10 and a few other applications but I don't know how to
package them so I can't share them others, too old/not motivated to
learn how.

I will use this as my main puppylike OS until the next release comes
out, if I don't break it somehow or get bored and do another fatdog64
install.

Thanks again to kirk and james for a great OS.

[Q5sys]

I added xfce4-4.10 and a few other applications but I don't know how to package them so I can't share them others, too old/not motivated to learn how.

Its actually rather simple in reality, but I understand that sometimes you just dont want to put forth the effort. I was considering building KDE today... then I decided... 'meh'. lol

[Yoni]

Latest Firefox and Thunderbird updates plug CRITICAL SSL vuln

http://www.theregister.co.uk/2014/09/25 ... h_ssl_vuln

Mozilla Firefox needs patching urgently following the discovery that the open source browser is vulnerable to SSL man-in-the-middle attacks.

The critical bug arises because the Network Security Services (NSS) libraries parser built into the browser is capable of being tricked into accepting forged RSA certificate signatures.

Man-in-the-middle attacks create a means for attackers to impersonate a bank or webmail provider, tricking surfers into handing over logon credentials that can be relayed to the genuine organisation.

Normally surfers would be confronted with a warning that the certificate of the site was invalid, but this would not happen in cases where man-in-the-middle attacks are in play.

Fortunately patches are already available. Firefox ESR 31.1.1, Firefox ESR 24.8.1, Thunderbird 31.1.1, and Thunderbird 24.8.1 have been updated to NSS 3.16.2.1.

Firefox 32.0.3 and SeaMonkey 2.29.1 have been updated to NSS 3.16.5.

It almost goes without saying that all these updates are rated as critical.

The bug was discovered by Antoine Delignat-Lavaud, a security researcher at Prosecco. More details are available in Mozilla's advisory

https://www.mozilla.org/security/announ ... 14-73.html

Had all better use the latest version.

[jamesbond]

@JustGreg

Both Fatdog64 version 631 and 700b1 produced the same results. I would not panic. Usually, a fix will be available in a short time. The issue will be with the devices that have embedded Linux that required update from the manufacturer.

I said this

Updated bash (look for bash-4.2-x86_64-2.txz) is already in the repo since yesterday.

Probably not clear enough, but that is the patched version of bash. Try that and your test will not work anymore.

@Yoni - how tiring, I just patched bash yesterday and now another one [Comment not targeted at you but targeted at the fact that a week cannot pass without new security issues ...] Anybody who is worried is advised to get the official Firefox from mozilla, there is a thread somewhere where I outline how to install it.

I'll reply the rest later. For video problems kirk will probably be the one replying

[Yoni]

@Yoni - how tiring, I just patched bash yesterday and now another one [Comment not targeted at you but targeted at the fact that a week cannot pass without new security issues ...] Anybody who is worried is advised to get the official Firefox from mozilla, there is a thread somewhere where I outline how to install it.

Yeah i know what you mean as these serious security updates make having to remaster a pain as well.

Shame there isn't a way for those of us on fast connections that Fatdog could download the latest firefox and flashplayer on each boot so it's always running the latest version.

Unless it could be scripted in some way?

[eowens2]

jamesbond said

Updated bash (look for bash-4.2-x86_64-2.txz) is already in the repo since yesterday.

Probably not clear enough, but that is the patched version of bash.

When I go to Control Panel/System/Gslapt Package Manager, and look for “bash

[stemsee]

FatDog Remastering app.
Needs testers.
Remasters all the way to iso (unattendremaster) including auto-repack initrd.

Burn hybrid iso to cd/dvd or write it to usb. Create savefile function as well.

sfsdirect - very fast remaster, running-system to sfs in ram or on device
EDIT: 29th September 2014

Here it is!

rc2 of StemSeeS-Remastering-Suite.sfs

EDIT 30th September 2014 01:00

https://drive.google.com/file/d/0B4GhZV ... sp=sharing

[step]

jamesbond said

Updated bash (look for bash-4.2-x86_64-2.txz) is already in the repo since yesterday.

Probably not clear enough, but that is the patched version of bash.

When I go to Control Panel/System/Gslapt Package Manager, and look for “bash

[JustGreg]

Thank you JamesBond and step for the information on update Bash to eliminate the security issue. I used gslapt to get and installed the patched version of Bash. The information from step is very useful. I did get the error he wrote about. Following his advice, I downloaded and installed the patched version of Bash using gslapt.

I rebooted to ensure the system started from a known clean state. When I ran the test script for the vulnerability, the vulnerability was not present and here was the response:

Code: Select all

/bin/sh: warning: X: ignoring function definition attempt
/bin/sh: error importing function definition for `X'
completed
/bin/bash: warning: X: ignoring function definition attempt
/bin/bash: error importing function definition for `X'
completed

Clearly, the problem is solved. We all have to update to really solve the problem. It is truly amazing how quickly these security vulnerabilities are solve by the Linux community.

[Bindee]

Sadly it will need another update in the near future as the current one is just a quick partial fix by the reports online.

[Q5sys]

Just noticed that if I load a SFS file, the menu entries are added into the fatdog menu. If you unload the SFS file... they arent removed. I havent taken a peek at the unload script, but I'll see about maybe adding in the refresh menu thing.
I'll add it on my list of things to take a crack at if I get time this weekend. I'm neck deep in an awesome project for puppy though that I want to keep focusing on for right now... or i'd go tackle it right away.

[eowens2]

step said:

In gslapt, cLick the update icon to update sources. If it says that the contrib source is unavailable choose to disable it and continue.
Then search for bash and you should get both bash- 4.2-x86_64-1 and bash- 4.2-x86_64-2. If you don't disable the faulty source sources don't get updated so you don't get bash- 4.2-x86_64-2.

You can also download the file directly from the package repo: open firefox in FD700beta and go to the home page. Read down the page until you find the link to the repo.

Thanks, step. Patched version (bash-4.2-x86_64-2) found and installed. Test script run, results same as those posted by JustGreg.

[jamesbond]

Please update to bash-4.2-x64_64-3.txz; and afterwards confirm that "bash --version" shows patchlevel 49

GNU bash, version 4.2.49(2)-release (x86_64-unknown-linux-gnu)

patchlevel 49 fixes this issue: http://murga-linux.com/puppy/viewtopic. ... 895#800895

[prehistoric]

Not seeing bash-4.2-x64_64-3.txz in http://distro.ibiblio.org/fatdog/packages/700/, but not getting update on contributed directory. Where should I look for it?

[Q5sys]

Not seeing bash-4.2-x64_64-3.txz in http://distro.ibiblio.org/fatdog/packages/700/, but not getting update on contributed directory. Where should I look for it?

Also regarding packages in the repo:

[eowens2]

I have been trying to update a realtek wireless driver, and have downloaded a package to do this.

The process uses the command "dkms", as in

Code: Select all

#dkms add ./rtl8192cu-fixes
#dkms install 8192cu/1.9

to be entered in the terminal, but the command does not seem to be in the fd64-devx_700b1.sfs or the package repo.

Might it be possible to add this to the devx/repo?