I ran into a website that changed their SSL requirements again. Doggone it.
I can read and thank but cannot post or PM. The fellow has a 95 yr old brass carburetor part I'd really like to have.
Been looking at a new Seamonkey, Mine's quite old (2.49.1) and Mike's mega.nz site won't let me in due to the old browser.
Pale moon 27.6.1 behaves the same. Out of date also.
It's been years since I used an sfs file but excited to try it again. An old GUI guy.
What options are out there for old users like me when this happens?
I don't do windows.
SSL (Secure Socket Layer) changing again? (Solved)
Moderator: Forum moderators
-
TC-21-32
- Posts: 47
- Joined: Thu Feb 16, 2023 4:21 am
- Location: In my office in MN
- Has thanked: 63 times
- Been thanked: 11 times
SSL (Secure Socket Layer) changing again? (Solved)
Last edited by TC-21-32 on Tue Apr 11, 2023 11:24 pm, edited 1 time in total.
I still miss puppy 4.21. Been a user since 4.11 and never going back.
-
bigpup
- Moderator
- Posts: 6929
- Joined: Tue Jul 14, 2020 11:19 pm
- Location: Earth, South Eastern U.S.
- Has thanked: 897 times
- Been thanked: 1508 times
Re: SSL (Secure Socket Layer) changing again?
What Puppy version are you using?
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected 
-
TC-21-32
- Posts: 47
- Joined: Thu Feb 16, 2023 4:21 am
- Location: In my office in MN
- Has thanked: 63 times
- Been thanked: 11 times
Re: SSL (Secure Socket Layer) changing again?
Solved. I grabbed a tarball.bz from the SeaMonkey project for 2.53.16.
Plopped it in a save file and presto. Updated SSL. It even looked for SeaMonkey files on its own and I didn't even have to think.
Same browser, same tabs, same bookmarks with an upgraded backend. 
Thanks to the crew here, I got over my fear of tarballs. 
I still miss puppy 4.21. Been a user since 4.11 and never going back.