get bytes from socket data event nodejs The Next CEO of Stack OverflowHow does the socket API accept() function work?C#: How should TCP socket buffer data be handled? As bytes or converted to an ascii string?Receive TCP payloads from socket immediately (packet-by-packet) in CMissing data from socketTCP Packets in Raw socket - Centos 6.6Transferring data through tcp sockets using nodejsDelay in reading TCP socket dataNode.js tcpsocket on('data') eventError writing to nodejs socket (TypeError: Invalid data, chunk must be a string or buffer, not object)TCP sockets: How much incoming data is buffered before calling accept?
Why does the UK parliament need a vote on the political declaration?
Sending manuscript to multiple publishers
Is it my responsibility to learn a new technology in my own time my employer wants to implement?
Elegant way to replace substring in a regex with optional groups in Python?
Why is the US ranked as #45 in Press Freedom ratings, despite its extremely permissive free speech laws?
Received an invoice from my ex-employer billing me for training; how to handle?
Is it possible to search for a directory/file combination?
Why do we use the plural of movies in this phrase "We went to the movies last night."?
How does the Z80 determine which peripheral sent an interrupt?
I believe this to be a fraud - hired, then asked to cash check and send cash as Bitcoin
Preparing Indesign booklet with .psd graphics for print
Anatomically Correct Strange Women In Ponds Distributing Swords
Are there any unintended negative consequences to allowing PCs to gain multiple levels at once in a short milestone-XP game?
"In the right combination" vs "with the right combination"?
Several mode to write the symbol of a vector
Is 'diverse range' a pleonastic phrase?
How to safely derail a train during transit?
If Nick Fury and Coulson already knew about aliens (Kree and Skrull) why did they wait until Thor's appearance to start making weapons?
Unreliable Magic - Is it worth it?
If/When UK leaves the EU, can a future goverment conduct a referendum to join the EU?
Written every which way
If the heap is initialized for security, then why is the stack uninitialized?
Would this house-rule that treats advantage as a +1 to the roll instead (and disadvantage as -1) and allows them to stack be balanced?
What is "(CFMCC)" on an ILS approach chart?
get bytes from socket data event nodejs
The Next CEO of Stack OverflowHow does the socket API accept() function work?C#: How should TCP socket buffer data be handled? As bytes or converted to an ascii string?Receive TCP payloads from socket immediately (packet-by-packet) in CMissing data from socketTCP Packets in Raw socket - Centos 6.6Transferring data through tcp sockets using nodejsDelay in reading TCP socket dataNode.js tcpsocket on('data') eventError writing to nodejs socket (TypeError: Invalid data, chunk must be a string or buffer, not object)TCP sockets: How much incoming data is buffered before calling accept?
I have a kinda weird problem
I've been trying to implement my own tls implementation to be able to connect to a server that is not 100% compliant to the TLSv1.2 specification (the client_random and server_random are not random but generated from a timestamp, and the server forces the client to have the record layer version be tls 1.2 to perform the handshake)
On top of that I needed to send some data in clearText in a protocol similar to http but not http (sts/1.0) before I can start the tls handshake
so I hacked together a implementation to both things, but I'm hitting something that I did not know could happen
when receiving the server's certificate in the tls handshake, the bytes that I see in the buffer I created with Buffer.from(data, "ascii") (yes the socket encoding is also ascii) (and I also tried with utf-8 encoding) were not the ones I was seeing in wireshark and are leading to my x509 parser to fail (if works if I create a buffer from the copy pasted hex stream of the certificate from wireshark). I believe this is a encoding issue, but then what encoding can I use to get the raw bytes in data without having to encode it ?
example:
beginning of certificate message in wireskark:
16:03:03:03:52:0b:00:03:4e:00:03:4b
beginning of certificate message in nodejs encoded in ascii:
16:03:03:00:2a:02:00:00:26:03:03:12
The socket is use is the one from net.Socket
My plan at the time of writing this to solve this issue is to have a low level language act as a proxy, receive the raw bytes, create the ascii representation of those bytes, then send that to my nodejs socket. not the best solution at all but that's all I could find on my own.
PS: if anyone knows a nodejs tls implementation that can accept a specific client_random and/or force the tls record layer version to be 1.2 during the handshake, you would save me tens of hours of developping everything I need.
PS2: I tried to look for a "raw" tcp socket on nodejs to get more control on the data I receive, and there is a "raw-socket" npm package. But from what I saw there is no way to set the port you want to connect to on the server. If anyone used this package before and knows how to set a port in a tcp socket under that package, I'd like to understand how you did it.
thanks for helping!
node.js sockets ssl tcp tls1.2
asked Mar 8 at 14:19
torsinatorsina
214
add a comment |
I have a kinda weird problem
I've been trying to implement my own tls implementation to be able to connect to a server that is not 100% compliant to the TLSv1.2 specification (the client_random and server_random are not random but generated from a timestamp, and the server forces the client to have the record layer version be tls 1.2 to perform the handshake)
On top of that I needed to send some data in clearText in a protocol similar to http but not http (sts/1.0) before I can start the tls handshake
so I hacked together a implementation to both things, but I'm hitting something that I did not know could happen
when receiving the server's certificate in the tls handshake, the bytes that I see in the buffer I created with Buffer.from(data, "ascii") (yes the socket encoding is also ascii) (and I also tried with utf-8 encoding) were not the ones I was seeing in wireshark and are leading to my x509 parser to fail (if works if I create a buffer from the copy pasted hex stream of the certificate from wireshark). I believe this is a encoding issue, but then what encoding can I use to get the raw bytes in data without having to encode it ?
example:
beginning of certificate message in wireskark:
16:03:03:03:52:0b:00:03:4e:00:03:4b
beginning of certificate message in nodejs encoded in ascii:
16:03:03:00:2a:02:00:00:26:03:03:12
The socket is use is the one from net.Socket
My plan at the time of writing this to solve this issue is to have a low level language act as a proxy, receive the raw bytes, create the ascii representation of those bytes, then send that to my nodejs socket. not the best solution at all but that's all I could find on my own.
PS: if anyone knows a nodejs tls implementation that can accept a specific client_random and/or force the tls record layer version to be 1.2 during the handshake, you would save me tens of hours of developping everything I need.
PS2: I tried to look for a "raw" tcp socket on nodejs to get more control on the data I receive, and there is a "raw-socket" npm package. But from what I saw there is no way to set the port you want to connect to on the server. If anyone used this package before and knows how to set a port in a tcp socket under that package, I'd like to understand how you did it.
thanks for helping!
node.js sockets ssl tcp tls1.2
asked Mar 8 at 14:19
torsinatorsina
214
add a comment |
I have a kinda weird problem
I've been trying to implement my own tls implementation to be able to connect to a server that is not 100% compliant to the TLSv1.2 specification (the client_random and server_random are not random but generated from a timestamp, and the server forces the client to have the record layer version be tls 1.2 to perform the handshake)
On top of that I needed to send some data in clearText in a protocol similar to http but not http (sts/1.0) before I can start the tls handshake
so I hacked together a implementation to both things, but I'm hitting something that I did not know could happen
when receiving the server's certificate in the tls handshake, the bytes that I see in the buffer I created with Buffer.from(data, "ascii") (yes the socket encoding is also ascii) (and I also tried with utf-8 encoding) were not the ones I was seeing in wireshark and are leading to my x509 parser to fail (if works if I create a buffer from the copy pasted hex stream of the certificate from wireshark). I believe this is a encoding issue, but then what encoding can I use to get the raw bytes in data without having to encode it ?
example:
beginning of certificate message in wireskark:
16:03:03:03:52:0b:00:03:4e:00:03:4b
beginning of certificate message in nodejs encoded in ascii:
16:03:03:00:2a:02:00:00:26:03:03:12
The socket is use is the one from net.Socket
My plan at the time of writing this to solve this issue is to have a low level language act as a proxy, receive the raw bytes, create the ascii representation of those bytes, then send that to my nodejs socket. not the best solution at all but that's all I could find on my own.
PS: if anyone knows a nodejs tls implementation that can accept a specific client_random and/or force the tls record layer version to be 1.2 during the handshake, you would save me tens of hours of developping everything I need.
PS2: I tried to look for a "raw" tcp socket on nodejs to get more control on the data I receive, and there is a "raw-socket" npm package. But from what I saw there is no way to set the port you want to connect to on the server. If anyone used this package before and knows how to set a port in a tcp socket under that package, I'd like to understand how you did it.
thanks for helping!
node.js sockets ssl tcp tls1.2
asked Mar 8 at 14:19
torsinatorsina
214
I have a kinda weird problem
I've been trying to implement my own tls implementation to be able to connect to a server that is not 100% compliant to the TLSv1.2 specification (the client_random and server_random are not random but generated from a timestamp, and the server forces the client to have the record layer version be tls 1.2 to perform the handshake)
On top of that I needed to send some data in clearText in a protocol similar to http but not http (sts/1.0) before I can start the tls handshake
so I hacked together a implementation to both things, but I'm hitting something that I did not know could happen
when receiving the server's certificate in the tls handshake, the bytes that I see in the buffer I created with Buffer.from(data, "ascii") (yes the socket encoding is also ascii) (and I also tried with utf-8 encoding) were not the ones I was seeing in wireshark and are leading to my x509 parser to fail (if works if I create a buffer from the copy pasted hex stream of the certificate from wireshark). I believe this is a encoding issue, but then what encoding can I use to get the raw bytes in data without having to encode it ?
example:
beginning of certificate message in wireskark:
16:03:03:03:52:0b:00:03:4e:00:03:4b
beginning of certificate message in nodejs encoded in ascii:
16:03:03:00:2a:02:00:00:26:03:03:12
The socket is use is the one from net.Socket
My plan at the time of writing this to solve this issue is to have a low level language act as a proxy, receive the raw bytes, create the ascii representation of those bytes, then send that to my nodejs socket. not the best solution at all but that's all I could find on my own.
PS: if anyone knows a nodejs tls implementation that can accept a specific client_random and/or force the tls record layer version to be 1.2 during the handshake, you would save me tens of hours of developping everything I need.
PS2: I tried to look for a "raw" tcp socket on nodejs to get more control on the data I receive, and there is a "raw-socket" npm package. But from what I saw there is no way to set the port you want to connect to on the server. If anyone used this package before and knows how to set a port in a tcp socket under that package, I'd like to understand how you did it.
thanks for helping!
node.js sockets ssl tcp tls1.2
node.js sockets ssl tcp tls1.2
asked Mar 8 at 14:19
torsinatorsina
214
asked Mar 8 at 14:19
torsinatorsina
214
asked Mar 8 at 14:19
torsinatorsina
214
asked Mar 8 at 14:19
torsinatorsina
214
asked Mar 8 at 14:19
torsinatorsina
214
214
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I used a python proxy to send me the ascii representation of those bytes and everything works. I'm quite frustrated I couldn't find a way to do it in node without having to do a damn .node
answered Mar 8 at 17:40
torsinatorsina
214
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55065097%2fget-bytes-from-socket-data-event-nodejs%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I used a python proxy to send me the ascii representation of those bytes and everything works. I'm quite frustrated I couldn't find a way to do it in node without having to do a damn .node
answered Mar 8 at 17:40
torsinatorsina
214
add a comment |
I used a python proxy to send me the ascii representation of those bytes and everything works. I'm quite frustrated I couldn't find a way to do it in node without having to do a damn .node
answered Mar 8 at 17:40
torsinatorsina
214
add a comment |
I used a python proxy to send me the ascii representation of those bytes and everything works. I'm quite frustrated I couldn't find a way to do it in node without having to do a damn .node
answered Mar 8 at 17:40
torsinatorsina
214
I used a python proxy to send me the ascii representation of those bytes and everything works. I'm quite frustrated I couldn't find a way to do it in node without having to do a damn .node
answered Mar 8 at 17:40
torsinatorsina
214
answered Mar 8 at 17:40
torsinatorsina
214
answered Mar 8 at 17:40
torsinatorsina
214
answered Mar 8 at 17:40
torsinatorsina
214
214
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55065097%2fget-bytes-from-socket-data-event-nodejs%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
