S/MIME and Digital Certificate Support on Androi

by weddi » Thu, 05 Nov 2009 00:27:43 GMT


Sponsored Links
 Does Android currently support S/MIME within email?  Does Android
allow for Client Authentication onto secured websites using a Digital
Certificate.

This would be the ability to store a digital certificate's private and
public keys within the phone (preferably through a .p12 or .pfx file)
and use that certificate to sign email messages.  The same certificate
should also be able to encrypt emails to a recipient whose public key
is stored on the device along with the ability to decrypt messages
sent to you.

I think that this functionality is key for businesses that incorporate
digital certificates as a way to secure exchange certificates and
sensitive information.  The only main OS's who use S/MIME currently is
a Blackberry device from RIM and any phone with Windows Mobile.  The
Blackberry allows the S/MIME package to be installed, however it is
disabled from the beginning which is a pain to installed for every
Blackberry.  Windows Mobile also uses it very nicely, however Windows
Mobile as an OS isn't the nicest as an OS (my opinion).

The iPhone allows for Digital Certificates to be installed and used
for Client Authentication, however it has absolutely no support for S/
MIME currently.

Assuming that the Android OS does not support S/MIME, I believe it
would be the best way to go as more business orientated people will be
able to use the phone.



Other Threads

1. List adapter: failing to recycle views = lots of memory allocated?



I don't think that was the case. I think the example is just sub-optimal.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://twitter.com/commonsguy

Warescription: Three Android Books, Plus Updates, One Low Price!

-- 

2. List adapter: failing to recycle views = lots of memory allocated?

Hi,

I'm looking at List8 in the sdk api samples folder. In this example,
the list adapter doesn't recycle 'convertView':

  public View getView(int position, View convertView, ViewGroup
parent) {
    // Make an ImageView to show a photo
    ImageView i = new ImageView(mContext);

    i.setImageResource(mPhotos.get(position));
    i.setAdjustViewBounds(true);
    i.setLayoutParams(new AbsListView.LayoutParams(
      LayoutParams.WRAP_CONTENT,
      LayoutParams.WRAP_CONTENT));
    // Give it a nice background
    i.setBackgroundResource(R.drawable.picture_frame);
    return i;
  }

I'm running this example on a nexus one. I am flinging the listview up
and down, and it seems to grow the heap up to 8mb at times before
releasing anything. This doesn't happen when convertView is recycled,
the memory usage remains quite stable as expected.

I started working on a project where there's an adapter implemented
which also does not recycle convertView. Same behavior as above, I can
grow the heap to 12/13mb before anything is released. So I end up
seeing a lot of out of memory exceptions as I play with other parts of
the app and so much memory is already allocated.

There's no reason not to use convertView, and none of this behavior is
unexpected. I thought though that in earlier versions of the SDK that
listview would internally release views more quickly if you weren't
using convertView, and were allocating all of them like in the above
example? By earlier versions, I mean like the first version of the SDK
two years ago, when we were trying to figure out what convertView was
at all. Just curious,

Thanks

-- 

3. Learn the latest phone from Nokia n86 pictures and Features

4. What is the best way to schedule an event that will wake up the phone if it goes into sleep mode?

5. seekbar half clickable

6. Accessing sdcard on ADP2 failed

7. surfaceCreated(SurfaceHolder holder) method never gets called