[PATCH] Use safe alignment macros for in-tree SRV record parsing

[Jakub Hrozek]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The in-tree SRV record parsing is used with very old c-ares libraries
that don't implement the parsing themselves (c-ares < 1.7, used in e.g.
RHEL5)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk2kCbwACgkQHsardTLnvCUFigCfTljsGOGwbvPSE3ty6yzdIAVl
> GYUAoNV9GbVVOd2LNLzD59rHBvrKFDPd
> =rn4B
> -----END PGP SIGNATURE-----

[Jan Zelený]

Jakub Hrozek <jhrozek(a)redhat.com&gt; wrote:
>  The in-tree SRV record parsing is used with very old c-ares
> libraries
>  that don't implement the parsing themselves (c-ares < 1.7, used in e.g.
>  RHEL5) 
Ack

Jan

[Stephen Gallagher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/12/2011 04:13 AM, Jakub Hrozek wrote:
>  The in-tree SRV record parsing is used with very old c-ares
> libraries
>  that don't implement the parsing themselves (c-ares < 1.7, used in e.g.
>  RHEL5) 
Is this being proposed for the master branch or also for sssd-1-5?

- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk2kOC4ACgkQeiVVYja6o6PpugCgirl540UdBoHbUwnMBPF0mlfV
> K44AnAjfaeELdeygRLrSdSXPdaWv9nkR
> =0TvY
> -----END PGP SIGNATURE-----

[Jakub Hrozek]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/12/2011 01:32 PM, Stephen Gallagher wrote:
>  On 04/12/2011 04:13 AM, Jakub Hrozek wrote:
> > The in-tree SRV record parsing is used with very old c-ares libraries
> > that don't implement the parsing themselves (c-ares < 1.7, used in e.g.
> > RHEL5)
>  
>  Is this being proposed for the master branch or also for sssd-1-5?
>   
I would rather see this in the stable branch, too. If someone is using a
system that is so old^w stable that it still contains c-ares 1.6, he
will likely be using the stable branch.

The risk is minimal, the macros are the same as c-ares upstream uses.

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk2kOvoACgkQHsardTLnvCUzjwCbB1EFiTSLAcU251054Au9pf7M
> 7SoAn3Tk5DqxafguchF1T2FnBaj7viB6
> =r31R
> -----END PGP SIGNATURE-----

[Stephen Gallagher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/12/2011 07:43 AM, Jakub Hrozek wrote:
>  On 04/12/2011 01:32 PM, Stephen Gallagher wrote:
> > On 04/12/2011 04:13 AM, Jakub Hrozek wrote:
> >> The in-tree SRV record parsing is used with very old c-ares libraries
> >> that don't implement the parsing themselves (c-ares < 1.7, used in e.g.
> >> RHEL5)
>  
> > Is this being proposed for the master branch or also for sssd-1-5?
>  
>  
>  I would rather see this in the stable branch, too. If someone is using a
>  system that is so old^w stable that it still contains c-ares 1.6, he
>  will likely be using the stable branch.
>  
>  The risk is minimal, the macros are the same as c-ares upstream uses.
>   
Pushed to master and sssd-1-5.

- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk2kUz8ACgkQeiVVYja6o6NHtACZAW9Gd+cL+0q00R6ai1jhSQ+G
> OjQAn1Z22D/4SyGcwAOFPg2ercpCvEVH
> =bEaV
> -----END PGP SIGNATURE-----