|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
per-user directories for obexapp-serverHello!
I was able to set up the Bluetooth-server on my main machine, but all of the pushed files (Object Pushed) end up in the same root-only directory... Is there, perhaps, a way to specify a different directory for each device-ID (bdaddr)? This way my wife and myself could have our own locations (under home-directories somewhere) for pictures and phonebook backups... Please, advise. Thanks! Yours, -mi P.S. Maybe, the hcsecd.conf's syntax can be extended to (optionally) provide the username associated with each listed device? _______________________________________________ freebsd-bluetooth@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..." |
|
|
Re: per-user directories for obexapp-serverOn Thu, Apr 9, 2009 at 12:47 PM, Mikhail T. <mi+thun@...> wrote:
> Hello! > > I was able to set up the Bluetooth-server on my main machine, but all of > the pushed files (Object Pushed) end up in the same root-only > directory... Is there, perhaps, a way to specify a different directory > for each device-ID (bdaddr)? not at the moment, no. > This way my wife and myself could have our own locations (under > home-directories somewhere) for pictures and phonebook backups... > Please, advise. Thanks! Yours, > > -mi > > P.S. Maybe, the hcsecd.conf's syntax can be extended to (optionally) > provide the username associated with each listed device? technically, nothing prevents you from running 2 or more instances of obexapp on different rfcomm channels. each instance would use different root directory. this way each of you can use service on different rfcomm channel to push data into appropriate root directory. i guess its possible to teach obexapp about mapping between client's bdaddr and root directory. ideally, of course, what we want it to have credentials passed over obex connection so the server knows exactly who is talking to it, but that, of course, will likely never happen :) thanks, max _______________________________________________ freebsd-bluetooth@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..." |
|
|
Re: per-user directories for obexapp-serverOn Thu, 9 Apr 2009, Mikhail T. wrote:
> I was able to set up the Bluetooth-server on my main machine, but all of > the pushed files (Object Pushed) end up in the same root-only > directory... Is there, perhaps, a way to specify a different directory > for each device-ID (bdaddr)? One trouble with bluetooth is that there is no finer identification than 'device id', so a multi-user system ends up allowing access by any user to all known devices. This could likely be worked out, I had some ideas about passing credentials around in the kernel to enable marking baseband links as private, and having link keys stored in users home directories but I'm not sure the effort required would be worth it as most systems (with bluetooth) are single-concurrent-user anyway. In the meantime I would suggest something like having a ttyaction(5) mechanism to arrange something like mount -t null -o mount /var/obex ${HOME}/obex for the user logged in on the console, so that incoming files are stored the logged in users directory (or /var/obex if nobody is logged in at the console). iain _______________________________________________ freebsd-bluetooth@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..." |
| Free embeddable forum powered by Nabble | Forum Help |