Hey no problem! Should I still open that issue? Seems like you have one made already (<a href="https:&#x2F;&#x2F;github.com&#x2F;sadasystems&#x2F;private-message&#x2F;issues&#x2F;5" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;sadasystems&#x2F;private-message&#x2F;issues&#x2F;5</a>).<p>I ended up doing this for a project that I wanted to have use RSA for large chunks of data, for sending it was:<p>1. Generate random AES cipher key (I used a 16 byte key) using any available <i>secure</i> rng (it all depends on where the thing gets it&#x27;s entropy, I think node&#x27;s crypto.getRandomBytes is supposed to be strong)<p>2. Pad &amp; Encrypt  data with AES<p>3. Encrypt randomly-generated key with RSA<p>4. Send the message in an envelope like: {key: &lt;RSA encrypted AES key&gt;, data: &lt;AES encrypted data&gt;}<p>For me, the devil was in the details -- padding took an especially long time for me to understand and solve (the thing I was working on was cross platform, so ruby-&gt;js or python-&gt;ruby, and of course not all implementations pad the same way), but once that was solved, most other things were easy. The node part was also particularly troubling because I had to deal with the way to specify encodings in node, which was kind of confusing (I spent a lot of time messing with base64&#x2F;binary encoding and having my terminal start showing gibberish when I tried to print binary data)<p>I don&#x27;t have access to that code now (I actually wrote it in order to get around the fact that internal networks at a certain company I used to work at didn&#x27;t have a custom rootCA&#x2F;support TLS properly), otherwise I&#x27;d just post it.<p>Would love to help with the implementation though