I agree it would be ideal to have the newer modules running on both servers -- I am just not sure the best way to ensure backward compatibility with data that is stored encrypted via the "old method". I guess I could create a copy of the table in question with unencrypted data, and then re-encrypt with the new method. Any other suggestions?[root@ Crypt-IDEA-1.01]# perl Makefile.PL Checking if your kit is complete... Looks good Writing Makefile for Crypt::IDEA [root@ Crypt-IDEA-1.01]# make cp IDEA.pod blib/lib/Crypt/IDEA.pod cp IDEA.pm blib/lib/Crypt/IDEA.pm /usr/local/bin/perl /usr/local/lib/perl5/5.8.0/ExtUtils/xsubpp -typem +ap /usr/local/lib/perl5/5.8.0/ExtUtils/typemap -typemap typemap IDEA +.xs > IDEA.xsc && mv IDEA.xsc IDEA.c Please specify prototyping behavior for IDEA.xs (see perlxs manual) cc -c -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE +-D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -O2 -DVERSION=\"1.01\" - +DXS_VERSION=\"1.01\" -fpic "-I/usr/local/lib/perl5/5.8.0/i686-linux/C +ORE" IDEA.c IDEA.xs: In function `XS_Crypt__IDEA_crypt': IDEA.xs:66: `sv_undef' undeclared (first use in this function) IDEA.xs:66: (Each undeclared identifier is reported only once IDEA.xs:66: for each function it appears in.) make: *** [IDEA.o] Error 1
In reply to Re: Re: Crypt CBC using IDEA - output differs btwn systems
by ewitch
in thread Crypt CBC using IDEA - output differs btwn systems
by ewitch
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |