var test = require('tape') var crypto = require('diffie-hellman/browser') test('diffie-hellman mod groups', function (t) { [ 'modp1', 'modp2', 'modp5', 'modp14', 'modp15', 'modp16' ].forEach(function (mod) { t.test(mod, function (t) { t.plan(3) var dh1 = crypto.getDiffieHellman(mod) var p1 = dh1.getPrime().toString('hex') dh1.generateKeys() var dh2 = crypto.getDiffieHellman(mod) var p2 = dh2.getPrime().toString('hex') dh2.generateKeys() t.equals(p1, p2, 'equal primes') var pubk1 = dh1.getPublicKey() var pubk2 = dh2.getPublicKey() t.notEquals(pubk1, pubk2, 'diff public keys') var pub1 = dh1.computeSecret(pubk2).toString('hex') var pub2 = dh2.computeSecret(dh1.getPublicKey()).toString('hex') t.equals(pub1, pub2, 'equal secrets') }) }) }) test('diffie-hellman key lengths', function (t) { [ 64, 65, 192 ].forEach(function (len) { t.test('' + len, function (t) { t.plan(3) var dh2 = crypto.createDiffieHellman(len) var prime2 = dh2.getPrime() var p2 = prime2.toString('hex') var dh1 = crypto.createDiffieHellman(prime2) var p1 = dh1.getPrime().toString('hex') dh1.generateKeys() dh2.generateKeys() t.equals(p1, p2, 'equal primes') var pubk1 = dh1.getPublicKey() var pubk2 = dh2.getPublicKey() t.notEquals(pubk1, pubk2, 'diff public keys') var pub1 = dh1.computeSecret(pubk2).toString('hex') var pub2 = dh2.computeSecret(dh1.getPublicKey()).toString('hex') t.equals(pub1, pub2, 'equal secrets') }) }) })
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 19553 | swellard | Move and rename clients | ||
//guest/perforce_software/helix-web-services/main/source/clients/2016.1.0/javascript/node_modules/crypto-browserify/test/dh.js | |||||
#1 | 18810 | tjuricek |
First-pass at JavaScript client SDK. JavaScript requires Node with Gulp to "browserfy" the library. It's the easiest way I found to use the swagger-js project; bundle up a wrapping method. There is no JavaScript reference guide. The swagger-js doesn't really document what they do very well, actually. Overall I'm not particularly impressed by swagger-js, it was hard to even figure out what the right method syntax was. We may want to invest time in doing it better. This required setting CORS response headers, which are currently defaulted to a fairly insecure setting. |