Automating Xamarin Protection with Dotfuscator

May 10, 2017 5736 Views Joseph Sewell

This week, all eyes of the software community will be fixed on Microsoft's Build conference. Microsoft and its partners are set to announce new technologies and lay out their vision for the future of software development. Recent years have seen the narrative take a decidedly cross-platform approach. Visual Studio Code gives developers tools to create what they want no matter their OS of choice. .NET Core extends the reach of the popular .NET Framework to Mac and Linux. Finally, Xamarin, which was acquired by Microsoft in 2016, lets app developers write their app once, then publish it for Android, iOS, and Windows devices.

As a Visual Studio 2017 Premier Launch Partner, PreEmptive Solutions is pleased to announce, as part of Microsoft Build 2017, a new way to integrate Dotfuscator's protection into Xamarin apps. This new Dotfuscator-Xamarin integration has a number of advantages:

Easy setup - Developers just download an MSBuild targets file and import it into their projects with a few simple property changes. No more need to define custom targets or copy files as a post-build step!
Deep pipeline integration - The new integration automatically puts Dotfuscator into the Xamarin build pipeline, protecting apps as they're built in Visual Studio or MSBuild. Developers don't have to worry about forgetting the protection step, since it's now included as part of the build.
Incremental builds - Don't waste time reapplying Dotfuscator's protection when your project hasn't changed. The integration is smart enough to know when a build is necessary, and when it can be skipped.
Automatic configuration - Get up and running quickly: the integration creates a Dotfuscator config file automatically, with sensible defaults for the project. Instructions are provided for further configuration, including a case study of how to discover which additional identifiers (if any) need to be excluded from renaming obfuscation.
Detailed instructions - We've detailed how to use the integration with a well-known Xamarin.Forms sample. Developers can see the practical application of these instructions through an included git repo, which walks through the process step-by-step.
All major project types supported - The integration supports projects targeting Android, iOS, and Universal Windows (UWP).
Proven protection strategy - The app is protected by Dotfuscator, the industry standard .NET obfuscation and protection tool.
Free to start - The integration works not only with the commercial Dotfuscator Professional Edition, but also with Dotfuscator Community Edition (CE), which is included with Visual Studio. Developers can use the integration to quickly discover the capabilities of Dotfuscator's protection.

To get started, see Integrating Dotfuscator's Protection into Your Xamarin Apps in Visual Studio. There you can read the step-by-step instructions, as well as download the necessary MSBuild targets file.

We plan to keep introducing features like this, to make the protection process easier and more accurate, for Xamarin and all other kinds of apps. Stay up-to-date with the latest Dotfuscator features by visiting the Dotfuscator Downloads page. For announcements and other information, keep an eye on our blog and follow our Twitter account, @PreEmptive.

Hardened Apps = Harder Target = Reduced Corporate Risk

There’s an app for that.

Apple’s (now trademarked) slogan is perhaps more telling than the company intended: Organizations rise and fall on the strength of applications — well-integrated, full-featured apps can help drive market success, while offerings more limited in scope and functionality may prove disastrous.

The sheer volume of both external and internal applications has also created a new challenge for companies: Risk management. Cybercriminals are both creating custom code and leveraging tools available on the Dark Web to compromise applications, steal corporate data and wreak network havoc.

GDPR fines were inevitable. Despite years of lead-up and months of warning before the legislation came into effect last May, many companies simply weren’t prepared for the complex (and evolving) nature of EU privacy expectations.

Now search giant Google is in the compliance law’s cross hairs: As noted by Bloomberg, Google has been assessed a $57 million fine because it “fails to adequately explain how it collects data to offer personalized advertising.” For some experts, the fine is a warning of things to come — companies must improve their data handling or face the consequences. For others, the penalties are a step too far with a purpose too vague.

The hard truth? No matter where opinions fall, GDPR fines are now out in full force — and your application could be next.

Hackers are winning. As noted by Information Age, data breach reports are up 75 percent over the last two years — while part of this increase is tied to emerging legislation and disclosure requirements, a quick look at tech headlines makes it clear that attackers are coming out ahead in the fight to keep corporate networks, applications and data secure.

But it’s not all bad news. Armed with knowledge of the current breach landscape — along with actionable insight to protect critical assets — organizations can start to even the score and put hackers on the defensive. Here’s what you need to know.

DashO 9.2 is available for immediate download and includes two powerful new controls:

1) Emulator Check, a new injectable control that

Detects when a hardened app is being executed on an emulator (even if that emulator is not rooted), and
Responds with the one or more pre-defined defenses and/or app-specific defenses – all in real-time.

Butter Knife is an annotation processing library that helps streamline boilerplate Java code in Android views. At compile time, Butter Knife annotations are processed to generate the relevant UI code to make views function properly.

When obfuscating applications that use Butter Knife, there are specific configuration patterns you should follow. The code that connects generated classes to their views uses runtime reflection under the hood. Because of this, the original name of the View is required.

When configuring DashO we need to:

Automating Xamarin Protection with Dotfuscator

Hardened Apps = Harder Target = Reduced Corporate Risk

GDPR Goes After Google — And Your App Could be Next

Data Breaches in 2019: Why the Hackers are Winning (And What You Can do About It)

Android Developers Gain Major App Security Boost with DashO v9.2

Protecting Java Android Applications that use Butter Knife

Latest Blog Posts

Hardened Apps = Harder Target = Reduced Corporate Risk

GDPR Goes After Google — And Your App Could be Next

Data Breaches in 2019: Why the Hackers are Winning (And What You Can do About It)

Android Developers Gain Major App Security Boost with DashO v9.2

Protecting Java Android Applications that use Butter Knife

Twitter

App Protection Blogs

Automating Xamarin Protection with Dotfuscator

Latest Blog Posts

Twitter