June 2023, AWS Will Break TLS 1.0, 1.1, Jungledisk

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


Well-known member
Sep 30, 2020
Hi all. Thought you might like to see this note I got from Amazon Web Services (AWS). In June 2023, they will break TLS 1.0 and 1.1 on their systems which will break anything using it, including old installs of Jungledisk. I have not been upgrading as it does exactly what I want and new versions of programs, particularly when there are management changes, break old features and user interfaces that used to work. Looks like now I'll have no choice. Here is a copy of an email AWS sent me. I got something similar from my email provider. Thought I'd pass it along. (below) @Steve may or may not have covered this on the podcast as I'm a bit behind in listening.

May your bits be stable and your interfaces be fast. :cool: Ron

(email from AWS)


AWS is updating the TLS configuration for all AWS API endpoints to a minimum of version TLS 1.2. In preparation for this update, we have identified TLS 1.0 or TLS 1.1 connections to AWS APIs from your account that must be updated to maintain AWS connectivity. Please update your client software as soon as possible to use TLS 1.2 or higher to avoid the risk of an availability impact.

We are making this change so our customers can benefit from the enforcement and simplification of only modern TLS encryption protocols. This update will remove the ability to use TLS versions 1.0 and 1.1 with all AWS APIs in all AWS Regions by June 28, 2023. Therefore, we recommend considering the time needed to verify your changes in a staging environment before introducing them into production.

How can I determine the client(s) I need to update?
We have provided the connection details following this messaging to help you pinpoint your client software that is responsible for using TLS 1.0 or TLS 1.1, so you can update it accordingly. Additionally, our related AWS Security blog post [1] provides information on how you can use TLS information in the CloudTrail tlsDetails field.

If you need further guidance or assistance, please contact AWS Support [2] or your Technical Account Manager.

[1] https://aws.amazon.com/blogs/security/tls-1-2-required-for-aws-endpoints
[2] https://aws.amazon.com/support

Please see the following for further details on the TLS 1.0 or TLS 1.1 connections detected from your account between August 19, 2022 and September 02, 2022 (the UserAgent may be truncated due to a limit in the number of characters that can be displayed):

Region | Endpoint | API Event Name | TLS Version | Connection Count | UserAgent
us-east-1 | s3.amazonaws.com | ListBuckets | TLSv1 | 10 | [Jungle Disk Desktop HTTP/86]
us-east-1 | s3.amazonaws.com | GetBucketLocation | TLSv1 | 20 | [Jungle Disk Desktop HTTP/86]

Amazon Web Services
Hi all,

It looks like the time is coming up soon when all my backups to Jungledisk will break. Is anyone else still using it? I have intentionally been not upgrading the software as upgrades tend to break things and change things and I've had the system running exactly like I wanted since @Steve recommended the product many years ago. I also have a number of filters and rules in place and I haven't wanted to risk upgrades. Is anyone using Jungledisk with Amazon S3 and TLS 1.2? What did you have to do to upgrade and did it affect your backups and procedures?

Going to jungledisk.com now forwards to cyberfortress.com. I found a couple of Jungledisk related pages but am not sure what level of support Jungledisk is now getting.

I found this press release from last year. The press release gives me the impression that they've completely forgotten individual users.

I hate it when something I've got running like a well oiled machine stops working and I have to spend dozens if not hundreds of hours fixing it.

May your bits be stable and your interfaces be fast. :cool: Ron
Last edited:
Hi all. Been doing some detective work. I found out how to upgrade Jungledisk Desktop (not workgroup) to the latest version from about 2 years ago. It supports TLS 1.2 so it should at least fix my problem for a while. I have to do the procedure on all my PC's. If you need it, here is the procedure for updates. I checked my Jungledisk settings and they appear to be the same as before. I'm currently running a Jungledisk backup to Amazon S3 and it seems to be working. Even though Cyber Fortress doesn't seem to be marketing to individuals, their tech support was very helpful. See below for the procedure.

May your bits be stable and your interfaces be fast. :cool: Ron


Go to:

You will find this phone number for support which forwards to another number:


You may discuss your situation with a human if you wish.

Upgrade procedure:

Go to:

Login with your jungledisk email and password. Click link to go to the control panel.

Click download software.

As of Jungledisk Desktop 3.21 all TLS is 1.2 as far as I know.

Go to the desktop section. Download your software.
For me it's win 64 ver 3.34.1.

Copy Jungledisk desktop software existing folder to a backup folder.

Run Jungledisk desktop monitor.
Go to configuration, enter password if necessary.

Turn on check box to show advanced settings if relevant.

Expand online disk drive for this pc.

Expand network drive.

Expand legacy backup (if relevant)

Expand my backup (or whatever's relevant).

Click on my backup (or whatever's relevant).

To the right click export backup job configuration.
Select a destination folder.

Cancel out of configuration.

Close desktop monitor window.

Close desktop monitor from system tray by right click and exit.

Run jungle disk 3.34.1 installer from the folder you downloaded it to.

Install to same folder that 3.16 (or whatever you have) was in.

In my case, it failed with this error:
Visual c++ 2015 - 2019 Redistributable (x64) required:
Get the latest version here:

Go download that file and save it in a folder, run virus scan on it, and run it.

Run jungle disk 3.34.1 installer from the folder you downloaded it to.

Install to same folder that 3.16 (or whatever you have) was in.


Jungledisk desktop should be ready to run at version 3.34.1 with TLS 1.2 support. You may wish to check your settings to make sure all were imported properly.


Following is a copy of a letter from tech support which explains further.


Thanks for calling Cyber Fortress Support!

Today, you called to know if the latest version of Jungle Disk Desktop (version 3.34.1) supports TLS 1.2 since Amazon is now requiring all TLS protocols to run 1.2 for all AWS API endpoints. After reviewing your installation report, all machines are still running version 3.16. Jungle Disk Desktop 3.21 began supporting TLS 1.2 only and you may find this in this information in the Release Notes in the Control Panel. You may download the latest version of Jungle Disk Desktop 3.34.1 in the Jungle Disk Downloads page in the Control Panel.

If you have any other questions, please feel free to contact us again and we'll be happy to help :)

Data Security Technician

  • Like
Reactions: RobAllen