[AxCrypt SupportModerator]

Hello,

Please try version 2.1.1516 which is just released.

[AxCrypt SupportModerator]

Hello,

Please try version 2.1.1516 which is just released.

[AxCrypt SupportModerator]

Thank you, Eduardo!

[AxCrypt SupportModerator]

Hello,

The size difference is just due to the fact that the small one is without ILMerge, and the larger one after (i.e. includes all assemblies).

The language problem is different though, when we have time we’ll try to figure out why our builds produce working binaries for all languages, while community builds apparently do not. They should.

[AxCrypt SupportModerator]

Hello all,

There’s nothing magic about our build. We do not use anything (except of course code signing certificates) that is not in the public repository.

Our build-server command line to build the stand-alone version is essentially (minus some stuff for our versioning since we inject our build number into the assembly version and naming etc):

msbuild AxCrypt.NET.sln /p:Configuration=Release

This should produce ‘AxCrypt.exe’ with all the required culture satellite assemblies merged in and workable.

That’s it. Please note that we won’t actually do the ILMerge stuff for Debug builds – but if you wish you can change the .targets files for that.

[AxCrypt SupportModerator]

Hello Eduardo,

May I ask what it is you’re trying to achieve? Is it something we could put on the to-do list for the main distribution (we do have a portable / standalone build for download, as you know so I’m not sure why you can’t just use our build mechanism)?

[AxCrypt SupportModerator]

Thank you – we’re looking into it! See https://bitbucket.org/axantum/axcrypt-net/issues/327/when-opening-an-encrypted-txt-file-with .

[AxCrypt SupportModerator]

Hello Sylvester,

Also, in the main UI there is a (sort of) progress bar. It doesn’t reflect progress very well, but it does show activity and it allows cancelling as well.

[AxCrypt SupportModerator]

Hello Carl,

Sorry, you don’t! Read https://forum.axcrypt.net/blog/use-of-different-passwords/ for more information about why we did it this way.

[AxCrypt SupportModerator]

Thanks Iain!

[AxCrypt SupportModerator]

Hello Neutron,

Thanks for reporting. We’ll look into this. I’ve filed a bug report for it here: https://bitbucket.org/axantum/axcrypt-net/issues/327/when-opening-an-encrypted-txt-file-with .

If you have more information on the issue, please let us know here or comment on the issue.

[AxCrypt SupportModerator]

Dear Jorge,

Happy to hear it, and good luck!

[AxCrypt SupportModerator]

Hello Eduardo,

Our pre-built portable executable includes the language satellite assemblies, and allows language switching. Check the file ‘Axantum.targets’ for hints on how to do it. Unless of course you’re fine with using ours!

As for “chosen not to use embedded dependencies and instead rely upon multiple DLLs which are in directories: de, es, fr, it, ko, nl, pt, ru, sv, tr” – well, that’s just how it works by default.

And, yes, it would be awesome if someone would contribute a way to build a single executable using embedded resouce assemblies with the AssemblyResolve event instead of ILMerge. There’s an issue waiting to be resolved for that: https://bitbucket.org/axantum/axcrypt-net/issues/14/change-single-exe-strategy . We did a proof of concept for that with another software, a portable client version of the password manager and it works fine.

[AxCrypt SupportModerator]

Hello ibrahim,

Unfortunately, if you do not know the password for an AxCrypt-encrypted file you cannot open it, even if you can sign in to the account. This is by design, it’s just this situation that AxCrypt is made for and it works like this even if you actually are the original owner of the file.

Please check the FAQ at http://www.axcrypt.net/support/faq/ for more information.

[AxCrypt SupportModerator]

Hello Helga (and thank you Dominik!),

Thank you for the screen shot! It’s amazing how much one can tell from a single screen shot ;-)

The file your friend sent to you is encrypted with Version 2, but your friend has not used the key sharing feature and shared the access with you before sending it.

As Dominik says, your friend must add you to the list of key sharing recipients and then send the file again.

The key sharing function embeds the shared key into the file. The file must thus first be key shared with the recipient, then sent or file shared. Please note that AxCrypt does not share or send the actual file. To see a quick instructional video explaining how to use key sharing, please view https://www.youtube.com/watch?v=9z3KOZD-Yks .

[Author]

Posts