TrustMeSecurity.com

TrustMe Security, a provider of development platforms for secure online communication applications, today announced that it is adding support for OAuth to the TrustMe Security API.

OAuth is an open protocol that enables secure API authentication for web, mobile and desktop applications using a standard method. The protocol gives service provider developers access to their data on OAuth compatible services while protecting their account credentials. Supporting OAuth is ensuring that TrustMe is working with developers to easily work with the best available open protocols and standards.

“With only about six per cent of all Facebook applications averaging at least 500 active users per day TrustMe wants to ensure that developers have access to the tools they need to easily and efficiently develop applications for all online communication platforms,” said Mike Mullen, CTO of TrustMe Security. “Consumers need to feel confident that the applications they are using are safe and secure. Supporting open protocols like OAuth will help developers feel confident in the security they are offering with TrustMe’s API.”

TrustMe empowers developers to add security and privacy to online communication platforms such as email, social networks (Facebook, MySpace, LinkedIn, etc.), instant messaging and VoIP. Developers may access TrustMe’s Public Key Name Service (PKNS) using a REST-based API. The PKNS allows applications and web sites to encrypt communications and limit the disclosure of a person’s personal information to only that person’s trusted contacts.

“OAuth is an emerging, community-driven open protocol that is essential to lowering the cost of doing the right thing when it comes to helping people share their information between web services in a safe and easy way,” said Chris Messina, Open Source Advocate-at-Large. “That TrustMe should adopt this protocol speaks to their foresight and good intentions when it comes to securely delivering people’s private and personal information wherever it needs to go.”

While attending the F8 Conference this week in San Francisco, the TrustMe team will be meeting with Facebook developers to gain insight and feedback on additional open protocols and standards developers are relying on as well as the TrustMe API. TrustMe is dedicated to providing the developer community with the most complete and easy-to-use development tools to secure online communication applications. The TrustMe API is available for free at www.trustmesecurity.com.

-30-

Looking for more information? You can contact Drew at TrustMe at 506 860 6600 or our fantastic media rep, Natalie Sauvé from High Road Communications at 613 688 1187.

RSA Cryptography methods have been standardized across all development platforms for many years now.

Every platform I have worked on (Linux, OSX, MS) has basic usable methods of encrypting and decrypting RSA encrypted information. This would lead a programmer to believe that you can pass that encrypted data between environments and systems. Much to my dismay, I have found out this is not actually the case.

Read this MSDN article that explains how since version 1, the MS .NET platform actually passes RSA encrypted data around backwards.

http://blogs.msdn.com/shawnfa/archive/2005/12/05/500144.aspx

Mike and Elisabeth will be in San Francisco today at SummerMash San Francisco and Social Media Camp. We’ll see you there.

Our development lead Dean and his wife Rachel welcomed their new daughter Lauren into the world at 5:10 a.m this morning. This is number three for Dean and Rachel and their third girl. Mother and baby are doing well. Congratulations!

We’ll create a TrustMe account for Lauren to make sure she gets started on the right foot.

Mike and Derek’s latest podcast is available at devcasting.com.  Click here for a direct link.

I had an excellent lunch-time conversation with a few mates from here at TrustMe Security as well as Derek Hatchard from ArdentDev. So good was the conversation that I thought I’d bring the underlying question (in my mind) to the web and try to get some feedback.

At issue were the fundamentally different styles of tagging that we use. Although the differences in the end result of our methodologies is minimal, I think I can learn by understanding them. My main motivation is to find the best possible tagging methodology for myself while making my tags relevant for others to find the content.

So my questions are:

• How do you tag your content?
• What, if any, questions do you ask yourself when determining tags for your content?
• Do these questions differ based on the tag provider? (e.g. is your methodology fundamentally different when tagging for digg, delicious, you own blog, etc.?).

For example, when I tag for del.icio.us I sometimes pretend I’m telling somebody about the site I am tagging and use tags based on how I’d describe it to them. I think I am likely to use those words/phrases again when searching for this bookmark in the future. Until recently I didn’t really understand any other way of doing it. See? I need some feedback!

I had a great time at Third Tuesday last night and met a ton of great people! Thanks for the opportunity to participate in the panel discussion on social media. I’m going to try to expand on our discussion with some advice and information that you can apply to your social media strategy on this blog in the coming days and weeks so keep an eye out!

Also, I’ll be involved in organizing the next Moncton edition of ThirdTuesday, which, if I’m not mistaken, is September 16, 2008. If anybody would like to offer some suggestions you can comment here, on the meetup site or contact me directly. Looking forward to the next one! Cheers.

Mozilla is attempting to set the Guinness World Record for Most Software Downloaded in 24 Hours starting at 10:00 AM PDT (1:00 PM EST and 2:00 PM AST).

You can download the very popular web browser, when it’s available, by clicking here.

We check our site for compatibility with Internet Explorer 7x, Firefox 2x, Opera 9x and Safari 3x. We’ll deprecate our support for Firefox 2x in about a month, although typically with Firefox supporting older versions is not an issue.

Derek Hatchard and our own Mike Mullen have posted another podcast over at devcasting.com. This podcast includes Mike’s reflecting on our MESH 08 experience amongst other topics. Check it out.

We’re happy to announce that [private] BETA invites are on their way out. The new platform site has been released. If you attended our recent launch event or have been promised a key by speaking with one of our representatives, they will be with you soon.

At the moment the platform is still very developer focused in order to help developers incorporate TrustMe technology into their applications. In coming updates we will be incorporating additional functionality for developers and users in order to make our platform the most full-featured integration point for trust-based technology.

I’m really looking forward to seeing what the community will do with our platform to enhance their applications’ security.