Hackers Exploiting Fake Video Conferencing Apps to Target Web3 Professionals
December 9, 2024
Fake Hardhat npm Packages Exploit Ethereum Developers
January 8, 2025
Microsoft has announced an urgent change affecting the distribution of .NET installers and archives, necessitating immediate action from developers to prevent service disruptions.
Background
Historically, Microsoft has hosted certain .NET binaries and installers on Azure Content Delivery Network (CDN) domains ending in .azureedge.net, specifically dotnetcli.azureedge.net and dotnetbuilds.azureedge.net, which are managed by Edgio.
After Edgio’s bankruptcy, Akamai purchased a few of its assets in December 2024.
Consequently, the Edgio platform is scheduled to cease operations on January 15, 2025.
Immediate Actions Required
To ensure continuity, Microsoft is migrating these resources to Azure Front Door CDNs.
Developers must take the following steps before January 7, 2025:
- Update References: Scan your codebases for any mentions of azureedge.net and modify them as follows:
- Change dotnetcli.azureedge.net to builds.dotnet.microsoft.com.
- Change dotnetcli.blob.core.windows.net to builds.dotnet.microsoft.com.
- Automatic Migration: Microsoft will automatically migrate workloads by January 7, 2025.
- Note: Automatic migration is not possible for endpoints with *.vo.msecnd.net domains.
- Custom CDN Providers: If you plan to migrate to Akamai or another CDN provider, set the Feature Flag DoNotForceMigrateEdgioCDNProfiles before January 7, 2025, to prevent automatic migration to Azure Front Door.
Important Dates
- January 3, 2025: Configuration changes to Azure CDN by Edgio profiles will be frozen.
- January 7, 2025: Deadline for automatic migration to Azure Front Door.
- January 14, 2025: The deadline for finishing the move to a different CDN
- January 15, 2025: Edgio platform ceases operations.
Security Considerations
To mitigate security risks associated with the potential acquisition of the azureedge.net domain by malicious actors, Microsoft has taken control of the domain.
However, the old domain names cannot be used to resolve to the new servers.
Recommendations
- Adopt Custom Domains: To enhance flexibility and reduce single points of failure, it’s advisable to implement custom domains promptly.
- Monitor Services: Ensure that your services are functioning correctly post-migration and watch for any downtime or disruptions.
By adhering to these guidelines, developers can maintain uninterrupted access to .NET resources and uphold the security and reliability of their applications.
