EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Large files

Also by EldoS: Rethync
The cross-platform framework that simplifies synchronizing data between mobile and desktop applications and servers and cloud storages
#12616
Posted: 02/26/2010 13:02:46
by Everett Bell (Standard support level)
Joined: 02/26/2010
Posts: 8

Can anyone provide potential filesize limitations or implications using PGP encryption and compression in SecureBlackBox?

I know that's a little vague but I'm just looking for any experiences with using source files of 1-2GB or even larger size, or multiple source files adding up to multiple GBs compressed and encrypted into a single file.

So far my testing seems to show the entire source file is loaded/processed in memory so RAM/Virtual disk space is one limiting factor ... any other thoughts?

Thanks!
Everett Bell
SynTel, LLC
#12618
Posted: 02/26/2010 13:37:25
by Mykola Olshevsky (Basic support level)
Joined: 07/07/2005
Posts: 450

Hi. There is no limitation for file size while using new OpenPGP features (i.e. when you don't need to be compatible with PGP 2.3.*, PGP 6.5.*).
Also, our library doesn't need to store whole file in memory, it processes it as stream, you can check it with PGPFilesDemo.
The only one exception is when you need to be compatible with older implementations, but in such case you can use temporary files to store intermediate data.
#12619
Posted: 02/26/2010 13:52:11
by Mykola Olshevsky (Basic support level)
Joined: 07/07/2005
Posts: 450

Forgot to add: no PGP-specific size limitation, but, since we work with Pascal/.NET Streams, there is 64-bit data size limitation.
#12621
Posted: 02/26/2010 14:50:42
by Everett Bell (Standard support level)
Joined: 02/26/2010
Posts: 8

Thanks! I was testing with specifying source and destination filenames directly as opposed to the streams. I'll look into working with the streams directly now.
#12622
Posted: 02/26/2010 15:40:23
by Mykola Olshevsky (Basic support level)
Joined: 07/07/2005
Posts: 450

Work with streams is similar to work with filenames, and if you seen high memory usage it means that you didn't attach handler for OnTemporaryStreamNeeded, or didn't set .UseNewFeatures to true (and .UseOldPackets to false).
You should take a look at PGPFilesDemo application.
Also by EldoS: BizCrypto
Components for BizTalk® and SQL Server® Integration Services that let you securely store and transfer information in your business automation solutions.

Reply

Statistics

Topic viewed 1225 times

Number of guests: 1, registered members: 0, in total hidden: 0




|

Back to top

As of July 15, 2016 EldoS Corporation will operate as a division of /n software inc. For more information, please read the announcement.

Got it!