# Regarding the «Noise over TCP (uplink to storage node)» document

**URL:** <https://forum.storj.io/t/regarding-the-noise-over-tcp-uplink-to-storage-node-document/21030>\
**Category:** Node Operators\
**Created:** [January 16, 2023, 12:53am UTC](https://forum.storj.io/t/regarding-the-noise-over-tcp-uplink-to-storage-node-document/21030 "2023-01-16T00:53:05Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jtolio](https://storj.bcdn.literatehosting.com/letter_avatar/jtolio/32/5_5575768a8748004e209b776fc1b2916d.png) [@jtolio](https://forum.storj.io/u/jtolio)\
**Post date:** [January 17, 2023, 9:45pm UTC](https://forum.storj.io/t/regarding-the-noise-over-tcp-uplink-to-storage-node-document/21030/4 "2023-01-17T21:45:16Z")

</div>

> [@BrightSilence](#):
>
> If I understand correctly, this means uplink is sending data before definitive verification that it is talking to the intended node. Probably limited concern as all the data is, is just an encrypted blob, but that makes me feel a little icky. (probably not rational though)

You’re right! But also as you say, the data is encrypted with the storage node’s key, so you would have to have the storage node’s key to be able to decrypt it, which in some sense does provide the secrecy you’d expect if you only wanted to send the data to that node.

> [@BrightSilence](#):
>
> When an uplink requests a transfer from the satellite, it could include a validity timestamp signed by the satellite after which nodes won’t accept the transfer anymore. This could at least shrink the vulnerability window for replay attacks. Downside being that the client itself also has limited time to perform the request.

This is a good idea, and assuming there isn’t too much clock drift in the network, this is probably worth adding to some of the commands that aren’t already protected by Orders/OrderLimits, which essentially provide this functionality already.

Good points!

I just started a new thread for the two design docs in question here: [Two new blueprints/design drafts seeking feedback: Replacing TLS with Noise and TCP\_FASTOPEN](https://forum.storj.io/t/two-new-blueprints-design-drafts-seeking-feedback-replacing-tls-with-noise-and-tcp-fastopen/21053).

---

_[View the full topic](https://forum.storj.io/t/regarding-the-noise-over-tcp-uplink-to-storage-node-document/21030)._