I guess it’d be the same as distributing any non binary. Use your C++ wrapper to decode the qmls. Before you load the main source.

I was wondering if this could be built in to the wrapper template provided by Qt creator.

xsacha wrote:

I guess it’d be the same as distributing any non binary. Use your C++ wrapper to decode the qmls. Before you load the main source.

Use a somewhat safe algorithm, though. And rename the file extensions.

tamhanna wrote:

xsacha wrote:

I guess it’d be the same as distributing any non binary. Use your C++ wrapper to decode the qmls. Before you load the main source.

Use a somewhat safe algorithm, though. And rename the file extensions.

Yes that option is always open. But if built in to Qt Creator everyone will benefit from it.

QtK wrote:

tamhanna wrote:

xsacha wrote:

I guess it’d be the same as distributing any non binary. Use your C++ wrapper to decode the qmls. Before you load the main source.

Use a somewhat safe algorithm, though. And rename the file extensions.

Yes that option is always open. But if built in to Qt Creator everyone will benefit from it.

But then it is also easier to break.

I wiull never forget the Astraware Superpatcher for Palm.- If every developer rolls his own scheme, well, not all of them will get hit. There is security in numbers here

tamhanna wrote:

QtK wrote:

tamhanna wrote:

xsacha wrote:

I guess it’d be the same as distributing any non binary. Use your C++ wrapper to decode the qmls. Before you load the main source.

Use a somewhat safe algorithm, though. And rename the file extensions.

Yes that option is always open. But if built in to Qt Creator everyone will benefit from it.

But then it is also easier to break.

I wiull never forget the Astraware Superpatcher for Palm.- If every developer rolls his own scheme, well, not all of them will get hit. There is security in numbers here

What if you can generate a binary out of qml files instead of just obfuscating it?

Welcome to .net – if the platform is large enough, someone will take the time to roll a decompiler.

As a quick solution just pack them as resource and apply some crypto on it. At loading simply uncrypto it and load as resource.
Or as quickest solution simply use as internal resources (inside binary).

Hi,
not sure if the internal resource is so save though…

Denis Kormalev wrote:

As a quick solution just pack them as resource and apply some crypto on it. At loading simply uncrypto it and load as resource. Or as quickest solution simply use as internal resources (inside binary).

Even I had thought of that but in that case I thought there might be a resource decompiler already present. But then this should work good as a quick solution. thank you.

tamhanna wrote:

Hi, not sure if the internal resource is so save though…

But still seems to be a quick and good workaround .

Well. If one is really paranoid, one could also do the internal resource plus the crypto algorithm ;)

Did a quick Google BTW – and found no decompiler…

If it doesn’t already exist, it will soon. Where there’s a will, there is a way.
Unfortunately it seems you’re stuck in a game of cat and mouse. However, if you make it too difficult, the cat may not bother to chase.

xsacha wrote:

If it doesn’t already exist, it will soon. Where there’s a will, there is a way. Unfortunately it seems you’re stuck in a game of cat and mouse. However, if you make it too difficult, the cat may not bother to chase.

Don’t challenge me.

It would seriously be a cool project . Qt Resource Decompiler.

The only issue I see is that every compiler aligns his C arrays differently into the binary. So such a decompiler would always be limited to one or two configurations at a time.