mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] net-snmp: Improved SNMPv3 authentication and privacy support.
Date: Fri, 21 Feb 2014 12:42:17 +0100	[thread overview]
Message-ID: <902e54c409b56dbfacbbc3512b192309@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <1392977215-14447-1-git-send-email-bth@kamstrup.dk>

Hei Bruno, 

Am 2014-02-21 11:06, schrieb Bruno Thomsen:
> Tested SNMPv3 with USM (User-based Security Model) SHA auth + AES
> priv, minimal agent option disabled.

I couldn't find this option disabled in your patch.

>  	--$(call ptx/endis, PTXCONF_NET_SNMP_DOM_SOCK_ONLY)-agentx-dom-sock-only \
>  	--enable-mib-config-checking \
> @@ -121,6 +119,12 @@ else
>  NET_SNMP_AUTOCONF += --disable-snmpv2c
>  endif
>  
> +ifdef PTXCONF_NET_SNMP_PRIVACY
> +NET_SNMP_AUTOCONF += --enable-privacy
> +else
> +NET_SNMP_AUTOCONF += --disable-privacy
> +endif
> +
>  ifdef PTXCONF_NET_SNMP_DES
>  NET_SNMP_AUTOCONF += --enable-des
>  else
> @@ -133,6 +137,12 @@ else
>  NET_SNMP_AUTOCONF += --disable-md5
>  endif
>  
> +ifdef PTXCONF_NET_SNMP_SHA_AES
> +NET_SNMP_AUTOCONF += --with-openssl
> +else
> +NET_SNMP_AUTOCONF += --without-openssl
> +endif

Why did you ont use the ptx/wwo and ptx/endis makros for this?

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-02-21 11:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21 10:06 Bruno Thomsen
2014-02-21 11:42 ` Alexander Dahl [this message]
2014-03-06 17:29 ` Michael Olbrich
2014-03-07 12:25   ` Bruno Thomsen

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=902e54c409b56dbfacbbc3512b192309@idefix.lespocky.dyndns.org \
    --to=post@lespocky.de \
    --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