Packetizer Forums

We don't have that feature in AES Crypt. It would be useful, but not something we plan to implement. Of course, if there are folks interested to contribute this to the open source project, we would welcome it.

There isn't by default. If you modify the source code, of course it's doable. The program is written intentionally to delete the files since they are not supposed to be trusted.

This error message means that the file has been corrupted. AES Crypt not only encrypts the file, but it also produces something called a "Message Authentication Code" (MAC) and appends that to the end of the file. If the MAC does not validate correctly, then AES Crypt assumes the file has ...

I created a file with exactly 4000000 bytes and then I encrypted it. Here are the results on my Linux machine (Intel 32-bit): $ time aescrypt -e -p test testfile real 0m0.312s user 0m0.242s sys 0m0.028s So, that is considerably faster than 8s. I'm not sure why it's taking so long on the ARM processo...

If you installed the Windows executable, the you should uninstall it from the Windows Control Panel under "Programs". In the list of installed programs, you will find "AES Crypt". Simply select that and uninstall it.

It's called "AESCrypt.dll" and it's in the directory where AES Crypt gets installed. You can get the entire source code and change it as necessary to make it useful in your environment. Just download the source from www.aescrypt.com.

AES Crypt uses 256-bit encryption presently.

Usually, H.323 endpoints are provisioned with the address of a Gatekeeper. Usually, it's provisioned as the IP address, not a domain name. However, it is possible to provision an endpoint with a domain name. As an example, if you create an account at h323.net and download the Spranto soft client, yo...

On the topic of H.323 vs SIP...after reviewing the site I have a couple of questions. I will be presenting benfits for video conferencing through SIP as well as how our company would benefit by migration from H.323 to SIP. It seems that after reading Packetizers "H.323 vs. SIP" article th...

By default, H.323 uses port 1718 (multicast) and 1719 (unicast) for RAS traffic. However, those are just the recommended default values. If two communicating devices agree, they could use different addresses. H.323 Annex O describes how to use DNS with H.323 systems. So, if an endpoint or Gatekeeper...