Bash "Shell Shock"

For discussions about security.
Post Reply
Message
Author
Kester

Bash "Shell Shock"

#1 Post by Kester »

This is my first post after rejoining the forum on the day I read about the Bash problem.

I have a dual boot desktop computer with a frugal installation of Puppy Precise 5.7.1 and XP Pro SP3. I also have a Windows 7 desktop computer which I occasionally boot with a Puppy Slacko 5.7 live DVD (a Puppy save file etc. is stored on the Windows 'C' drive).

Having just read of the potential threats concerning Bash, could the Puppy Linux experts who frequent this forum offer any advice to a relative beginner as to what steps can be taken to alleviate any possible problems.

Thank you.

User avatar
Ted Dog
Posts: 3965
Joined: Wed 14 Sep 2005, 02:35
Location: Heart of Texas

#2 Post by Ted Dog »

sadly puppylinux is mostly glued together as root with shellscripts. Some apps are just really complex scripts. But the way the flaw works requires some really old internet methods. which I do not think are used here. Needs fixing and should be easy replacement when its fixed.

User avatar
cimarron
Posts: 292
Joined: Fri 31 May 2013, 01:57

#3 Post by cimarron »


User avatar
Smithy
Posts: 1151
Joined: Mon 12 Dec 2011, 11:17

#4 Post by Smithy »

The BBC News was shrieking that it was a virus.
Shorely shome mistake there.
I heard facebook has been absolutely compromised at server level.

User avatar
prehistoric
Posts: 1744
Joined: Tue 23 Oct 2007, 17:34

#5 Post by prehistoric »

Don't we already have a simpler shell like ash, which is not vulnerable, in Puppy distributions? Inserting calls to ash in the few places where scripts call programs which directly interpret data from the Internet would provide a tested solution while waiting for tested patches to bash. This reduction in capability of the shell launching Internet programs should not have any adverse effect on the remainder of the system, and offers protection from scripting exploits we haven't even thought about.

Kester

Bash "Shell Shock"

#6 Post by Kester »

Hi,

I've followed some of the links provided by posters on this thread, downloaded and installed some recommended packages and tested Bash using the terminal. The results appear to have created a fix for the time being at least.

However, as a typical home PC user who can use the computer but is not necessarily completely au fait with what goes on underneath, I am still a bit apprehensive. I would appreciate advice in simple layman's language as to my best approach to be as secure as possible when using Puppy.

Thanks.

User avatar
Moose On The Loose
Posts: 965
Joined: Thu 24 Feb 2011, 14:54

Re: Bash "Shell Shock"

#7 Post by Moose On The Loose »

Kester wrote: However, as a typical home PC user who can use the computer but is not necessarily completely au fait with what goes on underneath, I am still a bit apprehensive. I would appreciate advice in simple layman's language as to my best approach to be as secure as possible when using Puppy.

Thanks.
If you are not running a web server etc, you don't have to deal with most of the security issues because someone outside your house doesn't really even know there is a computer to be targeted.

If you have a home router, think about its security first. This is what is connected to the outside.

Disable remote administration and use a wired connection for administration.
Change the password, write it down on something.
Enable the routers firewall

On your PC, follow all the usual advice about not going to dodgy web sites.

sheldonisaac
Posts: 902
Joined: Mon 22 Jun 2009, 01:36
Location: Philadelphia, PA

Re: Bash "Shell Shock"

#8 Post by sheldonisaac »

parts were snipped
Moose On The Loose wrote:
Kester wrote: I would appreciate advice in simple layman's language as to my best approach to be as secure as possible when using Puppy.
If you have a home router, think about its security first. This is what is connected to the outside.

Disable remote administration and use a wired connection for administration.
Change the password, write it down on something.
Enable the routers firewall
Finally!!
Thanks a lot, Moose On The Loose!

There are lots of settings in my Actiontec router (from Verizon) that say: Leave this alone unless you know what you're doing; or some such verbiage.
I did check that it was set according to your instructions.

Thanks again,
Sheldon
Dell E6410: BusterPup, BionicPup64, Xenial, etc
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P

Kester

Bash "Shell Shock"

#9 Post by Kester »

Hi Moose,

Glad you were on the loose so you could offer that useful advice.

I do not use the wireless facility of my ADSL Modem/Router so that part has not been set up and remains 'Off' - my only connections are via wired ethernet links - I don't even have my two desktops networked but transfer files, when necessary, via usb devices. The firewall is set in it's default setting which blocks outside networks accessing my system. I've not reset the password as yet so I will look into that now that I have downloaded the manual for my model (my ISP did not provide one when they replaced my previous defunct non-wifi device). My ISP tells me that firmware is updated automatically from their end and I need do nothing - they assure me that bash patches have been included in the recent firmware updates.

Other than the password issue, which should be resolved shortly, I think my setup meets the standards you advise but please let me know if you think I've missed something.

Thanks for your interest and help, Kester.

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#10 Post by bigpup »

If you have a home router, think about its security first. This is what is connected to the outside.

Change the password, write it down on something.
That is the first and most important thing to do.
CHANGE THE PASSWORD!!!!!!!

The easiest way to compromise a system. Use the manufactures password to gain access.
All the manufactures hardware comes setup with a default password that is easy to find. Go to Google search.

Example:
For most NETGEAR devices, except ReadyNAS products and Fully Managed Switches, the following are default the username and password :

Username = admin
Password = password
( For older devices, Password = 1234 )

So, Change The Password when you get the hardware.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

Kester

#11 Post by Kester »

@bigpup and moose,

Router password changed successfully - thanks for the nudges.

I was surprised that ZyXEL only accepted letters and numerals in the password. My password creation system includes non-numeric/non letter symbols at its higher security level - I had to fall back to a lower security level to get my password to work.

Anyway, all done now, cheers, Kester.

bark_bark_bark
Posts: 1885
Joined: Tue 05 Jun 2012, 12:17
Location: Wisconsin USA

#12 Post by bark_bark_bark »

Shellshock Is Still a Risk, Even for Patched Machines
Ionut Ilascu wrote:Systems that have been immunized against Shellshock are still vulnerable to exploits for this vulnerability in Bash command interpreter, under certain conditions.
The attack would have to be carefully planned and multi-layered, but an experiment carried out by security researchers at Trend Micro shows that it can be done, unless preventative security solutions are in place.
....

Post Reply