{"action":"opened","issue":{"url":"https://api.github.com/repos/milagro-crypto/milagro-crypto-c/issues/285","repository_url":"https://api.github.com/repos/milagro-crypto/milagro-crypto-c","labels_url":"https://api.github.com/repos/milagro-crypto/milagro-crypto-c/issues/285/labels{/name}","comments_url":"https://api.github.com/repos/milagro-crypto/milagro-crypto-c/issues/285/comments","events_url":"https://api.github.com/repos/milagro-crypto/milagro-crypto-c/issues/285/events","html_url":"https://github.com/milagro-crypto/milagro-crypto-c/issues/285","id":341834854,"node_id":"MDU6SXNzdWUzNDE4MzQ4NTQ=","number":285,"title":"AES_GCM de/crypt with curve BLS383","user":{"login":"jaromil","id":148059,"node_id":"MDQ6VXNlcjE0ODA1OQ==","avatar_url":"https://avatars2.githubusercontent.com/u/148059?v=4","gravatar_id":"","url":"https://api.github.com/users/jaromil","html_url":"https://github.com/jaromil","followers_url":"https://api.github.com/users/jaromil/followers","following_url":"https://api.github.com/users/jaromil/following{/other_user}","gists_url":"https://api.github.com/users/jaromil/gists{/gist_id}","starred_url":"https://api.github.com/users/jaromil/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jaromil/subscriptions","organizations_url":"https://api.github.com/users/jaromil/orgs","repos_url":"https://api.github.com/users/jaromil/repos","events_url":"https://api.github.com/users/jaromil/events{/privacy}","received_events_url":"https://api.github.com/users/jaromil/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-17T09:20:01Z","updated_at":"2018-07-17T09:20:01Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"dear Milagro devs, experimenting with ECDH and in particular AES_GCM de/cryption (pbc_support.c) for curve BLS383 I've stumbled into a segfault which may signal a bug.\r\n\r\nI believe it is reproducible by creating two pub/priv keyrings with BLS383 then computing a  session key for them using `ECP_BLS383_SVDP_DH`. Then using this session key as `K` argument into `AES_GCM_ENCRYPT(k, iv, h, in, out, t)` it segfaults inside that function.\r\n\r\nI am reasonably sure of my code here, since the very same procedure using curve ED25519 leads to success and all my tests pass.\r\n\r\nDo you have any insights? are AES_GCM operations on BLS383 supported in milagro and covered by tests?\r\n\r\nthanks!"}}
{"actor":{"display_login":"jaromil"}}