Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - dukat

Pages: [1]
Users / Multiple Interfaces on Core
« on: January 11, 2008, 04:26:28 pm »

I've added a new (faster) Interface on the core, and I want to change the internal one. It used to be eth0, but now it's eth2. How can I change that on the web page? Even better, how can I have both networks configured as internal networks?

Say something like this: eth0 - 192.168.80.x; eth2: 192.168.81.x - both should be served as the internal ones. Any advice?

Installation issues / Samba Authentication and export Issue??
« on: January 06, 2008, 11:32:17 pm »

I've set up a dedicated core with two password-protected users, "dukat" and "trine".

When I connect to the core via a regular PC, I can see four shares: home, public, dukat, and trine.
So user "dukat" should not be able to see "trine"'s files. But there's also the "home" export on the core and as the share level in smb.con on the core is set to "user", every valid Pluto user can access this. And here he gains access to all home folders on the core. Not only can "dukat" access "trine"'s private files (under /home/user_2) but also access all home directories of all system users that might have been created outside of Pluto! What's the home export for anyway? Does LinuxMCE use it? Otherwise it should be disabled.

Is this behaviour intended? I hardly can believe that, so I would call this a serious security bug. Maybe my configuration is messed up, in case here's my core's smb.conf:

Code: [Select]
## @FileType: Pluto Sectioned Config File ##
## @Version: 1 ##
## @KeepSections: ##
## @RemoveSections: ##

## BEGIN : Domain and Hostname

        workgroup = LinuxMCE
        server string = dcerouter
        netbios name = dcerouter

## END : Domain and Hostname
        smb ports = 139
        log level = 2
        invalid users = root
        log file = /var/log/samba/log.%m
        max log size = 1000
        syslog = 0
        encrypt passwords = true
        socket options = TCP_NODELAY
        dns proxy = no
        passwd program = /usr/bin/passwd %u
        passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n .
        username map = /etc/samba/usermap.txt
        unix extensions = yes
        security = user

        comment = public files
        browseable = yes
        writable = yes
        create mask = 0777
        directory mask = 0777
        path = /home/public/data
        public = no
        follow symlinks = yes
        wide links = yes

        comment = shared home files
        browsable = yes
        writable = yes
        path = /home
        public = no
        guest ok = no
        force user = root
        force group = public
        create mask = 0774
        directory mask = 0775
        inherit acls = yes
        inherit uid = yes
        inherit owner = yes
        inherit permissions = yes

## BEGIN : User Shares

                comment = dukat's private files
                browseable = yes
                writable = yes
                create mask = 0770
                directory mask = 0770
                path = /home/user_1
                public = no

                comment = trine's private files
                browseable = yes
                writable = yes
                create mask = 0770
                directory mask = 0770
                path = /home/user_2
                public = no

## END : User Shares

## BEGIN : InternalStorageDevices

## END : InternalStorageDevices

Installation issues / [Fixed] Core-only install won't autostart
« on: October 23, 2007, 10:24:11 pm »

after I installed a dedicated core, I would like to have it autostart on every boot. According to the install wiki, a text mode GUI should appear on boot, but it doesn't at my system. Instead, I have to log into my system, start X automatically, and then launch the core. I'd much appreciate a core without X, so the console GUI would be perfect. Any ideas?


Installation issues / Linux Orbiter available like in Windows?
« on: October 23, 2007, 10:20:25 pm »

I've got a dedicated core running and would like to use it from my normal Kubuntu desktop. I don't see the point in rebooting over the network, and have kubuntu again, just to watch some pictures.

I think the Windows orbiter is a fine idea. Just download it and go. Why doesn't this exist for Linux? I know I can install the Linux MD on kubuntu from the LMCE install CDs (after it detects a running core, it allowsn me a MD installation), but this changes my whole system! It deinstalls aptitude and a lot of other stuff, and I had to manually get my system back to normal!

There are a lot of .debs on the Linux install CD, isn't there just one I can install and have an orbiter without my system turned upside down?

Pages: [1]