public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] pin less obex file transfer
Date: Thu, 06 Sep 2007 11:20:33 +0200	[thread overview]
Message-ID: <1189070433.7318.26.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <20070906105703.d2e79f4d.marco.milanesi@iaki.it>

Hi Marco,

>     I have the need to transfer files from PC to mobile without inserting the pin code in the mobile.
> 
> it has to be done only via command line, I have tried to disable in /etc/bluetooth/hcid.conf the param:
> 
>     - security none
> 
> with no success (it always asks the pin number)
> 
> as a side note, with kfbtobex kde graphic application I was able to transfer file without authentication to the mobile

wild guess is that you used the wrong RFCOMM channel number. Make sure
you use the Object Push channel retrieved via SDP and not some static
magic. If the phone requires a PIN you can't do anything about it.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-09-06  9:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06  8:57 [Bluez-users] pin less obex file transfer Marco Milanesi
2007-09-06  9:20 ` Marcel Holtmann [this message]
2007-09-06  9:33   ` Marco Milanesi
2007-09-06  9:53     ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1189070433.7318.26.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox