Openssl update to 1.0.1k

[robert_m]

Dear musher0 -

My glasses are fine, I responded to 8Geee (at 3:15 AM local time) and then downloaded the sfs file and then back to bed. I live next door to a UCSC student household, and they had decided to have a party that began at 1 AM.

I am just getting around to trying it out, I promise I will report back.

Please be patient, I'm new to Puppy and I'm not very quick, taking notes and whatnot.

I do appreciate the build of the latest, and your recommendation that it should work for me.

Regards,

[8Geee]

Musher:
appologies

I confused the slacko 5.7.1 with the precise (deb) 5.7.1. I thought robert_m was using slacko, so my comments were in-line. When I looked carefully again, I saw the deb Ubuntu reference, and appologized to him for the confusion I had. I do realize there are different needs for different distro-bases.

It was not my intent to cause a chase down a rabbit hole.

Thank you for your efforts in this matter.

Regards
8Geee

[robert_m]

This is my second experience with installing packages on Puppy. I am really impressed with how intuitive the interface is, and how many things just work.

I copied the file openssl-1.0.2f.sfs to a partition on my flash drive (from my network share - no setup required)

I found the menu=>setup=>SFS load-on-the-fly utility and loaded the new file.

I the version and date are as before:

Code: Select all

# openssl version -a
OpenSSL 1.0.1 14 Mar 2012
built on: Mon Apr 15 15:27:09 UTC 2013

I rebooted, re-loaded, no difference.

This is probably due to my inexperience.
Should oppenssl show up in the package manager "installed Packages" box? The nvidia driver (pet) I installed is there.
I didn't see any errors when I loaded it.
I unloaded and loaded, got confirmation messages - success- for both operations. Still, the openssl version is not correct.

I moved the sfs file to /root/home ( as instructed in
http://puppylinux.org/wikka/software, repeated the install process, same result except as shown in the attached images

Any help is appreciated.

[slavvo67]

Only pet files show up as installed. You can convert the sfs to a .pet file with sfs2pet or some other converter on this board. Then, when you click on the pet, it will install and reflect in the PPM.

[musher0]

Only pet files show up as installed. You can convert the sfs to a .pet file with sfs2pet or some other converter on this board. Then, when you click on the pet, it will install and reflect in the PPM.

There is a pet available for this, as well as the sfs. Please see above:
http://murga-linux.com/puppy/viewtopic. ... ost#888366

[watchdog]

What about puppy 4.31, wary and lucid? They are no longer supported. I'm not using them but if I should keep one of them in hands then I would experiment a glibc upgrade and use the musher0's openssl pet.

LATER: I have compiled openssl-1.0.2f in wary with glibc 2.10.1. It is not recommended to upgrade core libraries: it's only at your own risk. It works for me and I have tested it but not deeply.

openssl-1.0.2f-w5-i486.pet:

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

openssl_DEV-1.0.2f-w5-i486.pet:

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

openssl_DOC-1.0.2f-w5-i486.pet:

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

Code: Select all

# openssl version -a
OpenSSL 1.0.2f  28 Jan 2016
built on: reproducible build, date unspecified
platform: linux-elf
options:  bn(64,32) rc4(8x,mmx) des(ptr,risc1,16,long) idea(int) blowfish(idx) 
compiler: gcc -I. -I.. -I../include  -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -DL_ENDIAN -O3 -fomit-frame-pointer -Wall -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM -DVPAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM
OPENSSLDIR: "/etc/ssl"

[perdido]

This is my second experience with installing packages on Puppy. I am really impressed with how intuitive the interface is, and how many things just work.

I copied the file openssl-1.0.2f.sfs to a partition on my flash drive (from my network share - no setup required)

I found the menu=>setup=>SFS load-on-the-fly utility and loaded the new file.

I the version and date are as before:

Code: Select all

# openssl version -a
OpenSSL 1.0.1 14 Mar 2012
built on: Mon Apr 15 15:27:09 UTC 2013

I rebooted, re-loaded, no difference.

Any help is appreciated.

Here you go!

Follow the instructions here http://www.bleepingcomputer.com/forums/ ... linux-571/

And you should end up here

Code: Select all

# openssl version -a
OpenSSL 1.0.1 14 Mar 2012
built on: Thu Jan  7 15:13:24 UTC 2016

No re-boot required.
That is the latest from Ubuntu for Precise 12.04

If you google

Code: Select all

precise 12.04 openssl package

About the 3rd hit is http://packages.ubuntu.com/precise/openssl

On the middle-right side of that page, listed under "Ubuntu Resources" is the "Ubuntu Changelog" that will show the changes and dates to the openssl package. Have fun!



.

[robert_m]

perdido -You have found this! The link that you posted to bleepingcomputer.com is actually how I began: it lead me to return here and ask if upgrading was necessary. Thanks for the pointer to "openssl (1.0.1-4ubuntu5.33) [security] "

Before I go of and try their method, I will finish up with the build that musher0 posted.

~~~~~~

musher
When I installed the openssl-1.0.2f.pet file it installed without incident, and I can see it in "Puppy Package Manager" dialog under " Installed Packages"

and from the command line

Code: Select all

# openssl version -a
OpenSSL 1.0.2f  28 Jan 2016
built on: reproducible build, date unspecified
platform: linux-elf
options:  bn(64,32) rc4(8x,mmx) des(ptr,risc1,16,long) idea(int) blowfish(idx) 
compiler: gcc -I. -I.. -I../include  -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -DL_ENDIAN -O3 -fomit-frame-pointer -Wall -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM -DVPAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM
OPENSSLDIR: "/usr/ssl"

(musher0)
My naive conclusion is that

1. openssl was successfully updated
2. the build is untested
3. a sufficient test is to encrypt and decrypt a file
4. the encrypted file can be decrypted with other past and future versions of openssl and TBD software

I have visited http://www.openssl.org/ and I see the 1.0.2f is the latest release, and considering the build notes

(musher0)
Yes my package should be compatible with Puppy Precise 5.7.1 since that PrecisePup uses glibc 2.15, a higher version retro-compatible with the glibc 2.13 that I compiled your openssl on.

Another reason is that ubuntu is derived from debian, and therefore ubuntu-type
Puppies are also Debian-compatible Puppies.

I am off to try using the encryption software. I will report back, for now accept my thanks to all for your attestation and efforts in helping me get the latest code on my system.

[6502coder]

@ musher0 and watchdog: thanks for the PET/SFS builds. Much appreciated.

Edit: @ watchdog: I installed your openssl-1.0.2f-w5-i486.pet on my Wary 5.1.4.1 which has glibc 2.11.1. No problems found so far.

[musher0]

My pleasure!

[watchdog]

If you use an ubuntu based puppy like precise or tahr (lucid is no longer supported) you have to update lists of packages in PPM and reinstall libssl and openssl (also if they are listed in PPM as already installed). Ubuntu use patched sources of openssl so the build date is what is important to see typing:

Code: Select all

openssl version -a

Sometimes updated openssl for a mantained puppy is available by quickpet, bugfix or updates manager in Menu-Setup.

[moeppyfan]

Another update today: https://www.openssl.org/news/secadv/20160301.txt

OpenSSL 1.0.2 users should upgrade to 1.0.2g
OpenSSL 1.0.1 users should upgrade to 1.0.1s

[8Geee]

not quite in the slackware repo yet, will keep an eye open fot it.

Thanks for the heads-up.

regards
8Geee

[watchdog]

openssl-1.0.2g-w5-i486.pet:
https://drive.google.com/file/d/0B9iMb4 ... sp=sharing

openssl_DEV-1.0.2g-w5-i486.pet:
https://drive.google.com/file/d/0B9iMb4 ... sp=sharing

openssl_DOC-1.0.2g-w5-i486.pet:
https://drive.google.com/file/d/0B9iMb4 ... sp=sharing

[6502coder]

@watchdog
Thanks for the pets. Installed w/o problems on Wary 5141.

[8Geee]

For those using 1.0.1 the "s" update is available for slacko puppies.

[musher0]

@watchdog
Thanks for the pets. Installed w/o problems on Wary 5141.

Same on "The Pooch" (experimental Dpup-3.14.56.1). Again thanks.

[paulh177]

Hello all.
... snip ...
You can download it as pets:
https://www.adrive.com/public/Knut3A/openssl-1.0.2f.pet (main archive)
https://www.adrive.com/public/7avQ9B/op ... 2f_man.pet (separate man files)

... or as an sfs for any Puppy:
https://www.adrive.com/public/WJrAAh/openssl-1.0.2f.sfs
.

These links are broken:

Code: Select all

The public file you are trying to download is associated with a non-valid account. 

Please contact the owner for further assistance.

I'd like to get my paws on this (see http://www.murga-linux.com/puppy/viewto ... 562#988562) ... anyone know where I can find a copy?

[musher0]

Hi PaulH177.

Sorry for the inconvenience. I ran out of money to keep that repo open. In
any case, that openssl version would be about two years old now.

Can you get one from your Pup's PPM? Is it current?

Another problem that I discovered, is that some Internet apps (e.g. the links
browser) want the openssl version that was on the Puppy at the time the
app was compiled -- they will not work with another version of openssl.

This does not help you much, eh?

BFN.