03-31-2013 02:55 PM
I haven't received any answers regarding my questions so I decided to repost it. Could someone from Blackberry explain why RIM chose to change a client-based solution like S/MIME and use as a server-based feature under Blackberry Enterprise Server?
Answers like "because we have been doing it all the time" is not what I am looking for and it should not be an answer from a security-conscious company like RIM.
03-31-2013 03:40 PM
Given the wording of your question and thereby just to set your expectation...please review this information (which is at the top of every page on this site):
So, while you may get lucky with a response from a BlackBerry representative (from time to time, they do drop by), you should not be expecting a formal nor authoritative response via this site (the Ts and Cs also confirm that, even when a BB person does respond, it is not to be taken as BlackBerry authoritative).
03-31-2013 04:07 PM
I asked them the questions multiple times and they have been avoiding to answer it. The only time i got an answer was like this "if you are concerned about security, get BES." And when I asked why they chose this way to implement, their answer was "because it is teh way we have been doing it."
So I am trying again to see if they will answer the question in a dedicated post.
03-31-2013 04:34 PM
OK...searching, I do see Vicious Ferret's reply to you (VF is an actual BB person):
As you continue to pursue, just do please understand that, especially in this forum, you are unlikely to get anything more than that...especially to your "why?" question. The answer, quite naturally, involves, trade secrets, proprietary information, and/or access to internal information...all of which are prohibited from being posted on this site (per the Ts and Cs).
In all honesty, I believe that, with VF's reply from up there, that's all you are going to get here on this site, especially in the public zone. You might try a PM instead, and see if you can get more...but I doubt you will. What you are asking for is quite outside the scope, purpose, and Ts&Cs of this site.
In a nutshell, this site is, on a user-to-user basis, all about "what is" and "how to" concerning "what is"...it is not for "what should be", "why is it", "when will it be", or other such discussions (except for speculation about those things...that's OK...but nothing authoritative).