Packetizer Forums

Re: Shouldn't encrypted files be bigger than the original on

2012-05-15T14:27:16Z

The files produced by AES Crypt are definitely larger, usually more than 132 bytes or so.

Re: how long can a password be?

2012-05-15T14:25:10Z

The password length should be the same. However, if you have a good random password, you do not need more than 256 bits for the password, since everything is no stronger than 256 bits. We have a password generator that uses a subset of the ASCII character chart to generate passwords. Since it does not use all of the bits in a byte, one needs more characters. Per our calculations, 65 characters would be more than enough. See this page:
http://www.packetizer.com/security/pwgen/

Shouldn't encrypted files be bigger than the original ones?

2012-05-15T05:56:54Z

I'm not an expert, but AFAIK encrypted files should be bigger than the original ones.

But I tried to encrypt a .zip and a .jpeg, and both created a .aes file of the same size.

Is the real size being hidden or what?

Re: how long can a password be?

2012-05-14T11:24:29Z

Is this for the graphical version or the command-line-terminal version?

Re: H.323 Plus and FFmpeg compatibility

2012-05-13T07:15:31Z

Hi,

I'm compiling the codecs ffrom H323Plus CVS with ffmpeg 0.9 on Linux and that seems to work fine.

Jan

H.323 Plus and FFmpeg compatibility

2012-05-12T20:41:51Z

I wanted to reach the author regarding the compatibility issues with H.323 Plus (1.24.0) and older FFmpeg releases (.e.g. 0.7 branch) never mind something fairly new-ish like the 0.10 branch. H.323 Plus is the only project left in the OpenBSD ports tree I'm having issues with trying to build with newer FFmpeg. We've had some minimalist patching to get H.323 Plus to build and run with FFmpeg 0.7 snapshots but as the API has changed even further between 0.7 and 0.8/0.9 and 0.10 snapshots we're using now this is causing further issues trying to build H.323 Plus. I see in the CVS repo you have made some sort of attempt at dealing with this for some parts of H.323 Plus code but then later reverted it. Even with that there was still the issue of fixing the autoconf script as well. Can you comment on when we might see a new release of H.323 Plus that will work with newer FFmpeg releases "out of the box"?

Re: invalid Signature error

2012-05-11T09:34:01Z

The "invalid signature" error is an unfortunate error message. What it means is that the 'AES' header was not observed at the start of the file. It's a basic sanity check to ensure that the file format is known before attempting the decryption process. A better message would be "invalid AES file". I'll add that to the to-do list.

invalid Signature error

2012-05-10T13:41:17Z

I tried to open a document that was encrypted but I am getting the error " invalid signature "..I know the password is correct because I encrypted it myself using (wapwolf from my dropbox). What is the problem? Can anyone help us?

Re: AES Decryption

2012-05-08T14:28:31Z

AESQuest wrote:
I have written down a Formula I would like to know if this will decrypt AES?

I've seen a lot of math over the years, but I can't read this. I cannot tell what you're proposing here. Can you present this in a way that is more readable? Perhaps others can read it, but I cannot.

AES Decryption

2012-05-08T10:50:10Z

I have written down a Formula I would like to know if this will decrypt AES?

The O after the Y is a (sigma sign)

Re: how long can a password be?

2012-05-06T20:18:37Z

I would need to look at the source code, but it is either 1024 bytes or 1024 Unicode characters. In any case, it is far bigger than necessary.

how long can a password be?

2012-05-06T15:02:38Z

For the Windows and Mac versions, how long can a password be? Thanks.

Re: AESCrypt for Android

2012-04-23T11:37:36Z

Because using a fixed value (like DEFAULT_MAC) is not desirable, in generateIv1() I replaced
"mac = DEFAULT_MAC;" with
"mac = generateRandomBytes(8);"

I incorporated AESCrypt.java into an Android program that I wrote for myself to decrypt small (<1MB) text files and speed has not been a problem for me.

Re: AESCrypt for Android

2012-04-19T16:28:24Z

The getHardwareAddress() call is only to help in the creation of a random initialization vector. It is good to have something random, but use of a MAC address is not random. Use of a fixed value is worse. The function attempts to make it random by also using the current time and then hashing the MAC and time. You could replace the call to get the MAC address with a call to Math.random()*256 or similar to get a random byte between 0 and 255. Do that 8 times (to fill up the IV array), with the time consuming the other 8 octets. Pseudo-random number generators are not ideal, but still better than a fixed value. Of course, hash it to make it even more obscure. (Note: the IV does not have to be random and it's certainly not secret. It's published in the clear. That said, we do not want to use the same IV all the time, either, as this would help one launch an attack knowing certain fixed values and results.)

As for performance, I'm not sure. Can you identify what is consuming the CPU? If it's the call to Java's AES routines, there is nothing we could do. If it is in the AES Crypt Java code, then we could address that.

AESCrypt for Android

2012-04-19T11:23:16Z

I tried AESCrypt.java in my Android application. NetworkInterface.getHardwareAddress() call does not exist in the Android Java library, so I have commented that code and use DEFAULT_MAC as mac. It works fine in my application. I have passed version 2 in encrypt function.

But in this forum there is a question about "Android Version?". In that topic it is written that this AESCrypt is not for android application.
If I use this way in android application then is there any chances of problem?

And currently it is very slow to encrypt and decrypt the file in android ?

Any help....

Re: Memory Leak in encrypt method on Android

2012-04-16T12:03:16Z

Have you tried creating the ByteArrayOutputStream within the for loop?
i.e. put "ByteArrayOutputStream baos = new ByteArrayOutputStream(ONE_MEGABYTE+ONE_KILOBYTE);" inside the for loop and replace the "baos(reset)" in the for loop with "baos(close)".

megaco decoding with opal

2012-04-11T10:09:00Z

i all,

I am trying to decode H248 megaco messages using opal library. I convert the payload (bytes after udp header) to PPer_Stream and give that to H248Message::Decode() method, but I dont get any meaningful output.

Here's how I use it:

PPER_Stream pstr((const BYTE *) pl, pllen);
H248_Message msg;

msg.Decode(pstr);
msg.PrintOn(cout);

Output:
{
version = 33
mId = domainName {
name = " [10.10.100.4]:2944 T=12449096{C=${A=T00100000003"
portNumber = 12338
}
messageBody = messageError {
errorCode = 12336
}
}

and payload starts like this:
"!/1 [10.10.100.4]:2944 T=12449096{C=${A=T0010000000302100005{E=12070391{......."

I also tried H248_MegacoMessage, but didnt help.

Any1 else tried decoding Megaco messages successfully?

Re: help with SIP compatability

2012-04-06T19:54:04Z

aaron wrote:
Thanks for the fast reply! This really helps clear up how the VoIP system will work. I think this will help make the sale.
Thanks again!

Just curious if you were able to make the sale?

Let us know!

Thanks,

-Jim

filtrar h323 en wireshark

2012-04-04T18:11:48Z

Hola, conoces como filtrar una llamada en h323 que contenga los protocolos h325 y h245 en wireshark

saludes

Re: AES Crypt key generation

2012-04-04T15:10:44Z

Getting access to the master key (K-2) is dependent on the password (and, thus, K-1). If one were to somehow guess at K-2 should not bother you. The fact that K-2 is used to encrypt the file does not compromise security, assuming one has a secure system with a reasonably good RNG; there's simply no way to guess at K-2. Given that most users do not use strong passwords, K-2 is definitely the more secure key. With a strong password, K-2 is equally strong. It's perhaps worth noting that AES Crypt was not the first encryption tool to use this approach. As one example, PGP did the same thing:
http://en.wikipedia.org/wiki/Pretty_Good_Privacy#Confidentiality

PGP use a public/private key pair as a "K-1" where we use a symmetric key K-1. However, PGP's "session key" is more-or-less the same as AES Crypt's K-2. In both PGP and AES Crypt, "K-2" is encrypted using "K-1".

With your use of hashing functions (SHA-512 and Whirlpool) to create a key, you should be mindful of the fact that hashing functions are not encryption functions. They just take input and create something that looks random. However, the output of a hash function is definitely not random. Given random input, though, the output random. Given predictable input, the output is predictable. So, you can certainly use the hashing functions as you propose to generate a K-1 or K-2, but the input to those functions needs to be random.

Re: AES Crypt key generation

2012-04-04T08:58:23Z

Yes that seemed to bother me a bit! Master key should be dependent somehow on the password. Maybe instead of using SHA-256 you can use SHA-512 derived from password and random salt (8192 times ofcourse) and cut the 512 bit output into 2 256 bit keys K-1 and K-2 in future designs maybe! That way the master key K-2 is dependent on the password and even if the OS RNG is flawed or doesn't have enough entropy (like mobiles or servers), we still can add entropy from the password...

PS: I am making a software just for fun that uses two hash algorithms SHA-512 and Whirlpool. The hashes are then XORed to each other to produce K-1 and K-2! Will that compromise security?

Re: AES Crypt key generation

2012-04-04T03:42:20Z

AES Crypt uses two different keys. One key is derived from the user's password (call that K-1). In order to perform the encryption, we also need an initialization vector (call it IV-1), a value that also needs to be randomly generated in order to improve security. We then generate a second key (K-2) and initialization vector (IV-2).

We take K-1 and IV-1 and use those to encrypt K-2 and IV-2. Those are stored in the file, which you have observed. Given a strong password (and coupled with the way in which we derive K-1), this should be well protected.

We then take K-2 and IV-2 and encrypt the file.

So, to be able to break AES Crypt, one needs to be able to get K-2 and IV-2. This should be virtually impossible unless there is a weakness in the random number generation. Likewise, breaking K-1 and K-2 in order to then decrypt the file should be virtually impossible, assuming one used a reasonably strong password. Since we use SHA-256 as a part of the K-1 derivation, one can easily argue that it also depends on the strength of SHA-256. We're not aware of any weaknesses in that algorithm, and certainly not aware of anything that can be observed from 8192 rounds of SHA-256.

In short, I see nothing insecure about storing K-2 and IV-2 in encrypted form in the file encrypted using another 256-bit key that is equally strong. If that key can be so easily obtained, then it should be equally as easy to decrypt the entire file had we used K-1 and IV-1. So, I think we can dismiss that as a flaw.

Now, to your point about the random number generator...

Encryption absolutely requires a strong random number generator (RNG). In that, there is no doubt. You are correct that many systems do not have enough entropy to generator too many random numbers, which is another reason why we hash the numbers we do get with SHA-256. The objective is to try to offset any weaknesses in the RNG by hashing the values with at least some numbers that are random, this avoiding the possibility that we have sequences of digits in the key of IV that are characteristic of a particular RNG implementation. We do assume that the operating system can generate some numbers that might be viewed as cryptographically strong, but we cannot introduce a better random number generator in software. The underlying operating system absolutely is the best place to generate and maintain entropy data. Thus, we rely on /dev/random and the Windows crypto APIs.

The biggest weakness in this approach, we believe, is that the RNG on a system could be compromised. Perhaps it generates a fixed, known sequence of integers. If it did that, then that would mean I could fairly easily determine IV-2 and K-2, the most important data that is securing the file. After all, if I knew the sequence in which numbers would be generated, then I would know exactly what the values for K-2 and IV-2 are. I would not need to know K-1 or IV-1.

The issue here, though, is that this weakness is the result of the system being compromised. If somebody has a system that has been compromised, then absolutely no security software is going to protect you. You may have a stealth random number generator and and use a perfectly random 256-bit key. But, all I would need to do is get access to your key. I could do that by logging your keystrokes or even reading through memory of an executing program.

So, while we do not rely on Microsoft or other third parties to perform the encryption function, we do rely on the operating system to be a source of random numbers. You may classify that as a weakness and I wish we had a better source of random numbers, too. But the fact remains that if the operating system cannot be trusted to provide random numbers, then it cannot be trusted, period. There is nothing we can do to address a system that has been compromised and that's really the only concern I have with the approach we take.

AES Crypt key generation

2012-04-03T12:13:37Z

There seem to be 2 flaws in design. First I don't know why the encrypted key needs to be placed in the encrypted file as well. Like TrueCrypt that never stores a hash of password or the encrypted key.

Secondly, key is randomly created can be a problem which means the key is not actually dependent on the password but the entropy of the system of that time which can be severely compromised and the Windows CryptoAPI is not even open source unlike dev/random, urandom in Linux. Can you explain it to me why you chose this particular design of AES Crypt. Thanks.

Re: ptlib/make/lib.mak no longer available

2012-04-01T13:31:10Z

I traced back to PTLib r27227, the last PTLib SVN revision below ptlib/make/lib.mak file gets removed. I created a patch file for src/Makefile file to remove lib.mak dependency as shown below.

--- a/src/Makefile

+++ b/src/Makefile

@@ -348,8 +348,6 @@ SYSLIBS        += -l$(PTLIB_BASE)$(LIB_T

 LIB_BASENAME=$(OH323_BASE)

 LIB_FILENAME=$(OH323_FILE)

 

-include $(PTLIBDIR)/make/lib.mak

-

 ####################################################

If I applied the above patch, the cross compilation will not be able to compile to produce any libh323.* library as shown below:

make -j1 -C /opt/openwrt-svn-trunk/build_dir/target-mipsel_uClibc-0.9.33/h323plus_cvs DESTDIR="/opt/openwrt-svn-trunk/build_dir/target-mipsel_uClibc-0.9.33/h323plus_cvs/ipkg-install" opt install

make[3]: Entering directory `/opt/openwrt-svn-trunk/build_dir/target-mipsel_uClibc-0.9.33/h323plus_cvs'

make[4]: Entering directory `/opt/openwrt-svn-trunk/build_dir/target-mipsel_uClibc-0.9.33/h323plus_cvs'

make[4]: Leaving directory `/opt/openwrt-svn-trunk/build_dir/target-mipsel_uClibc-0.9.33/h323plus_cvs'

make -C src opt

make[4]: Entering directory `/opt/openwrt-svn-trunk/build_dir/target-mipsel_uClibc-0.9.33/h323plus_cvs/src'

make[5]: Entering directory `/opt/openwrt-svn-trunk/build_dir/target-mipsel_uClibc-0.9.33/h323plus_cvs/src'

make[5]: *** No rule to make target `/opt/openwrt-svn-trunk/build_dir/target-mipsel_uClibc-0.9.33/h323plus_cvs/lib/libh323__.so', needed by `default_target'.  Stop.

make[5]: Leaving directory `/opt/openwrt-svn-trunk/build_dir/target-mipsel_uClibc-0.9.33/h323plus_cvs/src'

make[4]: *** [opt] Error 2

make[4]: Leaving directory `/opt/openwrt-svn-trunk/build_dir/target-mipsel_uClibc-0.9.33/h323plus_cvs/src'

make[3]: *** [opt] Error 2

make[3]: Leaving directory `/opt/openwrt-svn-trunk/build_dir/target-mipsel_uClibc-0.9.33/h323plus_cvs'

make[2]: *** [/opt/openwrt-svn-trunk/build_dir/target-mipsel_uClibc-0.9.33/h323plus_cvs/.built] Error 2

make[2]: Leaving directory `/opt/OpenWRT/feeds/packages/libs/h323plus_cvs'

make[1]: *** [package/feeds/local/h323plus_cvs/compile] Error 2

make[1]: Leaving directory `/opt/openwrt-svn-trunk'

make: *** [package/h323plus_cvs/compile] Error 2

ptlib/make/lib.mak no longer available

2012-03-27T18:32:41Z

Looks like H323Plus is now not cross compilable with the latest PTLib. I just did an update to my local PTLib, Opal, and H323Plus with the latest revision. When I tried to cross compile H323Plus, it spitted out an error message saying No such file or directory for ptlib/make/lib.mak as seen below.

make[2]: Entering directory `/opt/OpenWRT/feeds/packages/libs/h323plus_cvs'

. /opt/openwrt-svn-trunk/include/shell.sh; bzcat /opt/openwrt-svn-trunk/dl/h323plus_cvs-20120327.tar.bz2 | /bin/tar -C /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/.. -xf - --strip-components=1 -C /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs 

rm -rf /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/patches; mkdir -p /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/patches

touch /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/.quilt_used

touch /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/.prepared

if [ -s "/opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/patches/series" ]; then (cd "/opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs"; if quilt --quiltrc=- next >/dev/null 2>&1; then quilt --quiltrc=- push -a; else quilt --quiltrc=- top >/dev/null 2>&1; fi ); fi

touch "/opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/.quilt_checked"

#(cd /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs; [ -e configure ] && rm configure)

#(cd /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs; /opt/openwrt-svn-trunk/staging_dir/host/bin/aclocal.real --force)

#(cd /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs; /opt/openwrt-svn-trunk/staging_dir/host/bin/autoconf -f)

(cd /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/./; if [ -x ./configure ]; then /usr/bin/find /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/ -name config.guess | xargs -r chmod u+w; /usr/bin/find /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/ -name config.guess | xargs -r -n1 cp /opt/openwrt-svn-trunk/scripts/config.guess; /usr/bin/find /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/ -name config.sub | xargs -r chmod u+w; /usr/bin/find /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/ -name config.sub | xargs -r -n1 cp /opt/openwrt-svn-trunk/scripts/config.sub; AR=arm-openwrt-linux-uclibcgnueabi-ar AS="arm-openwrt-linux-uclibcgnueabi-gcc -c -Os -pipe -march=armv5te -mtune=xscale -fno-caller-saves -fhonour-copts -Wno-error=unused-but-set-variable -msoft-float" LD=arm-openwrt-linux-uclibcgnueabi-ld NM=arm-openwrt-linux-uclibcgnueabi-nm CC="arm-openwrt-linux-uclibcgnueabi-gcc" GCC="arm-openwrt-linux-uclibcgnueabi-gcc" CXX="arm-openwrt-linux-uclibcgnueabi-g++" RANLIB=arm-openwrt-linux-uclibcgnueabi-ranlib STRIP=arm-openwrt-linux-uclibcgnueabi-strip OBJCOPY=arm-openwrt-linux-uclibcgnueabi-objcopy OBJDUMP=arm-openwrt-linux-uclibcgnueabi-objdump SIZE=arm-openwrt-linux-uclibcgnueabi-size CFLAGS="-Os -pipe -march=armv5te -mtune=xscale -fno-caller-saves -fhonour-copts -Wno-error=unused-but-set-variable -msoft-float " CXXFLAGS="-Os -pipe -march=armv5te -mtune=xscale -fno-caller-saves -fhonour-copts -Wno-error=unused-but-set-variable -msoft-float " CPPFLAGS="-I/opt/openwrt-svn-trunk/staging_dir/target-arm_v5te_uClibc-0.9.33_eabi/usr/include -I/opt/openwrt-svn-trunk/staging_dir/target-arm_v5te_uClibc-0.9.33_eabi/include -I/opt/openwrt-svn-trunk/staging_dir/toolchain-arm_v5te_gcc-4.6-linaro_uClibc-0.9.33_eabi/usr/include -I/opt/openwrt-svn-trunk/staging_dir/toolchain-arm_v5te_gcc-4.6-linaro_uClibc-0.9.33_eabi/include " LDFLAGS="-L/opt/openwrt-svn-trunk/staging_dir/target-arm_v5te_uClibc-0.9.33_eabi/usr/lib -L/opt/openwrt-svn-trunk/staging_dir/target-arm_v5te_uClibc-0.9.33_eabi/lib -L/opt/openwrt-svn-trunk/staging_dir/toolchain-arm_v5te_gcc-4.6-linaro_uClibc-0.9.33_eabi/usr/lib -L/opt/openwrt-svn-trunk/staging_dir/toolchain-arm_v5te_gcc-4.6-linaro_uClibc-0.9.33_eabi/lib "   ./configure --target=arm-openwrt-linux --host=arm-openwrt-linux --build=x86_64-suse-linux --program-prefix="" --program-suffix="" --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --libexecdir=/usr/lib --sysconfdir=/etc --datadir=/usr/share --localstatedir=/var --mandir=/usr/man --infodir=/usr/info --disable-nls   --host=arm-openwrt-linux --build=x86_64-suse-linux --prefix="/usr" --enable-asntracing --enable-audio --disable-aec --enable-file --enable-gnugk --enable-h224 --enable-h230 --enable-h235 --enable-h239 --enable-h248 --enable-h249 --enable-h341 --enable-h350 --enable-h450 --enable-h46017 --enable-h46018 --enable-h46019m --disable-h46023 --enable-h4609 --enable-h460 --enable-h460p --enable-h501 --enable-option-checking --enable-t120 --enable-t38 --enable-versioncheck --enable-video --enable-capi --enable-celt --enable-default-to-full-capabilties --enable-h264 --enable-ixj --enable-libavcodec --enable-libavcodec-stackalign-hack --enable-localgsm --enable-localilbc --enable-localspeex --enable-sbc --enable-spandsp --enable-theora --enable-vpb --enable-x264 --enable-x264-link-static  ; fi; )

configure: WARNING: unrecognized options: --disable-nls, --enable-capi, --enable-celt, --enable-default-to-full-capabilties, --enable-h264, --enable-ixj, --enable-libavcodec, --enable-libavcodec-stackalign-hack, --enable-localgsm, --enable-localilbc, --enable-localspeex, --enable-sbc, --enable-spandsp, --enable-theora, --enable-vpb, --enable-x264, --enable-x264-link-static

configure: loading site script /opt/openwrt-svn-trunk/include/site/arm-openwrt-linux-uclibcgnueabi

checking whether the C++ compiler works... yes

checking for C++ compiler default output file name... a.out

checking for suffix of executables... 

checking whether we are cross compiling... yes

checking for suffix of object files... o

checking whether we are using the GNU C++ compiler... yes

checking whether arm-openwrt-linux-uclibcgnueabi-g++ accepts -g... yes

checking for arm-openwrt-linux-gcc... arm-openwrt-linux-uclibcgnueabi-gcc

checking whether we are using the GNU C compiler... yes

checking whether arm-openwrt-linux-uclibcgnueabi-gcc accepts -g... yes

checking for arm-openwrt-linux-uclibcgnueabi-gcc option to accept ISO C89... none needed

checking how to run the C preprocessor... arm-openwrt-linux-uclibcgnueabi-gcc -E

checking for grep that handles long lines and -e... /usr/bin/grep

checking for egrep... /usr/bin/grep -E

checking for ANSI C header files... yes

OpenH323 version is 1.24.1

checking for sys/types.h... yes

checking for sys/stat.h... yes

checking for stdlib.h... yes

checking for string.h... yes

checking for memory.h... yes

checking for strings.h... yes

checking for inttypes.h... yes

checking for stdint.h... yes

checking for unistd.h... yes

checking /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/ptlib2_svn/version.h usability... yes

checking /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/ptlib2_svn/version.h presence... yes

checking for /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/ptlib2_svn/version.h... yes

PTLib prefix set to.... /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/ptlib2_svn

checking Checking PTLib version 2.11.2... ok

configure: Disabling H.460.23/.24

configure: Enabling T.38

configure: AEC disabled

checking for a BSD-compatible install... /usr/bin/install -c

configure: creating ./config.status

config.status: creating openh323u.mak

config.status: creating Makefile

config.status: creating include/openh323buildopts.h

=== configuring in plugins (/opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/plugins)

configure: running /bin/sh ./configure --disable-option-checking '--prefix=/usr'  '--target=arm-openwrt-linux' '--program-prefix=' '--program-suffix=' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--libexecdir=/usr/lib' '--sysconfdir=/etc' '--datadir=/usr/share' '--localstatedir=/var' '--mandir=/usr/man' '--infodir=/usr/info' '--disable-nls' '--host=arm-openwrt-linux' '--build=x86_64-suse-linux' '--enable-asntracing' '--enable-audio' '--disable-aec' '--enable-file' '--enable-gnugk' '--enable-h224' '--enable-h230' '--enable-h235' '--enable-h239' '--enable-h248' '--enable-h249' '--enable-h341' '--enable-h350' '--enable-h450' '--enable-h46017' '--enable-h46018' '--enable-h46019m' '--disable-h46023' '--enable-h4609' '--enable-h460' '--enable-h460p' '--enable-h501' '--enable-option-checking' '--enable-t120' '--enable-t38' '--enable-versioncheck' '--enable-video' '--enable-capi' '--enable-celt' '--enable-default-to-full-capabilties' '--enable-h264' '--enable-ixj' '--enable-libavcodec' '--enable-libavcodec-stackalign-hack' '--enable-localgsm' '--enable-localilbc' '--enable-localspeex' '--enable-sbc' '--enable-spandsp' '--enable-theora' '--enable-vpb' '--enable-x264' '--enable-x264-link-static' 'build_alias=x86_64-suse-linux' 'host_alias=arm-openwrt-linux' 'target_alias=arm-openwrt-linux' 'CXX=arm-openwrt-linux-uclibcgnueabi-g++' 'CXXFLAGS=-Os -pipe -march=armv5te -mtune=xscale -fno-caller-saves -fhonour-copts -Wno-error=unused-but-set-variable -msoft-float ' 'LDFLAGS=-L/opt/openwrt-svn-trunk/staging_dir/target-arm_v5te_uClibc-0.9.33_eabi/usr/lib -L/opt/openwrt-svn-trunk/staging_dir/target-arm_v5te_uClibc-0.9.33_eabi/lib -L/opt/openwrt-svn-trunk/staging_dir/toolchain-arm_v5te_gcc-4.6-linaro_uClibc-0.9.33_eabi/usr/lib -L/opt/openwrt-svn-trunk/staging_dir/toolchain-arm_v5te_gcc-4.6-linaro_uClibc-0.9.33_eabi/lib ' 'CPPFLAGS=-I/opt/openwrt-svn-trunk/staging_dir/target-arm_v5te_uClibc-0.9.33_eabi/usr/include -I/opt/openwrt-svn-trunk/staging_dir/target-arm_v5te_uClibc-0.9.33_eabi/include -I/opt/openwrt-svn-trunk/staging_dir/toolchain-arm_v5te_gcc-4.6-linaro_uClibc-0.9.33_eabi/usr/include -I/opt/openwrt-svn-trunk/staging_dir/toolchain-arm_v5te_gcc-4.6-linaro_uClibc-0.9.33_eabi/include ' 'CC=arm-openwrt-linux-uclibcgnueabi-gcc' 'CFLAGS=-Os -pipe -march=armv5te -mtune=xscale -fno-caller-saves -fhonour-copts -Wno-error=unused-but-set-variable -msoft-float ' --cache-file=/dev/null --srcdir=.

configure: WARNING: unrecognized options: --disable-nls, --enable-asntracing, --enable-audio, --disable-aec, --enable-file, --enable-gnugk, --enable-h224, --enable-h230, --enable-h235, --enable-h239, --enable-h248, --enable-h249, --enable-h341, --enable-h350, --enable-h450, --enable-h46017, --enable-h46018, --enable-h46019m, --disable-h46023, --enable-h4609, --enable-h460, --enable-h460p, --enable-h501, --enable-t120, --enable-t38, --enable-versioncheck, --enable-video

configure: loading site script /opt/openwrt-svn-trunk/include/site/arm-openwrt-linux-uclibcgnueabi

checking pkg-config is at least version 0.9.0... yes

checking build system type... x86_64-suse-linux-gnu

checking host system type... arm-openwrt-linux-gnu

checking target system type... arm-openwrt-linux-gnu

checking Debugging support... no

checking for C++ compiler default output file name... a.out

checking whether the C++ compiler works... yes

checking whether we are cross compiling... yes

checking for suffix of executables... 

checking for suffix of object files... o

checking whether we are using the GNU C++ compiler... yes

checking whether arm-openwrt-linux-uclibcgnueabi-g++ accepts -g... yes

checking for arm-openwrt-linux-gcc... arm-openwrt-linux-uclibcgnueabi-gcc

checking whether we are using the GNU C compiler... yes

checking whether arm-openwrt-linux-uclibcgnueabi-gcc accepts -g... yes

checking for arm-openwrt-linux-uclibcgnueabi-gcc option to accept ISO C89... none needed

checking for a BSD-compatible install... /usr/bin/install -c

checking for arm-openwrt-linux-ranlib... arm-openwrt-linux-uclibcgnueabi-ranlib

checking for arm-openwrt-linux-nm... arm-openwrt-linux-uclibcgnueabi-nm

checking for arm-openwrt-linux-ldd... no

checking for ldd... ldd

configure: WARNING: using cross tools not prefixed with host triplet

checking for arm-openwrt-linux-objdump... arm-openwrt-linux-uclibcgnueabi-objdump

checking how to run the C preprocessor... arm-openwrt-linux-uclibcgnueabi-gcc -E

checking for grep that handles long lines and -e... /usr/bin/grep

checking for egrep... /usr/bin/grep -E

checking for ANSI C header files... yes

checking for sys/types.h... yes

checking for sys/stat.h... yes

checking for stdlib.h... yes

checking for string.h... yes

checking for memory.h... yes

checking for strings.h... yes

checking for inttypes.h... yes

checking for stdint.h... yes

checking for unistd.h... yes

checking stddef.h usability... yes

checking stddef.h presence... yes

checking for stddef.h... yes

checking limits.h usability... yes

checking limits.h presence... yes

checking for limits.h... yes

checking float.h usability... yes

checking float.h presence... yes

checking for float.h... yes

checking fcntl.h usability... yes

checking fcntl.h presence... yes

checking for fcntl.h... yes

checking OPAL Version... 1.24.1

checking Plugin install directory... /usr/lib/opal-1.24.1

checking sys/time.h usability... yes

checking sys/time.h presence... yes

checking for sys/time.h... yes

checking sys/file.h usability... yes

checking sys/file.h presence... yes

checking for sys/file.h... yes

checking netinet/in.h usability... yes

checking netinet/in.h presence... yes

checking for netinet/in.h... yes

checking vfork.h usability... no

checking vfork.h presence... no

checking for vfork.h... no

checking for fork... yes

checking for vfork... yes

checking for working fork... cross

configure: WARNING: result yes guessed because of cross compilation

checking for working vfork... (cached) yes

configure: Forcing use of local GSM sources

checking size of short... (cached) 2

checking size of int... (cached) 4

checking size of long... (cached) 4

checking size of long long... (cached) 8

checking internal Speex version... 1.1.11.1

configure: forcing use of local Speex sources

configure: forcing use of local iLBC sources

checking for src_get_version in -lsamplerate... no

checking default to full capabilities at empty fmtp lines... yes

checking for LIBAVCODEC... no

checking libavcodec source... disabled

checking for X264... no

checking for THEORA... no

checking for CELT... no

checking dlfcn.h usability... yes

checking dlfcn.h presence... yes

checking for dlfcn.h... yes

checking if dlopen is available... yes

checking for dlopen in -ldl... yes

configure: h264 support disabled due to disabled dependency HAVE_X264

configure: h264 support disabled due to disabled dependency HAVE_H264_DECODER

checking enable H.264 support... no

checking IXJ... yes

checking linux/telephony.h usability... yes

checking linux/telephony.h presence... yes

checking for linux/telephony.h... yes

checking IXJ... yes

checking enable voicetronix vpb... yes

checking capi20.h usability... no

checking capi20.h presence... no

checking for capi20.h... no

checking CAPI... no

checking for fax_free in -lspandsp... no

checking for posix_memalign... yes

configure: creating ./config.status

config.status: creating audio/G722/Makefile

config.status: creating audio/G.722.1/Makefile

config.status: creating audio/G.722.2/Makefile

config.status: creating audio/GSM0610/Makefile

config.status: creating audio/gsm-amr/Makefile

config.status: creating audio/iLBC/Makefile

config.status: creating audio/Speex/Makefile

config.status: creating audio/LPC_10/Makefile

config.status: creating audio/G726/Makefile

config.status: creating audio/IMA_ADPCM/Makefile

config.status: creating audio/SBC/Makefile

config.status: creating audio/celt/Makefile

config.status: creating video/H.261-vic/Makefile

config.status: creating video/H.263-ffmpeg/Makefile

config.status: creating video/H.263-1998/Makefile

config.status: creating video/H.264/Makefile

config.status: creating video/H.264/gpl/Makefile

config.status: creating Makefile

config.status: creating audio/Speex/libspeex/speex_config_types.h

configure: WARNING: unrecognized options: --disable-nls, --enable-asntracing, --enable-audio, --disable-aec, --enable-file, --enable-gnugk, --enable-h224, --enable-h230, --enable-h235, --enable-h239, --enable-h248, --enable-h249, --enable-h341, --enable-h350, --enable-h450, --enable-h46017, --enable-h46018, --enable-h46019m, --disable-h46023, --enable-h4609, --enable-h460, --enable-h460p, --enable-h501, --enable-t120, --enable-t38, --enable-versioncheck, --enable-video

configure: creating ./config.status

config.status: creating audio/G722/Makefile

config.status: creating audio/G.722.1/Makefile

config.status: creating audio/G.722.2/Makefile

config.status: creating audio/GSM0610/Makefile

config.status: creating audio/gsm-amr/Makefile

config.status: creating audio/iLBC/Makefile

config.status: creating audio/Speex/Makefile

config.status: creating audio/LPC_10/Makefile

config.status: creating audio/G726/Makefile

config.status: creating audio/IMA_ADPCM/Makefile

config.status: creating audio/SBC/Makefile

config.status: creating audio/celt/Makefile

config.status: creating video/H.261-vic/Makefile

config.status: creating video/H.263-ffmpeg/Makefile

config.status: creating video/H.263-1998/Makefile

config.status: creating video/H.264/Makefile

config.status: creating video/H.264/gpl/Makefile

config.status: creating Makefile

config.status: creating audio/Speex/libspeex/speex_config_types.h

config.status: creating plugin-config.h

configure: WARNING: unrecognized options: --disable-nls, --enable-asntracing, --enable-audio, --disable-aec, --enable-file, --enable-gnugk, --enable-h224, --enable-h230, --enable-h235, --enable-h239, --enable-h248, --enable-h249, --enable-h341, --enable-h350, --enable-h450, --enable-h46017, --enable-h46018, --enable-h46019m, --disable-h46023, --enable-h4609, --enable-h460, --enable-h460p, --enable-h501, --enable-t120, --enable-t38, --enable-versioncheck, --enable-video



=================== Plugin configuration ======================

 prefix                           : /usr

 exec_prefix                      : /usr

 libdir                           : ${exec_prefix}/lib

 Audio Codec plugin install dir   : ${libdir}/opal-1.24.1/codecs/audio

 Video Codec plugin install prefix: ${libdir}/opal-1.24.1/codecs/video

 LID plugin install prefix        : ${libdir}/opal-1.24.1/lid

 FAX plugin install prefix        : ${libdir}/opal-1.24.1/fax



                              GSM :  yes (internal)

                          gsm-amr :  yes

                             iLBC :  yes (internal)

                            Speex :  yes (internal, version 1.1.11.1)

                            LPC10 :  yes

                            G.726 :  yes

                        IMA_ADPCM :  yes

                              SBC :  no



                           H.261  :  yes

                           H.263  :  no (ffmpeg version)

                     H.263/H.263+ :  no

                           H.264  :  no

                          THEORA  :  no

                    MPEG4 Part 2  :  no

                            CELT  :  no



                     SpanDSP FAX  :  no



                            CAPI  :  no

           Quicknet xJACK support :  yes

         Voicetronics VPB support :  yes



                         OS Type  :  linux-gnu

                    Machine Type  :  arm



 If all settings are OK, type make and make install 

========================================================

configure: WARNING: unrecognized options: --disable-nls, --enable-capi, --enable-celt, --enable-default-to-full-capabilties, --enable-h264, --enable-ixj, --enable-libavcodec, --enable-libavcodec-stackalign-hack, --enable-localgsm, --enable-localilbc, --enable-localspeex, --enable-sbc, --enable-spandsp, --enable-theora, --enable-vpb, --enable-x264, --enable-x264-link-static

rm -f /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/.configured_

touch /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/.configured_

make -j1 -C /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs DESTDIR="/opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/ipkg-install"

make[3]: Entering directory `/opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs'

make[4]: Entering directory `/opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs'

make[4]: Leaving directory `/opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs'

make -C src optshared

make[4]: Entering directory `/opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/src'

Makefile:351: /opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/ptlib2_svn/make/lib.mak: No such file or directory

make[4]: *** No rule to make target `/opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/ptlib2_svn/make/lib.mak'.  Stop.

make[4]: Leaving directory `/opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/src'

make[3]: *** [optshared] Error 2

make[3]: Leaving directory `/opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs'

make[2]: *** [/opt/openwrt-svn-trunk/build_dir/target-arm_v5te_uClibc-0.9.33_eabi/h323plus_cvs/.built] Error 2

make[2]: Leaving directory `/opt/OpenWRT/feeds/packages/libs/h323plus_cvs'

Re: Windows Movie Maker won't play MP4s

2012-03-27T15:44:31Z

Have you tried installing DivX?

Windows Movie Maker won't play MP4s

2012-03-27T06:42:54Z

What codec do I need to downlad for Windows Movie Maker to be able to play MP4s? My Windows Movie Maker won't play MP4s because it says I need to download the codec to play and edit my movie. Can anyone help and give me the site for the codec I need?

Re: AES crypt installed- not shows as running

2012-03-18T05:20:30Z

AES Crypt installs as a Windows shell extension. If you right click on a file on your desktop or elsewhere, you should see a menu option for AES Encrypt. That will handle the encryotion. The program that produces that error you mention is just a program to help make things work when you double click on a .as file. It can be called from the command line, but that was not the intent. If you want a command line (console) version, there is a separate download for that.

AES crypt installed- not shows as running

2012-03-18T00:43:12Z

Hi All,
I am a beginner using AES crypt, I have 32 version installed on laptop running XP & runs normal, however I've been trying to run it on Windows 7 " N version" Professional 64 bit version ( Yes I live in US & this is legit copy from my access to M$ TechNet standard account) running on Dual core Toshiba Laptop.

This seems to install OK trying to start it up via "Run as Administrator" permission ( I normally run as Limited user) nothing works, tried installing 32 bit version as well. there are only 3 files in AEScrypt folder under "program files folder on C drive
when I run one of the programs it generates this error message:
Usage: aescrypt32 [/d|/e] filename
when other icon is run DOS type box briefly flashes & nothing happens.
Am I overlooking something? if so, what is it?

Thanks
Sunmaster57

Re: Project Still Active?

2012-03-17T17:58:58Z

Just wanted to chime in real quick.
Everything is in sourceforge right now, including my changes. I have discovered some minor bugs relating to sreg and attribute exchange that need to be fixed before I post a release that includes my changes. (The trunk code works, but sometimes sreg and attribute exchange will not be sent when it should.)
I will upload a release for the packetizer version in the next day or so, and hopefully shortly after that I will post a new release to include my changes.