Packetizer Forums

I can't say whether the USB Pen Drive utility encrypts files using the same file format or not. One way to test, if you think you know the password, is to rename the file to have an extension ".aes" and then try to decrypt the file. If it is not a valid AES Crypt file, it will tell you so....

You might also want to look at these two presentations I prepared some time ago: Overview of H.323 H.323 Protocol Overview I would read them in that order. The first one is a little higher-level, but has flows and content not in the second deck. The second deck is what I use when I provide training ...

Do you want to do a call transfer? That is, H.450.2?

The "insurance.aes256" may very well contain random data. There's no way for me to tell. As for the file format, there is no standard file format for AES-encrypted files. OpenSSL has its own, WinZIP has its own, and we introduced our own. Since AES Crypt is focused strictly on encrypting f...

We recently saw a huge spike in traffic to the AES Crypt web site and the number of downloads of the program increased significantly. While we're certainly happy to see people take an interest in AES encryption technology and AES Crypt, in particular, what we discovered as we tried to find out why t...

Early media / late media is a term usually associated with SIP, not H.323. In any case, some devices support Fast Connect (aka, fastStart) and some do not. Some support H.245 tunneling and some do not. One does not have to support either of them, though, which is why we see devices doing different t...

That's really a question that would likely have to be directed to Avaya, but I'm sure there is a partner program. From what I recall, Avaya sometimes used H.323 Annex F. They also did something similar to H.460.6, but perhaps the implementation pre-dated the specification. In any case, if the desire...

The only documentation is what's posted to the AES Crypt web site for each version (Windows, Linux, Mac, Java). Using the program is really simple, though admittedly the documentation is fairly light. The program is free to use in any environment. There are no costs: it's free software. However, the...

Part of the code is under the GNU license, so that makes all of the code (effectively) under the GNU license.

What we will likely do at some point is replace the GNU code so it has an even less restrictive license, but for now that's the license that constrains it.

It sounds like this is not related to AES Crypt, but perhaps Windows encryption software? Do you know what the files were encrypted with?

If they're encrypted using AES Crypt, the only way to recover the files is to have the password.