From owner-freebsd-bluetooth@FreeBSD.ORG  Thu Feb 22 11:50:38 2007
Return-Path: <owner-freebsd-bluetooth@FreeBSD.ORG>
X-Original-To: freebsd-bluetooth@freebsd.org
Delivered-To: freebsd-bluetooth@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 8E8E916A404
	for <freebsd-bluetooth@freebsd.org>;
	Thu, 22 Feb 2007 11:50:38 +0000 (UTC)
	(envelope-from plunky@rya-online.net)
Received: from post.rya-online.net (post.rya-online.net [195.26.225.220])
	by mx1.freebsd.org (Postfix) with ESMTP id 5A2CC13C442
	for <freebsd-bluetooth@freebsd.org>;
	Thu, 22 Feb 2007 11:50:38 +0000 (UTC)
	(envelope-from plunky@rya-online.net)
Received: from rya-online.net (post.rya-online.net [127.0.0.1])
	by post.rya-online.net (Postfix) with SMTP
	id CA8B41D41AE; Thu, 22 Feb 2007 11:50:59 +0000 (GMT)
Sender: plunky@rya-online.net
From: "Iain Hibbert" <plunky@rya-online.net>
To: "Maksim Yevmenkin" <maksim.yevmenkin@gmail.com>
X-Mailer: Quality Web Email v3.1b, http://netwinsite.com/refw.htm
Date: Thu, 22 Feb 2007 11:50:59 GMT
Message-id: <45dd83a3.33a.2350.278725879@rya-online.net>
Cc: freebsd-bluetooth@freebsd.org
Subject: Re: obexapp 1.4.5
X-BeenThere: freebsd-bluetooth@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: plunky@rya-online.net
List-Id: Using Bluetooth in FreeBSD environments
	<freebsd-bluetooth.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>, 
	<mailto:freebsd-bluetooth-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bluetooth>
List-Post: <mailto:freebsd-bluetooth@freebsd.org>
List-Help: <mailto:freebsd-bluetooth-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>, 
	<mailto:freebsd-bluetooth-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Feb 2007 11:50:38 -0000

> > I will look into this a bit more, maybe if I arrange to
> > send() an zero length message before changing the uid it
> > may work, though I'm not sure how well sdpd will handle
> that..
>
> i'm not sure what are you suggesting

My thought was that a zero length message (sent at the end
of sdp_open_local()) would create a message event for sdpd
that only contains the SCM_CREDS message. Thus, we pass the
credentials before they are changed..

I will try it, later..

iain