HEX

File: D:/hMailServer/Data/showfile.com/admin/F5/{F5EC1829-C68F-47B0-AB75-43827B7F3834}.eml
Sender: noreply@tickets.rackspace.com
Date: Thu, 02 Oct 2025 19:00:06 +0000
Mime-Version: 1.0
Subject: Rackspace Cloud Support Update to: Disabling TLSv1.0/TLSv1.1 on Cloud Files
 CDN
From: Rackspace <noreply@tickets.rackspace.com>
To: admin@showfile.com
Message-Id: <20251002190006.c37ad556eefbe439@tickets.rackspace.com>
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.=
w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns=3D"http://www.w3.=
org/1999/xhtml"><head><meta http-equiv=3D"Content-Type" content=3D"text/htm=
l; charset=3DUTF-8" /><title></title></head><body marginheight=3D"0" margin=
width=3D"0"  bgcolor=3D"#f2f2f2"  topmargin=3D"0" leftmargin=3D"0"><br /><t=
able cellpadding=3D"0" cellspacing=3D"30" align=3D"center" bgcolor=3D"#dddd=
dd" ><tbody><tr><td valign=3D"middle" align=3D"center"><table border=3D"0" =
width=3D"640" cellpadding=3D"0" cellspacing=3D"0" style=3D"border:solid; bo=
rder-color:#cccccc;border-width:1px;" bgcolor=3D"#f5f5f5" ><tbody><tr><td b=
gcolor=3D"#f5f5f5" align=3D"left" style=3D"padding:20px;" ><img src=3D"http=
://b5d0ce80172fc36e9fca-d061b04efe6d45939e9c766c5e94c22b.r27.cf1.rackcdn.co=
m/newEmailHeaderLogo.png" /></td><td align=3D"right" bgcolor=3D"#f5f5f5"><f=
ont size=3D"2" face=3D"Helvetica, Verdana, Arial, sans-serif"><div id=3D"ac=
countNumber" style=3D"color:#000000;margin-right:10px;"><span style=3D"colo=
r:#999;">Account: </span>Vince Herbert (#10033994)</div><div id=3D"ticketNu=
mber" style=3D"color:#000000;margin-right:10px;"><span style=3D"color:#999;=
">Support Ticket: </span>#251002-iad-0010455</div></font></td></tr><tr><td =
colspan=3D"2" bgcolor=3D"#FFFFFF" style=3D"border: solid 0 #dddddd; border-=
top-width:1px; text-align:left;"><table border=3D"0" cellpadding=3D"0" cell=
spacing=3D"0" ><tr><td align=3D"left" bgcolor=3D"#FFFFFF"><font size=3D"2" =
face=3D"Helvetica, Verdana, Arial, sans-serif" ><blockquote><div id=3D"mess=
ageBody" style=3D"text-align:left;">Dear Vince,<p> A Rackspace Cloud suppor=
t ticket has been created to provide you with important information related=
 to your account.</p></div></blockquote></font></td></tr></table></td></tr>=
<tr><td colspan=3D"2" align=3D"center" bgcolor=3D"#FFFFFF"><table border=3D=
"0" cellpadding=3D"0" cellspacing=3D"0" ><tr><td align=3D"center" bgcolor=
=3D"#FFFFFF"><font size=3D"2" face=3D"Helvetica, Verdana, Arial, sans-serif=
"><blockquote><div id=3D"nextGenImageId" style=3D"text-align:left;"><p> Vie=
w this ticket at:</p><img src=3D"http://c3454057.r57.cf0.rackcdn.com/images=
/next-gen-cp-icon.png" alt=3D"" /><br /> <br /><a href=3D"https://mycloud.r=
ackspace.com/tickets" target=3D"_blank">mycloud.rackspace.com</a></div></bl=
ockquote></font></td></tr></table></td></tr><tr><td colspan=3D"2" bgcolor=
=3D"#FFFFFF" style=3D"border: solid 0 #dddddd; text-align:left;"><table bor=
der=3D"0" cellpadding=3D"0" cellspacing=3D"0" ><tr><td align=3D"left" bgcol=
or=3D"#FFFFFF"><font size=3D"2" face=3D"Helvetica, Verdana, Arial, sans-ser=
if" ><blockquote><div id=3D"ticketComment" style=3D"text-align:left;"><p>Ti=
cket comments:</p><hr/>
<pre style=3D"width: 700px; white-space: pre-wrap;">
Hello Rackspace Customer,

We are writing to inform you that we will disabling TLS v1.0 and TLS v1.1 p=
rotocols for requests to Rackspace Cloud Files CDN:

       October 16, 2025:  12:30 - 18:30 CDT (17:30 - 23:30 UTC)

We are making this change as part of an overall strategy to modernize all R=
ackspace systems to TLS 1.3. Due to both evolving regulatory requirements a=
nd security vulnerabilities in previous versions of TLS, we are initially p=
hasing out any versions prior to TLS 1.2. Any connecting systems now must s=
upport TLS version 1.2, at minimum, to connect to Rackspace Cloud Files CDN=
=2E

What is TLS?
TLS is a security protocol for establishing encrypted communication channel=
s over computer networks, protecting almost all Web traffic.  Older version=
s of this protocol (prior to 1.2) are vulnerable to attacks that could comp=
romise data sent over the network.
Rackspace recommends that customers completely remove all TLS support prior=
 to version 1.2 from their environments and start planning to move to TSL 1=
=2E3. Again, for this update customers=20=
must ensure that any systems or softwa=
re connecting to Rackspace Cloud Files support at least TLS version 1.2.

----------

What endpoints are involved?
The SSL links which show for any CDN-enabled Cloud Files containers in ever=
y region. =20

These include links with the following strings within them:
=E2=80=A2	ssl.cf0.rackcdn.com
=E2=80=A2	ssl.cf1.rackcdn.com
=E2=80=A2	ssl.cf2.rackcdn.com
=E2=80=A2	ssl.cf3.rackcdn.com
=E2=80=A2	ssl.cf4.rackcdn.com
=E2=80=A2	ssl.cf5.rackcdn.com
=E2=80=A2	ssl.cf6.rackcdn.com

The Rackspace Cloud Files API designates these endpoints as &quot;X-Cdn-Ssl=
-Uri.&quot;  You can find information on the API request call to list the U=
RLs associated with a Cloud Files container here: https://docs-ospc.rackspa=
ce.com/cloud-files/v1/cdn-api-reference/cdn-container-services-operations.h=
tml#list-metadata-for-cdn-enabled-container. =20
Alternatively, you may view the URLs from your cloud control panel: https:/=
/docs.rackspace.com/docs/secure-cloud-files-and-cdn-urls#http-or-https-acce=
ss-to-cloud-files-containers. =20

How can Rackspace help?
While our engineers are not in a position to directly support individual cu=
stomer configurations, we can provide guidance on general industry best pra=
ctices.
The required TLS 1.2 upgrade will most commonly affect customers connecting=
 to the API programmatically from their middleware application stack; the c=
hanges needed to upgrade for TLS 1.2 compatibility will need to be performe=
d by the customer&#x27;s application engineers.
Because TLS 1.2 was standardized in 2008, many systems which follow normal =
patching policies are likely already up to date and not in scope for this i=
ssue.  Nevertheless, we&#x27;ve included below some additional resources fo=
r systems that may require updates to comply with this updated standard.

Additional Resources:

Microsoft:=20
Engineers do not anticipate any issues for those customers utilizing techno=
logy newer than 2017 and current on patching. Consider the following as min=
imum compatible system baselines:=20
=E2=80=A2	.NET Framework: version 4.6.2 is the base version that supports T=
LS 1.2 (as of August 2016). Note: a few earlier variants do not appear to b=
e actively supported. For example, e.g., 4.5.1 and 4.5.2 can support TLS 1.=
2 with specified KBs (patches) installed
=E2=80=A2	Microsoft SQL Server 2016 and later supports TLS 1.2. Older SQL c=
lients may require special KBs (which were likely included in patching roll=
ups) to load
=E2=80=A2	Microsoft Windows Server 2012 and 2012 R2 will support TLS 1.2 wi=
th specified KBs that were released in June 2017. If you have patched since=
 that time, it&#x27;s likely the update was included in specified updates o=
r in patching rollups.
=E2=80=A2	Microsoft Windows Server 2016, 2019, and 2022: all support TLS 1.=
2

Azure:=20
Should be unaffected due to the use of newer technology. While there are po=
tential hurdles in Azure, these are unlikely and easy to fix (e.g., upgradi=
ng the .NET Framework used). Note: client VMs on Azure must also be up to d=
ate.

Linux:=20
Hosts will generally be up to date if they have recent patching, as all wil=
l be using the system-wide OpenSSL/GnuTLS libraries. If not, generally, the=
 solution is to update OpenSSL and/or GnuTLS packages. If the overall distr=
ibution version isn&#x27;t new enough to have recent packages, update that =
as well. Assuming the software version is recent enough, solutions may requ=
ire some configuration (e.g., the software can support TLS 1.2, but it&#x27=
;s just configured not to for whatever reason).

If an in-house/third-party package is doing TLS using its own libraries (or=
 a bespoke installation in its own directory, etc.), the team responsible f=
or that package should be engaged to investigate further.

https://ssl-config.mozilla.org/: This online tool can help with configurati=
on settings (it&#x27;s maintained by Mozilla, but it&#x27;s widely applicab=
le to many software packages, not just Firefox)

Sincerely,

Rackspace Technology
</pre>
<hr/></div></blockquote></font></td></tr></table></td></tr><tr><td colspan=
=3D"2" align=3D"left" bgcolor=3D"#FFFFFF"><font size=3D"2" face=3D"Helvetic=
a, Verdana, Arial, sans-serif" ><blockquote><div id=3D"messageSignature" st=
yle=3D"margin: 0 auto;text-align:left;">Best Regards,<br><a href=3D"http://=
www.rackspace.co.uk/" target=3D"_blank">The Rackspace Cloud</a><br><br><spa=
n style=3D"color:#333;">UK toll-free: 08000 546 345<br/>International: +44 =
(0) 208 734 4345<br/></span></div></blockquote></font> </td></tr><tr><td co=
lspan=3D"2" align=3D"left" bgcolor=3D"#FFFFFF"><font size=3D"2" face=3D"Hel=
vetica, Verdana, Arial, sans-serif"><blockquote><div id=3D"controlPanelmess=
ageId" style=3D"text-align:left;">Did you know that there is a Rackspace su=
pport hub? You can access Racker knowledge, discuss Rackspace products, and=
 quickly find your solution any time at <a href=3D"https://support.rackspac=
e.com" target=3D"_blank">support.rackspace.com</a>.</div></blockquote></fon=
t></td></tr></tbody></table></td></tr></tbody></table></body></html>