|
From: Gerd W. <ger...@t-...> - 2022-02-24 20:25:12
|
Recently all SQuirreL dropped all Log4j dependencies. Accordingly only recent snapshots contain this change, for example https://sourceforge.net/projects/squirrel-sql/files/3-snapshots/snapshot-20220222_1929/ Unfortunately neither for version 4.2.0 nor for any other version existing today there will be any patch releases. https://adoptium.net/releases.html provides current Java versions that don't require installation but just unzipping. Perhaps that's an option. Gerd Am 23.02.22 um 22:08 schrieb Manyam, Hema "Sekhar": > Hi, > > We are trying to use Opensource_SquirrelSQLClient_4.2.0 for connecting > to database. This is the first time we are going to install the client > software at our company. There are several log4j files packaged with the > product. > > Log4j issue was reported during November 2021, the log4j file inside > package were created during May 2021. > > We cannot install v4.3 as it needs Java SE v11 as prereq. We have JRE > v1.8 at our company so we can only install v4.2.0. > > Please let me know whether log4j related issues were resolved in v4.2.0. > > Thanks, > > *Sekhar* > > DTCC DISCLAIMER: This email and any files transmitted with it are > confidential and intended solely for the use of the individual or entity > to whom they are addressed. If you have received this email in error, > please notify us immediately and delete the email and any attachments > from your system. The recipient should check this email and any > attachments for the presence of viruses. The company accepts no > liability for any damage caused by any virus transmitted by this email. > Message content created by DTCC is automatically secured using Transport > Layer Security (TLS) encryption and will be encrypted and sent through a > secure transmission connection if the recipient's system is configured > to support TLS on the incoming email gateway. If there is no TLS > configured or the encryption certificate is invalid on the recipient's > system, the email communication will be sent through an unencrypted > channel. Organizations communicating with DTCC should be using TLS v1.2 > or newer to ensure continuation of encrypted communications. DTCC will > not be responsible for any disclosure of private information or any > related security incident resulting from an organization's inability to > receive secure electronic communications through the current version of > TLS. > > > _______________________________________________ > Squirrel-sql-users mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users |
