Quote:
Originally Posted by KraHen
Seriously, before using the expression "named pipes" at least do a bit of research on what they are because you clearly have no idea. Named pipes are only for LOCAL process communicaton, not over a network, so the only thing that can intercept it is a virus (most probably a kernel level one) intercepting the Win/Unix/Whatever API calls.
TL;DR version - NO
Please, for your own good, think 5 times before posting a question next time.
|
Thanks, you helped with your answer.
Quote:
|
so the only thing that can intercept it is a virus (most probably a kernel level one) intercepting the Win/Unix/Whatever API calls.
|
Well, i am learning, i just read the thread where i asked for help before and i noticed now the part saying "NamedPipes are only for local network"...
I am not even close to a professional level and i am reading articles and studying, i also missed this
Quote:
|
Named pipes can be used to provide communication between processes on the same computer or between processes on different computers across a network. If the server service is running, all named pipes are accessible remotely. If you intend to use a named pipe locally only, deny access to NT AUTHORITY\NETWORK or switch to local RPC.
|
On Microsoft post, and it's working using Hamachi IP, so it's fine, i wouldn't host a server in USA and China to use a Named Pipe. Thanks anyway, i had a doubt, i don't need to think 5x before asking a question, because if i did it, it's because i needed someone to explain it better.
You still on your quest to be a moderator? Because, i don't know, but i think you're doing it wrong.
Quote:
Originally Posted by Best Coder 2014
|
If you don't have nothing useful to say, don't reply, its simple.
It's a discussion forum, not the general conversation for trolling.
Maybe you're the best coder and the most asshole coder of the forum.
Who's good, doesn't quit trying to pull peoples down