public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Kartikey Parmar <kartikey2781@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Query: using obexftp application with no pin
Date: Thu, 26 Feb 2009 15:40:48 +0530	[thread overview]
Message-ID: <6887eb5d0902260210q100eca7bnfea66422ec61e58d@mail.gmail.com> (raw)

hi

Is it possible to send file using obexFTP by just accepting the
request to receive at the far end?

Just like it is possible to send ringtone / .jpg file from 1 bluetooth
enable mobile to another bluetooth enable mobile by just discovering
it and sending the selected file to it.
At the destination end user just needs to click on yes to accept data
from remote device.

In that case pairing is not required, that means neither side it
prompts to enter pin and on successful completion of the operation the
received file will be there in Received Files folder on the
destination bluetooth enable mobile phone.

I have written an file transfer application using openObex and obexFTP
functions which performs similar function.

In my application I did prompt user for any type of PIN / passkey,
still when my application attempts to connect with remote device it
prompt to enter PIN on the remote device and on successful submission
of PIN, bluez-gnome utility prompts me to enter PIN.

If both PIN are matches, it creates bonding and then I can have file
transfer between these two.

Is it possible to disable this PIN request and connection without any
PIN / linkkey? i.e. is it possible to exchange files withough bonding?

I m using openObex-1.5, obexFTP-0.23 and bluez-4.30 on Fedora 9

Awaiting for reply...

-- 
Kartikey Parmar
R&D Software Engg
Matrix Telecom Pvt Ltd
Baroda, Gujarat (India)
09879095390 (M)

                 reply	other threads:[~2009-02-26 10:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=6887eb5d0902260210q100eca7bnfea66422ec61e58d@mail.gmail.com \
    --to=kartikey2781@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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