Custom Query (98 matches)

Two prospective issues related to password-based login to ops.utah.geniracks.net:

1. Remote password-based SSH login to my user account (chaos) succeeds. Is there a plan to protect against password-guessing attacks on user accounts, which can be shared with site admins?
2. Since /etc/ssh/sshd_config contains:

   PermitRootLogin yes
   

   I am concerned that password-based root login may in fact be permitted on ops. Is that the case? If so, could this setting be changed to without-password?

There is a rack requirement that site admins be able to figure out where the software installed on their rack came from. In looking at boss.utah.geniracks.net (performing IG-MON-1 step 1), i was able to track down most things, but have the following three caveats in terms of tracking system binaries back to source code:

1. Since Emulab system binaries are installed by a make install type process, the easiest way to verify where they came from (that i can think of) is to md5 the binary and compare it to a binary in an .../obj tree whose corresponding .../src tree is known. On boss right now, that tree seems to be /users/stoller/testbed/{src,obj}. So that works well, but i had to make a guess about where the tree was likely to be. Are you planning a standard location for the {src,obj} from which each rack's Emulab software will be installed, or will it vary?
2. If the OS base install had been upgraded, i could do the same thing for verifying FreeBSD base system software by looking in /usr/{src,obj}. However, right now, boss has a FreeBSD base install, so there is no base software in /usr/obj. Does FreeBSD provide a standard solution for this, or do they assume that anyone who cares what version they're running has recompiled their base and thus has something in /usr/obj? Any thoughts?
3. Some software on the system comes from FreeBSD packages, which i believe are created by Utah. Is the source/patches/etc used to create those packages available somewhere?

In testing IG-MON-1 step 6, i wanted to identify the source of the following files from the FEDORA15-OPENVZ-STD image, which are part of Emulab:

/usr/local/etc/emulab/emulab-syncd
/usr/local/libexec/pubsubd

As a site administrator at a rack that contains an image like:

/usr/testbed/images/FEDORA15-OPENVZ-STD.ndz

how can i determine what version of Emulab was installed on this image?