[Nfd-dev] Running NFD without sudo

[Ivan Yeo]

Awesome! I’ll look into that first thing tomorrow. Thanks team!

Cheers,
Ivan

> On Jan 19, 2015, at 9:50 PM, Alex Afanasyev <alexander.afanasyev at ucla.edu> wrote:
> 
> There are exactly 2 settings that require superuser privileges: 
> - location of unix socket: this does not exist in Android environment and TCP socket must be used instead.  In the compiled code (nfd-android.tar.gz), both nfd.conf and client.conf are already configured (etc/ndn/client.conf).
> - ethernet support: this is not supported on Android for now and the whole section needs to be removed from nfd.conf
> 
> ---
> Alex
> 
>> On Jan 19, 2015, at 9:29 PM, Ivan Yeo <ivanyeo at CS.UCLA.EDU> wrote:
>> 
>> Hi Steve,
>> 
>> Thanks for pointing that out. I think I've connected the dots. I changed the 'unix_socket' in both nfd.conf and client.conf to point to a file in my home directory and I now I am able to run NFD & NRD without the need for sudo. As a simple test, I ran the producer and consumer example programs on the ndn-cxx examples and all is working now (with and without sudo).
>> 
>> Right now, I'm trying to eliminate all API calls or access that require super user privileges in hope that I can just pop the NFD binaries over to the Android and run it from within a user process container. I've gone through the settings of nfd.conf and turned off all settings that require super user privileges. Off the top of your head, are there other configurations or API calls that you know of that might need elevated privileges? 
>> 
>> Cheers,
>> Ivan
>> 
>> 
>> 
>> ----- Original Message -----
>> From: "Steve DiBenedetto" <dibenede at cs.colostate.edu>
>> To: "Junxiao Shi" <shijunxiao at email.arizona.edu>
>> Cc: "<nfd-dev at lists.cs.ucla.edu>" <nfd-dev at lists.cs.ucla.edu>, "Ivan Yeo" <ivanyeo at cs.ucla.edu>, "Steve DiBenedetto" <dibenede at cs.colostate.edu>
>> Sent: Monday, January 19, 2015 6:02:14 PM
>> Subject: Re: Running NFD without sudo
>> 
>> 
>> What's your client.conf look like? Also, does your current configuration work if you use sudo? 
>> 
>> 
>> On Mon, Jan 19, 2015 at 6:57 PM, Junxiao Shi < shijunxiao at email.arizona.edu > wrote: 
>> 
>> 
>> 
>> 
>> 
>> ---------- Forwarded message ---------- 
>> From: Ivan Yeo < ivanyeo at cs.ucla.edu > 
>> Date: Mon, Jan 19, 2015 at 4:49 PM 
>> Subject: Running NFD without sudo 
>> To: Junxiao Shi < shijunxiao at email.arizona.edu > 
>> 
>> 
>> Hi Junxiao, 
>> 
>> I have managed to get NFD to run on Mac OS 10.10 Yosemite by changing the following settings in /usr/local/etc/ndn/nfd.conf: 
>> 
>> face_system 
>> { 
>> ; The unix section contains settings of UNIX stream faces and channels. 
>> unix 
>> { 
>> listen no; set to 'no' to disable UNIX stream listener, default 'yes' 
>> path /var/run/nfd.sock ; UNIX stream listener path 
>> } 
>> 
>> udp 
>> { 
>> mcast no; set to 'no' to disable UDP multicast, default 'yes' 
>> mcast_port 56363 ; UDP multicast port number 
>> mcast_group 224.0.23.170 ; UDP multicast group (IPv4 only) 
>> } 
>> } 
>> 
>> However, right now, NRD cannot seem to be able to connect to the running NFD. I'm wondering if happened to turn off something that is required by the NRD. I'm still diving deeper to understand how the NRD is connecting to the NFD by looking into the code base. I was wondering if you happen to know where I should start looking to expedite the process? 
>> 
>> Thanks! 
>> 
>> Cheers, 
>> Ivan 
>> 
>> _______________________________________________
>> Nfd-dev mailing list
>> Nfd-dev at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>