Received: by 10.58.205.203 with SMTP id li11mr7245121vec.14.1352897231158;
        Wed, 14 Nov 2012 04:47:11 -0800 (PST)
X-BeenThere: nodejs@googlegroups.com
Received: by 10.220.107.208 with SMTP id c16ls312431vcp.3.gmail; Wed, 14 Nov
 2012 04:46:47 -0800 (PST)
Received: by 10.58.165.34 with SMTP id yv2mr8801403veb.10.1352897207713;
        Wed, 14 Nov 2012 04:46:47 -0800 (PST)
Received: by 10.58.165.34 with SMTP id yv2mr8801401veb.10.1352897207697;
        Wed, 14 Nov 2012 04:46:47 -0800 (PST)
Return-Path: <jcog...@gmail.com>
Received: from mail-vb0-f51.google.com (mail-vb0-f51.google.com [209.85.212.51])
        by gmr-mx.google.com with ESMTPS id q19si3996822vds.3.2012.11.14.04.46.47
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 14 Nov 2012 04:46:47 -0800 (PST)
Received-SPF: pass (google.com: domain of jcog...@gmail.com designates 209.85.212.51 as permitted sender) client-ip=209.85.212.51;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jcog...@gmail.com designates 209.85.212.51 as permitted sender) smtp.mail=jcog...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-vb0-f51.google.com with SMTP id fn1so329933vbb.38
        for <nodejs@googlegroups.com>; Wed, 14 Nov 2012 04:46:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=C3ImMyae5ok1l/w1OgRoYmldNIx+cGCFJmJruPtHVk8=;
        b=BEtWmKp13GrqzT2rtLF+nBVXfliVcqP/Y8y1MKK7B4A86rQg6CWHf7qijPxZNmKIGQ
         89U+dw9o0ztHiLbiX7hH57nekxiX2VqiUKUFxw7YRj72DoNAYaI+vLGq+hVpVLkwN4sI
         EL+7f370zWFKGVRfgnEnVM+IKjv0DvHXEfTVhIc2pT4r1s1E4ntLGQeRTC8N4xoJHkoj
         S+PpSK2a6m2kPbeo3hZJ95pWBwL0oSXiK8QiPvGQC+75LHcwcEYuLE5QvovkpyEJqU4D
         RCSxer9gf62NpgSsyY0UTl2gdeJO49rN43XLNY/QlwnaQLF/4R5mHkOmJjykYU2J0IWJ
         bMKQ==
MIME-Version: 1.0
Received: by 10.220.39.129 with SMTP id g1mr10884495vce.72.1352897207551; Wed,
 14 Nov 2012 04:46:47 -0800 (PST)
Received: by 10.58.80.72 with HTTP; Wed, 14 Nov 2012 04:46:46 -0800 (PST)
Date: Wed, 14 Nov 2012 12:46:46 +0000
Message-ID: <CALm1c-GoQXhRFfKUs8XG1f-OeKYFHZ2Pfk8nPqWDSADaDyr...@mail.gmail.com>
Subject: Picking modes in createCipher()
From: James Coglan <jcog...@gmail.com>
To: Node list <nodejs@googlegroups.com>
Content-Type: multipart/alternative; boundary=bcaec54ee45879468704ce73ed17

--bcaec54ee45879468704ce73ed17
Content-Type: text/plain; charset=ISO-8859-1

I'm wondering why crypto.createCipher() lets me pick aes-256-cbc but not
aes-256-ctr or aes-256-gcm. These modes are available in openssl and I can
invoke them from Ruby, no problem. Why are they not available in Node?

Thanks,
James

-- 
James Coglan
http://jcoglan.com
+44 (0) 7771512510

--bcaec54ee45879468704ce73ed17
Content-Type: text/html; charset=ISO-8859-1

I&#39;m wondering why crypto.createCipher() lets me pick aes-256-cbc but not aes-256-ctr or aes-256-gcm. These modes are available in openssl and I can invoke them from Ruby, no problem. Why are they not available in Node?<div>
<br></div><div>Thanks,</div><div>James<br clear="all"><div><br></div>-- <br>James Coglan<br><a href="http://jcoglan.com">http://jcoglan.com</a><br>+44 (0) 7771512510<br>
</div>

--bcaec54ee45879468704ce73ed17--