Skip to main content

Samba4 and Windows ADS interoperability!



Last night I've been busy setting up the Samba4 on my VMware Workstation. Installation went fine. I'll add the print screens and the rest later. We will also try to start playing with ADS and trying to pump all data, migrate users and the rest , bring the Windows PDC down and activate our Linux directory.

More coming soon...(as in tonight ;-))

Where do I get it?

OK A quick look at the installation. Remember a couple of things. This is a TP (Technology Preview), so don't go rushing into your environment and upgrading your Samba3 yet. Wait. Hey that's why we have VMware machines. No harm at all. We'll even make a copy of a sample ADS in VMware and do some fun stuff.

But OK first setting it up.

  • Unzip it (tar xzvf ...)
  • Go to the source directory.



  • Run ./autogen (see below). Since this is no release yet, you have to generate scripts by hand.
  • and then ./configure


  • Checking...


  • make proto all (if your GCC version is above 3.4 you can do it a lot faster (five times faster they say) then do make pch all



  • Time to install



  • And then Provision...






  • Creating a simple smb.conf

The provisioning will do that with no shares so you need to make one here yourself.


[myshare]
path = /tmp/test
read only = no

  • Starting Samba4


The easiest to just run "smbd", but a curious soul will do this inadvertently

# smbd -i -M single

This will "start" smbd without messages in stdout, and running a
single process. That mode of operation makes debugging smbd with gdb
easy.

Also note that you don't need to have an Samba3 nmdb instance running. So if you are running any , stop them before you start Samba4.

Make sure you put the bin and sbin directories from your new install
in your $PATH. Actually you should do that already before provisioning!

Next we'll continue testing and playing around ADS and even go to lengths of pumping the life(data) out of Windows PDC and shutting it down and replacing it with Linux based PDC.

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op
Post a Comment
Read more