Old versions of Sage Line 50 being depracated

Didn't find your answer?

Apparently an email from Sage is wanging around the internet letting users know that versions of Line 50 prior to v26.2 will be switched off in September/October time. My account manager confirmed as much although I haven't had the infamous email...

Just wondering if this is the QBO equivalent announcement to push more users to SBCA?!?

Replies (5)

Please login or register to join the discussion.

avatar
By johndon68
19th May 2022 17:49

Strictly speaking, it's not all the old versions of Sage, it is older version that 'phoned home' to check licence details, I think from v21 onwards but don't know for certain.

This is because they used a security protocol called TLS1 which has been deprecated and v26.3 is the oldest version that uses the current version of TLS (1.2 I think).

This was supposed to be implemented in March but Sage have delayed it.

John

Thanks (1)
avatar
By Hugo Fair
19th May 2022 18:15

"depracated" ... ouch, twice! Even when spelled correctly, and even when (mis-)used by those in the IT community, it is meant to indicate something along the lines of technologies which have been replaced by newer technologies. [Features typically get marked as "deprecated", rather than simply removed, in order to provide backward compatibility.]

I suspect you meant 'dropped' or 'withdrawn' ... which is undoubtedly what Sage would like to do.

They (and QB et al) are stuck in a cleft-stick (between 'legacy' & 'current' products), but haven't yet found the cojones to declare Line 50 as 'legacy' - although their recent batch of announcements make fairly clear where their investment is focused.

There comes a point (in the marketing planner's Transition model) when any losses of legacy licences is a good thing (think of saved costs) - so long as they don't all show up as 'new business' for just one competitor.
In the meantime their optimum plan is to transition as many as possible to the new 'growth' lines, but it's not far to the horizon (after which a legacy client is just a cost).

Thanks (1)
Replying to Hugo Fair:
avatar
By JustAnotherUser
20th May 2022 08:27

Direct from IETF
The Internet Engineering Task Force (IETF) is the premier Internet standards body, developing open standards through open processes.

The IETF is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet.

"This document formally deprecates Transport Layer Security (TLS)
versions 1.0 (RFC 2246) and 1.1 (RFC 4346). Accordingly, those
documents have been moved to Historic status. These versions lack
support for current and recommended cryptographic algorithms and
mechanisms, and various government and industry profiles of
applications using TLS now mandate avoiding these old TLS versions."

I think they mean 'deprecated' .

Thanks (0)
Replying to JustAnotherUser:
avatar
By Hugo Fair
20th May 2022 12:27

By quoting from the IETF you're hardly undermining my point about "even when (mis-)used by those in the IT community" ... but:
* they're talking about a protocol which is being archived in order to retain backwards compatibility (not a commercial package that is being withdrawn from sale) ... so that does fall within the IT community's use of the word.

Do you disagree with any of my more pertinent comments about the dichotomy for software companies (between legacy and current products) ... or my prediction with regard to OP's question?

Thanks (1)
Replying to Hugo Fair:
avatar
By JustAnotherUser
20th May 2022 12:37

Just supplying some detail to the issue pal, ironically I dont think the word deprecated actually appears on any Sage communication about this, only by the IETF and this thread.

Thanks (0)