Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Fredrik Noring <noring@nocrew.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] New keytab storage
Date: Sat, 31 Jan 2004 01:32:50 +0100	[thread overview]
Message-ID: <1075509170.3594.36.camel@pegasus> (raw)
In-Reply-To: <1075506991.14644.114.camel@akka.yeti.nocrew.org>

Hi Fredrik,

> Attached patch implements link key storage in /etc/bluetooth/keytab and
> /etc/bluetooth/keytab.shadow. The old /etc/bluetooth/link_key file is
> converted automatically.

I haven't reviewed the complete patch and at the moment and I am not
convinced in doing such a big change to the old code. But I have some
general comments.

Please send every patch as plain text and not compressed, because this
makes it easy to take a first look at it within the email client. If you
got oversize reports from the mailing list manager, don't worry I will
approve the email by hand.

If you do such a big change show us the output of diffstat so everybody
can see what files are going to be changed.

 Makefile.am |    4 
 Makefile.in |  548 ++++++++++++++++++++++++++++++++++++------------------------
 file.c      |   92 ++++++++++
 file.h      |   18 +
 hcid.h      |   21 +-
 keytab.c    |  459 ++++++++++++++++++++++++++++++++++++++++++++++++++
 keytab.h    |   14 +
 lib.h       |    4 
 main.c      |    2 
 security.c  |  108 ++---------
 10 files changed, 952 insertions(+), 318 deletions(-)

Don't include files that are generated by autoconf/automake. In your
case this is Makefile.in. diffstat or lsdiff helps here to check the
patch for unwanted files.

Follow the coding style. Read the paper from Greg Kroah-Hartman. It is
very good. Here are my notes:

The comment should be above the function declaration. Some goes for any
other statement.

	static int parse_hex_digit(char c)
	       /* Returns binary 0-15 for hex '0'-'a' and '0'-'A'.
	        * Returns -1 for invalid hex digits. */
	{

The parenthese must be behind the "if", "for" and "while" statement.

       fd = open(filename, O_RDONLY);
       if (fd < 0)
       {

Include a whitespace after "if", "for", "while" etc.

       for(;;)
       {

Typedefs are ugly, but if you use them, than the *_t version must match
the structure and not define something complete different.

	typedef uint8_t        link_key_t[16];

	struct link_key {

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-01-31  0:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-30 23:56 [Bluez-devel] [PATCH] New keytab storage Fredrik Noring
2004-01-31  0:32 ` Marcel Holtmann [this message]
2004-01-31  0:55   ` Fredrik Noring
2004-01-31  1:18     ` Marcel Holtmann
2004-01-31  9:27       ` Fredrik Noring
2004-01-31 15:23         ` Marcel Holtmann
2004-01-31 15:40           ` Fredrik Noring
2004-01-31 15:52             ` Marcel Holtmann
2004-01-31 16:03               ` Fredrik Noring
2004-01-31 18:01                 ` Marcel Holtmann
2004-01-31 18:15                   ` Fredrik Noring
2004-01-31 10:47   ` Fredrik Noring

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=1075509170.3594.36.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=noring@nocrew.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