Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Nigel Wade Newsgroups: comp.lang.java.programmer Subject: Re: java unix domain sockets ... or substitute Date: Thu, 04 Sep 2014 15:57:54 +0100 Lines: 13 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net oE3GPO+7V7Qr1CJ8v72OZgzr2oCZrxbpVnWlWCqo88KPX3iQKS Cancel-Lock: sha1:ah1Vwjwj56gnXcVRcRrWe4UdzZU= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 In-Reply-To: Xref: csiph.com comp.lang.java.programmer:29909 On 04/09/14 15:11, Chris Uppal wrote: > If you must use Unix group permissions, then Nigel Wade's suggestion of having > the server write a random number to a file that only it can write and only they > can read, and using that for validation, seems adequate. But note that that is > vulnerable to network sniffing. Network sniffing ought not to be much of a problem. If the server only listens on the loopback interface then external exploitation shouldn't be possible. A normal user should not be able to sniff the lookback interface, so the attacker would need root access on the local host. If an attacker has root access then all bets are off, and protecting the app. server would be low on the list of priorities.