René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Two questions about ssh-jce","articleBody":"1) \r\n`KeyFormat.SSH_RSA` has `Algorithm.SSH_RSA` as the first candidate for algorithm, but it is not supported by node-http-signature:\r\n\r\nhttps://github.com/adamcin/httpsig-java/blob/2b1fc5601bbc17ee4b953c0063423fffe2ccd0bb/ssh-jce/src/main/java/net/adamcin/httpsig/ssh/jce/KeyFormat.java#L53\r\n\r\nhttps://github.com/joyent/node-http-signature/blob/529441d9d04a8ecb296a2a152929332526344673/lib/utils.js#L13\r\n\r\nFor this to work without algorithms rotations, i do the following after a signer creation:\r\n\r\n```\r\nCollection\u003cAlgorithm\u003e algorithms = Collections.singletonList(Algorithm.RSA_SHA256);\r\nChallenge challenge = new Challenge(\"\u003cpreemptive\u003e\", Constants.DEFAULT_HEADERS, algorithms);\r\nsigner.rotateKeys(challenge);\r\n```\r\n\r\nIs this how it is supposed to be used? Can't there be more \"out of the box experience\" for this?\r\n\r\n\r\n2) \r\nWhy `SSHKey` here must have public key?\r\n\r\nhttps://github.com/adamcin/httpsig-java/blob/2b1fc5601bbc17ee4b953c0063423fffe2ccd0bb/ssh-jce/src/main/java/net/adamcin/httpsig/ssh/jce/SSHKey.java#L64\r\n\r\nIt seems that presence of methods like `canVerify` and checks in `verify` method itself should prevent invalid use. Just curious. Use case is that a key used only for signing, not verifying.","author":{"url":"https://github.com/vonagam","@type":"Person","name":"vonagam"},"datePublished":"2017-03-07T22:01:56.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/8/httpsig-java/issues/8"}