From 5dc9bc948cb849135b4876192875e860cf9158d3 Mon Sep 17 00:00:00 2001 From: Gurpartap Singh Date: Tue, 31 Jul 2012 12:58:58 +0530 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 28cb7e9..3a8b51e 100644 --- a/README.md +++ b/README.md @@ -45,7 +45,7 @@ Decrypting ## Corresponding usage in Objective-C -The AESCrypt Objective-C class understands what you're talking about in your Ruby code. The purpose of the Ruby gem and Objective-C class is to have something that works out of the box across the server (Ruby) and client (Objective-C). However, a standard encryption technique is implemented, which ensures that you can handle the data with any AES compatible library available across the web. So, you're not locked-in. +The AESCrypt Objective-C class, available at https://github.com/Gurpartap/AESCrypt-ObjC, understands what you're talking about in your Ruby code. The purpose of the Ruby gem and Objective-C class is to have something that works out of the box across the server (Ruby) and client (Objective-C). However, a standard encryption technique is implemented, which ensures that you can handle the data with any AES compatible library available across the web. So, you're not locked-in. Here's how you would use the AESCrypt Objective-C class: