Tuesday, September 1, 2009

eBuddy ~ Developers response, fix on its way!

Good news, I have just been in some discussion with the maintainers of eBuddy previously mentioned here. As you can see, we raised some issues about the method's utilised during key parts of the program's execution.

The maintainers have assured me that they take the issue very seriously and have committed to taking action to resolve the issues raised. You can see their response below:

"Thank you very much for your email. I really appreciate you reaching out to us in this way. I already saw the blog post via a Google alert in the weekend. Before responding to you we had internal discussion as to how this happened, what the best way is to deal with the situation etc.

Let me begin by saying we value security of our users very much! We support multiple products (both web and mobile) and want all of them to be safe for our users. One of our lead mobile developers (name) (also in cc) will reach out to with more detailed technical information as to how we will deal with the current situation.

But in short we are currently working on a staged approach where we will add rudimentary security to all or clients ASAP in the first stage (in this way we can get an update out to the public quickly). After that we will make all necessary changes to our back-end architecture and clients to raise the security to an ever higher level. A level can be expected from a professional company!"


It's good to see that they are taking the issue seriously and are committed to getting improvements out to the iPhone community asap. I look forward to testing the new version, till next time, safe iPhoning!

2 comments:

  1. im glad ebuddy's fixing this, i really like their service. and btw. i really like the new blog skin/theme (Y)

    ReplyDelete
  2. Any idea of this fixed has been implemented?

    ReplyDelete