I frequently run ssh-agent with its socket created at a different
location than the default one. When one does a ps command, one can see
where the socket has been created.
Would it be possible to do things in such a way that ps does not
reveal this information? I seem to remember coming across applications
that would prevent that from happening - that is, after processing they
would mangle their command line arguments so that ps would only print out
a string of x's, or something like that, in their stead.
.
Re: problem with Socket.Available ... > I try to implement a reusable socket class to send and receive data. ... you will find the code for this class (TcpHelper).... probably connection closed by peer");... > (command, bytesRead, ... (microsoft.public.dotnet.languages.csharp)
Re: CANNOT receive UDP data in SERVICE program ... UDP" is really a powerful command I didn't know before. ... Broadcast online request which brings local command socket port... Call setsockopt to set a 5000ms TIMEOUT option on #SOCK1;... In fact I can see the command data in Sniffer, ... (microsoft.public.win32.programmer.networks)
Re: CANNOT receive UDP data in SERVICE program ... After downloading a SERVICE source code and copy my codes into it, ... UDP" is really a powerful command I didn't know before. ... Broadcast online request which brings local command socket port... In fact I can see the command data in Sniffer, ... (microsoft.public.win32.programmer.networks)
Re: CANNOT receive UDP data in SERVICE program ... UDP" is really a powerful command I didn't know before. ... Broadcast online request which brings local command socket port... Call setsockopt to set a 5000ms TIMEOUT option on #SOCK1;... In fact I can see the command data in Sniffer, ... (microsoft.public.win32.programmer.networks)
Re: ssh-agent and Linux ... where the socket has been created. ... when the "netstat" command can give out the ... Is it not the case that with netstat you need root privileges in ... (comp.security.ssh)
