Securing Remote Procedure Calls over HTTPS

TL;DR

This paper presents a method to enhance the security of Remote Procedure Calls by tunneling them through HTTPS, leveraging SSL for encryption and server authentication to protect data transmission over the internet.

Contribution

It introduces a secure RPC tunneling approach over HTTPS that utilizes SSL for encryption and server authentication, improving remote communication security.

Findings

RPC over HTTPS effectively encrypts data traffic.

SSL ensures server authenticity during RPC communication.

The method enhances security without significant performance loss.

Abstract

Remote Procedure Calls (RPC) are widely used over the Internet as they provide a simple and elegant way of interaction between the client and the server. This paper proposes a solution for securing the remote procedure calls (RPC) by tunneling it through HTTPS (Hypertext Transfer Protocol over Secure Socket Layer). RPC over HTTP actually uses the Secure Socket Layer (SSL) protocol as a transport for the traffic. SSL mandates that the server authenticates itself to the client using a digital certificate (and associated private key). SSL is normally configured to encrypt traffic before transmitting it between the server and client and vice versa.