Skip to main content

Encryption of image files on Android — Cipher(Output|Input)Stream problems



I'm trying to encrypt image files on Android with password based encryption. To save the encrypted image I just do this:







FileOutputStream fos = new FileOutputStream(thumbnailFile);

CipherOutputStream cos = new CipherOutputStream(fos, encryptCipher);

Bitmap thumbnail = Bitmap.createScaledBitmap(bm2, 140, 140, true);

thumbnail.compress(Bitmap.CompressFormat.JPEG, 80, cos);







and to read it, this:







FileInputStream fis = new FileInputStream(f);

CipherInputStream cis = new CipherInputStream(fis, decryptCipher);

Bitmap b = BitmapFactory.decodeStream(cis);







but the Bitmap ends up as null. The code works when I bypass the encryption; that is when I use the File(Input|Output)Streams rather than the Cipher(Input|Output)streams.





My Ciphers are created as follows:







public void initCiphers(char password[]) {



PBEKeySpec pbeKeySpec;

PBEParameterSpec pbeParamSpec;

SecretKeyFactory keyFac;



byte[] salt = {

(byte)0xc7, (byte)0x73, (byte)0x21, (byte)0x8c,

(byte)0x7e, (byte)0xc8, (byte)0xee, (byte)0x99

};

int count = 20;

pbeParamSpec = new PBEParameterSpec(salt, count);

pbeKeySpec = new PBEKeySpec(password);

try {

keyFac = SecretKeyFactory.getInstance("PBEWithMD5AndDES");

SecretKey pbeKey = keyFac.generateSecret(pbeKeySpec);

encryptCipher = Cipher.getInstance("PBEWithMD5AndDES");

decryptCipher = Cipher.getInstance("PBEWithMD5AndDES");

encryptCipher.init(Cipher.ENCRYPT_MODE, pbeKey, pbeParamSpec);

decryptCipher.init(Cipher.DECRYPT_MODE, pbeKey, pbeParamSpec);

} catch (Exception e) {

Log.v("tag", e.toString());

}







I don't get any exceptions.





There is obviously some problem with using Cipher(Output|Input)Streams with the android functions for encoding and/or decoding images, but since those functions are opaque and there are no exceptions, its hard to know what it is. I suspect it has to do with padding or flushing. Any assistance would be gratefully appreciated.



Source: Tips4all

Comments

  1. You could subclass CipherOutputStream or even just OutputStream, and just override the flush() method to do nothing.

    ReplyDelete
  2. When writing to a CipherOutputStream, make sure you close() the stream after writing the data (and not closing the underlying stream before it). Closing makes sure the right padding is added. A flush() alone is not enough here.

    Also, I would advise to not use DES for new protocols - preferred nowadays is AES.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex