pangdudu-ruby-dbus 0.1.0 → 0.2.1

data/README.rdoc

@@ -1,111 +0,0 @@
-= Ruby D-Bus -> ffwd
-
-Ruby D-Bus provides an implementation of the D-Bus protocol such that the
-D-Bus system can be used in the Ruby programming language.
-
-
-This is my personal dev-fork of mvidners upstream.
-
-If you'd like to contrib to this fork, let me know.
-
-
-
-Most of my work here is actually for another project: http://github.com/pangdudu/robots/tree/master
-
-I might also start writing a less ugly version of: http://github.com/pangdudu/ruby-dbus-daemon/tree/master 
-
-If you know of a nice custom-dbus-daemon let me know. Still thinking about writing
-a dbus spec compliant server/daemon implementation in (pure) Ruby, so that I can
-play around with the network and authentification more easily.
-
-Oki, will clean up a little now. :)
-
-Peace.
-
-== Requirements
-
- * Ruby 1.8 (>= 1.8.6?)
-
-== Installation
-
-  sudo gem install pangdudu-ruby-dbus --source=http://gems.github.com
-
-== Features
-
-Ruby D-Bus currently supports the following features:
-
- * Connecting to local buses.
- * Accessing remote services, objects and interfaces.
- * Invoking methods on remote objects synchronously and asynchronously.
- * Catch signals on remote objects and handle them via callbacks.
- * Remote object introspection.
- * Walking object trees.
- * Creating services and registering them on the bus.
- * Exporting objects with interfaces on a bus for remote use.
- * Rubyish D-Bus object and interface syntax support that automatically
-   allows for introspection.
- * Emitting signals on exported objects.
- 
- * Connection to a local or remote bus over TCP/IP
- * Authentification mechanisms working now: External,CookieSHA1
-
-== Usage
-
-=== Basics:
-
-View a tutorial online on http://trac.luon.net/data/ruby-dbus/tutorial/.
-
-
-=== TCP/Remote stuff:
-
-Take a look at 'config/remote.session.dbus.conf' and start 'config/start_dbus_session.sh'.
-
-You can now try and run one of the tests e.g. 'test/simple_socket_test.rb'.
-
-
-=== Problems you'll have with 'CookieSHA1' when using it remotely: 
-
-Unless we [including you :)] write a funkier SASL authentification mechanism that
-makes sense when using it over-wire, we're stuck with the cookie auth.
-
-Works like this: 
-
-There is a file in '~/.dbus-keyrings' named 'org_freedesktop_general'. 
-It is '-rw-------' so that only you can read it (if you change the permissions, 
-dbus-daemon will most likely ignore the file leaving you with 'External', which is
-even worse remotely). It's kind of a secret key you use to auth against yourself 
-later on.
-
-If you take a look at 'dbus/auth.rb line 40+' you'll see the problem:
-
-  # Search cookie file for id
-  path = File.join(ENV['HOME'], '.dbus-keyrings', context)
-  
-So if you're starting 'config/start_dbus_session.sh' on one host and 'config/start_dbus_session.sh'
-on another one, you'll need to make sure that the content in '~/.dbus-keyrings/org_freedesktop_general'
-is the same on both machines, in order for the 'CookieSHA1' auth to work.
-
-Not cool. I can think of hacks with nfs,smb or fuse:sshfs making it less
-painful to use. 
-
-The file content also get's updated every 5 minutes (when a client fails to auth etc.). 
-Making copy and paste from one shell to another very frolic.
-
-To sum it up: 
-
-Today it's acceptable to use it like this, but until next week we'll need an easy 
-auth mechanism that works on the wire. 
-
-
-more infos:
-  http://dbus.freedesktop.org/doc/dbus-specification.html#auth-mechanisms
-  http://lists.freedesktop.org/archives/dbus/2007-June/008067.html
-
-Booyaa.
-
-== License
-
-Ruby D-Bus is free software; you can redistribute it and/or modify it
-under the terms of the GNU Lesser General Public License as published by the
-Free Software Foundation; either version 2.1 of the License, or (at
-your option) any later version.

data/config/remote.session.dbus.conf

@@ -1,39 +0,0 @@
-<!-- This configuration file controls the per-user-login-session message bus.
-     Add a session-local.conf and edit that rather than changing this 
-     file directly. -->
-
-<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-Bus Bus Configuration 1.0//EN"
- "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
-<busconfig>
-  <!-- Our well-known bus type, don't change this -->
-  <type>session</type>
-
-  <!-- If we fork, keep the user's original umask to avoid affecting
-       the behavior of child processes. -->
-  <keep_umask/>
-
-<!--  <allow_anonymous/> -->
-  
-  <!-- Listen to everything on tcp! -->
-  <listen>tcp:host=0.0.0.0,port=2687,family=ipv4</listen>
-  <!-- Listen on socket at this file location -->
-  <listen>unix:path=/tmp/socket_test_session_bus_socket</listen>
-  
-  <standard_session_servicedirs /> 
-
-  <policy context="default">
-    <!-- Allow everything to be sent -->
-    <allow send_destination="*" eavesdrop="true"/>
-    <!-- Allow everything to be received -->
-    <allow eavesdrop="true"/>
-    <!-- Allow anyone to own anything -->
-    <allow own="*"/>
-  </policy>
-
-  <!-- raise the service start timeout to 40 seconds as it can timeout
-       on the live cd on slow machines -->
-  <limit name="service_start_timeout">60000</limit>
-
-  <include if_selinux_enabled="yes" selinux_root_relative="yes">contexts/dbus_contexts</include>
-
-</busconfig>

data/config/start_dbus_session.sh

@@ -1,2 +0,0 @@
-#!/bin/bash
-dbus-daemon --print-address --config-file=remote.session.dbus.conf

data/test/simple_socket_test.rb

@@ -1,27 +0,0 @@
-#!/usr/bin/ruby
-
-require 'rubygems'
-require 'rofl'
-require 'dbus'
-
-=begin
-puts "NOW LISTING SYSTEM BUS:\n"
-
-#show services on system bus
-sysbus = DBus::SystemBus.instance
-puts "\tsystem bus - listnames:"
-sysbus.proxy.ListNames[0].each { |name| puts "\t\tservice: #{name}" } unless sysbus.nil?
-=end
-#test sockets
-
-puts "NOW LISTING SESSION BUS:\n"
-
-#show services on a tcp session bus
-#socket_name = "unix:path=/tmp/socket_test_session_bus_socket" #look at: config/remote.session.dbus.conf
-#socket_name = "tcp:host=0.0.0.0,port=2687,family=ipv4" #look at: config/remote.session.dbus.conf
-socket_name = "tcp:host=10.11.12.13,port=2687,family=ipv4" #look at: config/remote.session.dbus.conf
-dlog "\tsession socket name: #{socket_name}"
-DBus.const_set("SessionSocketName", socket_name) #overwrite the modules constant
-sesbus = DBus::SessionBus.instance
-dlog "\tsession bus - listnames:"
-sesbus.proxy.ListNames[0].each { |name| dlog "\t\tservice: #{name}" } unless sesbus.nil?