From: Bruno Thomsen <bth@kamstrup.dk>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCHv3] net-snmp: Improved SNMPv3 authentication and privacy support.
Date: Fri, 14 Mar 2014 14:39:21 +0000 [thread overview]
Message-ID: <915054555B5659448ACF8A70E114824DE75F562D@Exchange2010.kamstrup.dk> (raw)
In-Reply-To: <20140313143809.GG20431@pengutronix.de>
-----Original Message-----
From: ptxdist-bounces@pengutronix.de [mailto:ptxdist-bounces@pengutronix.de] On Behalf Of Michael Olbrich
Sent: 13. marts 2014 15:38
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCHv3] net-snmp: Improved SNMPv3 authentication and privacy support.
>On Thu, Mar 13, 2014 at 03:20:26PM +0100, Bruno Thomsen wrote:
>> Enabled SHA authentication and AES privacy (encryption) using OpenSSL.
>> Upgraded from libnl1 to libnl3 dependency, and explicitly request libnl3.
>> Disable minimal agent when privacy is enabled.
>>
>> Tested SNMPv3 with USM (User-based Security Model) SHA auth + AES priv, minimal agent option disabled.
>
>This still doesn't work with nl3:
>
>ptxdist -f clean && ptxdist prepare net-snmp
>
> [...]
>checking for library containing nl_connect... no [...]
>
>I've applied this without the nl1 -> nl3 change.
Okay, my configure also state "nl_connect... no", but compiles and run as expected with network interfaces, routing, etc. information.
I only upgraded from libnl1 since it produced compile-time errors in my setup (ptxdist 2012.04.0 with mainline rules).
Venlig hilsen / Best regards
Kamstrup A/S <http://www.kamstrup.dk>
Bruno Thomsen
Development engineer
Technology
Kamstrup A/S
Industrivej 28
DK-8660 Skanderborg
Tel: +45 89 93 10 00
Fax: +45 89 93 10 01
Dir: +45 89 93 13 94
E-mail: bth@kamstrup.dk
Web: www.kamstrup.dk
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-03-14 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 14:20 Bruno Thomsen
2014-03-13 14:38 ` Michael Olbrich
2014-03-14 14:39 ` Bruno Thomsen [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=915054555B5659448ACF8A70E114824DE75F562D@Exchange2010.kamstrup.dk \
--to=bth@kamstrup.dk \
--cc=ptxdist@pengutronix.de \
/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