fedotovcorp
Does it matter how the cryptographic keys stored?
Remme PKI (d) protocol – How to join the DLT network that stores public keys
Machine Identity for IoT Communications
Contest on Gitcoin: a cybersecurity solution for smart home data communication
Re:Remme API – store public key of your certificate on the PKI (d) blo...
on Tuesday March 05, 2019 @05:44AM (#19309661)
Thanks! Did you try it? Can you share your feedback is this API useful for your goals?
Remme API – store public key of your certificate on the PKI (d) blockchain
Bounty Program – Smart Home Solution Based on Remme Protocol
Beta Invite-Only test program of the certificate management tool
Keyhub – Certificate lifecycle management beta test program
Remme – A Java Integration Library for PKI (D) Protocol
Open Source Java Library for Distributed PKI Protocol
Remme – Blockchain-Based Protocol for Public Keys Management
What is the best way to protect machine identity (IoT device ID)?
Hi, everyone. What are the best approaches to make a secure inter-device connection? As I get they both needs have Machine ID that binds with Initial Device Identifier (IDevID) or Locally Significant Device Identifiers (LDevIDs) through digital SSL/TLS certificates. Is it enough for protection against MITM attacks?
Remme protocol – an open source distributed storage for cryptographic keys
Information monoculture challenge: policy-based vs. reputation-based trust
Securing IoT devices connections with blockchain: does it make sense?
Telegram bot to test protocol storing public keys on blockchain
Distributed PKI: Development and Use Cases
Re:Can we merge Certificate Transparency with blockchain?
on Wednesday January 23, 2019 @05:40AM (#18977182)
> Running a permissioned blockchain is nontrivial.
You are right. It's needed a relevant BFT protocol, a lot of work with masternodes community and smart economic system inside. You can look at an example of a such protocol: https://github.com/Remmeauth/remme-core/tree/dev
Re:Can we merge Certificate Transparency with blockchain?
on Tuesday January 22, 2019 @06:57AM (#18967634)
Thanks for the references! The main issue isn't the support and maintenance of a such distributed network, but its integration with current solutions and avoiding centralized middleware services that will weaken the schema described in the documents.
Can we merge Certificate Transparency with blockchain?
REMChain proof-of-service consensus for PKI (d)
Re:REMME – A blockchain-based protocol for issuing X.509 client certif...
on Thursday January 17, 2019 @06:43AM (#18930037)
You are right. There are a lot such ideas of implementations for DNS, CA level etc. For authentication, there are also field to try it, but of course, blockchain isn't a solution that would fit everywhere.
Re:REMME – A blockchain-based protocol for issuing X.509 client certif...
on Thursday January 17, 2019 @06:41AM (#18930029)
The answer about the auth process with current protocol was written above.
Re:REMME – A blockchain-based protocol for issuing X.509 client certif...
on Thursday January 17, 2019 @06:39AM (#18930024)
It depends on how you estimate CA vulnerability and how much your organization ready to trust it. There are enough cases when important auth info was leaked.
REMME – JavaScript SDK for Distributed PKI Solution
Re:REMME – A blockchain-based protocol for issuing X.509 client certif...
on Wednesday January 16, 2019 @11:42AM (#18922327)
We understand your pain related to difficulties to get started with blockchain protocols. One of our goals actually makes it as easy as possible to interact with. Unfortunately, the time that we invest in such adaptation isn't enough, but we have tight terms for our roadmap realization.
Re:REMME – A blockchain-based protocol for issuing X.509 client certif...
on Monday January 14, 2019 @04:55AM (#18901914)
Why does user need to hand over its private key? It obviously breaks the security policy.