[{"data":1,"prerenderedAt":221},["ShallowReactive",2],{"project-17463015":3},{"id":4,"name":5,"line":6,"line_source":7,"title":8,"url":9,"domain":10,"maker":11,"posted_at":12,"year":13,"points":14,"comments":15,"rank_in_year":16,"shown_in_year":17,"top":18,"tier":19,"category":20,"subcategory":21,"format":22,"keywords":23,"reception":29,"sentiment":30,"stance_mix":31,"scored_comments":35,"aspects":36,"strip":42,"post_text":44,"what":45,"said":81,"maker_in_thread":147,"shape":156,"grid":158,"attempts":182,"same_week":183,"maker_shows":43,"maker_hidden":213,"reader_version":214,"card":215},"17463015","Gmelius","Prevent email forgery in Gmail using a Blockchain-powered architecture","title","Show HN: Prevent email forgery in Gmail using a Blockchain-powered architecture","https:\u002F\u002Fgmelius.com\u002Femail-blockchain\u002F","gmelius.com","xpressyoo",1530796841,2018,19,14,1225,2155,57,"shown","productivity","email tools","browser_extension",[24,25,26,27,28],"email forgery","email timestamping","gmail","blockchain","merkle tree","roasted",-0.533,{"positive":32,"neutral":33,"mixed":32,"critical":34},0,1,7,8,{"idea":37,"execution":39,"privacy":40},{"positive":32,"critical":38},4,{"positive":32,"critical":33},{"positive":32,"critical":41},2,[33,32,33,32,33,32,33,32,43,33,32,33,32,33],3,null,{"problem":46,"audience":53,"pricing":44,"motivation":57,"time_to_build":44,"stack":61,"openness":78,"stage":79,"team_size":80},{"value":47,"source":48,"evidence":49},"Email has no built-in way to prove the integrity, authenticity or send time of its content","maker",[50],{"id":51,"by":11,"text":52},"17463397","Hi vivan. Thanks for your comment. Besides the signature of an email using the robustness and persistence of the blockchain, what is different with \"Email Stamping\" and…",{"value":54,"source":48,"evidence":55},"Professionals sending sensitive emails such as lawyers, insurers and brokers",[56],{"id":51,"by":11,"text":52},{"value":58,"source":48,"evidence":59},"Prove that emails were sent with specific content at a specific time, for legal evidence",[60],{"id":51,"by":11,"text":52},[62,68],{"value":63,"source":48,"evidence":64},"Gmail API",[65],{"id":66,"by":11,"text":67},"17463616","Yes, we integrate with Gmail and communicate via the official Gmail API. We only receive response statuses and act accordingly. Moreover, we think it's important for this…",{"value":69,"source":48,"evidence":70},"RSA signing with SHA2-512 hashing",[71,75],{"id":72,"by":73,"text":74},"17463456","crote","Big red flag: > The hash of an email is computed using the SHA2-512 hashing algorithm and signed with our own 512-bit private RSA key. Why even bother signing it if your key is…",{"id":76,"by":11,"text":77},"17463557","Thanks for your comments. \"They both supply email tracking, and protect your privacy by blocking email tracking.\" > This is mainly offered to prevent false positives for our own…","unknown","launched","company",{"praise":82,"objections":83,"requests":116,"questions":117,"alternatives":129},[],[84,96,103,109],{"value":85,"source":86,"evidence":87},"Blockchain adds no real benefit over existing email signatures","commenter",[88,92],{"id":89,"by":90,"text":91},"17463304","vivan","What benefit does the anchoring give over just the signing part? Surely the signature is enough to prove that the email is from the expected sender? I feel like this is just an…",{"id":93,"by":94,"text":95},"17465927","jlgaddis","Yes, because the killer feature missing from SPF + DKIM + DMARC is \"blockchain\". \u003Crolls eyes> Every time I see some new \"\u003Creliable tech>, now with Blockchain!\" announcement, it…",{"value":97,"source":86,"evidence":98},"Timestamping proves existence at a time, not sending or authenticity",[99],{"id":100,"by":101,"text":102},"17463496","nadaviv","How does that prove the email was sent, though? Couldn't one timestamp the email into the blockchain, without actually sending the email to the other party? Edit: btw, I released…",{"value":104,"source":86,"evidence":105},"Gmelius is a trusted third party, so the blockchain does not remove trust",[106],{"id":107,"by":101,"text":108},"17463665","Well, doesn't that mean that the security model is based on you acting as trusted third party and relying on you to only write truthful data to the blockchain? In other words,…",{"value":110,"source":86,"evidence":111},"512-bit RSA key is far too weak",[112,113],{"id":72,"by":73,"text":74},{"id":114,"by":73,"text":115},"17463813","\"The insertion is done when we have received a response from Google servers\" But GMelius is a client-side application, right? According to your whitepaper, the insertion is done…",[],[118,122],{"value":119,"source":86,"evidence":120},"Why anchor each email rather than the Merkle root",[121],{"id":72,"by":73,"text":74},{"value":123,"source":86,"evidence":124},"How does it prove the email was actually sent",[125,126],{"id":100,"by":101,"text":102},{"id":127,"by":101,"text":128},"17463571","So you're acting as a trusted party to get delivery confirmations from Google? What if Google doesn't confirm delivery, but you decide to write to the blockchain anyway? Also,…",[130,135,143],{"value":131,"source":86,"evidence":132},"Email signing with SPF, DKIM and DMARC",[133,134],{"id":93,"by":94,"text":95},{"id":89,"by":90,"text":91},{"value":136,"source":86,"evidence":137},"Blockchain timestamping services such as btproof",[138,139],{"id":100,"by":101,"text":102},{"id":140,"by":141,"text":142},"17463467","1ba9115454","You can use a blockchian to as a trusted timestamping service https:\u002F\u002Fstrongcoin.com\u002Fblog\u002Fusing_the_blockchain_as_a_trusted_timestamping_service Wether this would hold up in…",{"value":144,"source":86,"evidence":145},"Streak CRM",[146],{"id":89,"by":90,"text":91},{"comments":148,"answered":149,"key":150},6,5,[151,152,155],{"id":51,"text":52},{"id":153,"text":154},"17463527","The insertion is only done once we have received a response from Google servers that the email has been indeed sent (without bounce or other errors).",{"id":66,"text":67},{"commenters":148,"max_depth":34,"maker_replies":148,"first_comment_mins":157,"lifespan_hours":148},42,[159,161,163,164,166,168,169,170,173,174,176,178,179,181],[89,32,33,160,90,32],"project\u002Fcritical\u002Fidea",[51,32,32,162,11,33],"maker\u002Fneutral\u002Fidea",[100,32,33,160,101,32],[153,32,32,165,11,33],"project\u002Fneutral\u002Fexecution",[127,32,33,167,101,32],"project\u002Fcritical\u002Fexecution",[66,32,32,165,11,33],[107,32,33,160,101,32],[171,32,32,172,11,33],"17463748","project\u002Fneutral\u002Fidea",[140,32,43,172,141,32],[72,33,33,175,73,32],"project\u002Fcritical\u002Fprivacy",[76,33,32,177,11,33],"maker\u002Fneutral\u002Fnone",[114,33,33,175,73,32],[180,33,32,165,11,33],"17463890",[93,41,33,160,94,32],[],[184,189,194,199,203,208],{"id":185,"name":186,"points":187,"category":188},"17487552","Browsh",967,"dev_tools",{"id":190,"name":191,"points":192,"category":193},"17470037","Hacker News job trends",371,"data",{"id":195,"name":196,"points":197,"category":198},"17509601","Solving Rush Hour",223,"games",{"id":200,"name":201,"points":202,"category":20},"17506753","Markdown New Tab",218,{"id":204,"name":205,"points":206,"category":207},"17505559","Oathkeeper",174,"infrastructure",{"id":209,"name":210,"points":211,"category":212},"17508151","Online challenge",143,"learning_science",false,"v2",{"id":216,"name":5,"line":6,"ai":213,"cat":20,"year":13,"points":14,"comments":15,"rec":29,"s":217,"top":18,"kw":218,"maker":11,"domain":10,"tier":19,"attempts":32,"strip":219,"url":9,"mix":220,"praise":-1,"objection":85,"sub":21},17463015,-0.53,[24,25,26,27,28],"10101010310101",[32,33,32,34],1794036567496]