From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SSL and L2CAP
Date: Fri, 09 Jun 2006 09:06:11 +0200 [thread overview]
Message-ID: <1149836771.6618.1.camel@localhost> (raw)
In-Reply-To: <BAY18-F204E0C80858C7BCEF24318D6880@phx.gbl>
Hi Ali,
> my question is similar to:
> http://sourceforge.net/mailarchive/message.php?msg_id=7257931
>
> I have an L2CAP application, and I was wandering if I could apply SSL to
> L2CAP sockets?
>
> I am new at SSL, my understand is that it should be working with most of the
> socket types. However, my search for information led me to the link above
> and there is no answer to it.
I never had to deal with SSL progamming in detail. So in general you can
do everything over L2CAP. However the L2CAP is a SOCK_SEQPACKET and not
a SOCK_STREAM like TCP. If you need a SOCK_STREAM you must use a RFCOMM
socket.
Regards
Marcel
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-06-09 7:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 3:34 [Bluez-devel] SSL and L2CAP Ali BT
2006-06-09 7:06 ` Marcel Holtmann [this message]
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=1149836771.6618.1.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@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;
as well as URLs for NNTP newsgroup(s).