On Mon, Mar 6, 2017 at 8:46 AM, Constantine <[email protected]> wrote:
> Hi Thank you :)
> I don't have such knowledge, unfortunately.
> We are using this for a simple chat application and we create a different
> key for each user through a KDF process. So all data will be encrypted and
> decrypted with this key for each user.
>
In your case, you might want to basically encrypt the serialized protocol
buffer messages. E.g.
message PlainChatMessage {
string text = 1;
int ....
}
// define your RPC request and responses using this message
message EncryptedChatMessage
{
bytes encrypted_data = 1;
}
>
> It will be good that we gRPC add a layer of custom encryption? (I don't
> know how hard it is or how much effort it will take.)
>
> On Monday, March 6, 2017 at 11:04:47 AM UTC+3:30, Jan Tattermusch wrote:
>>
>> Hi, something like this can be implemented by changing the channel
>> internals in gRPC C core. We have an API to add things like that, but
>> expect you'll need a very good knowledge of how gRPC C core works to make
>> this work.
>>
>> Also, why do you need custom encryption at all? gRPC comes with SSL/TLS
>> support built-in and I'd strongly recommend using it instead of trying to
>> come up with your own custom solution.
>>
>> On Mon, Mar 6, 2017 at 8:08 AM, Constantine <[email protected]> wrote:
>>
>>> I have a nodejs server and two android and ios clients. I want to use my
>>> own encryption method to encrypt data at clients and decrypt it at
>>> the server? I mean the following picture:
>>>
>>>
>>>
>>>
>>> <https://lh3.googleusercontent.com/-QYW7AdFlCkk/WL0KzmAo4XI/AAAAAAAAIuo/RjsIbxhWcL4C5F6SAc2XvcdBU2gw5zg8QCLcB/s1600/Untitled%2BDiagram.png>
>>>
>>>
>>> Is it possible?
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "grpc.io" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To post to this group, send email to [email protected].
>>> Visit this group at https://groups.google.com/group/grpc-io.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/grpc-io/e24d1b71-8301-4a57-9b92-7aae1d6e895a%40googlegroups.com
>>> <https://groups.google.com/d/msgid/grpc-io/e24d1b71-8301-4a57-9b92-7aae1d6e895a%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/grpc-io.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/grpc-io/30c26e22-0225-4a21-876d-4265a6f25f74%40googlegroups.com
> <https://groups.google.com/d/msgid/grpc-io/30c26e22-0225-4a21-876d-4265a6f25f74%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/CACF4M0QjrQmGjxGHiUdaKB_Be-7nHjBBiS2A5SqcvZtXnVFctw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
