On 3/10/25 1:39 PM, Bart Van Assche wrote:
Are there any objections against removing NOAUTODEPS support? I noticed
that ./config.status is often run if no changes have been made to any
configure script. Hence this proposal to remove NOAUTODEPS support and
instead to let developers run the
Hi,
Are there any objections against removing NOAUTODEPS support? I noticed
that ./config.status is often run if no changes have been made to any
configure script. Hence this proposal to remove NOAUTODEPS support and
instead to let developers run the configure script and/or autoreconf
when
#x27; -x AES-256 -X 'admin_test_password#9812'
> /tmp/xsnmp/snmpagent create danellb adminextronshaaes256
> snmpset: Decryption error
> + status=
>
>
>
> --
> *From:* Bill Fenner
> *Sent:* Tuesday, June 4, 2024 11:13 PM
> *To:* su
n Fri, May 17, 2024 at 7:44 AM sukeerthi bj wrote:
> Hi,
>
> I see AES192 and SHA256 support in SNMP, but wanted to understand if below
> code is doing right? Here for pcks_generate_ku only CKM_SHA_1 is passed.
> For SHA256 should not CKM_SHA256 be passed here instead?
> Can anyon
Hi,
I see AES192 and SHA256 support in SNMP, but wanted to understand if below
code is doing right? Here for pcks_generate_ku only CKM_SHA_1 is passed.
For SHA256 should not CKM_SHA256 be passed here instead?
Can anyone have a look into this and explain?
#ifndef NETSNMP_DISABLE_MD5
if
Hi Bart,
The changes look great. Go ahead with the merge to master.
Hayden
On Thu, Aug 4, 2022 at 2:39 PM Bart Van Assche wrote:
> On 7/28/22 20:48, Bart Van Assche wrote:
> > On 7/27/22 09:27, Hayden Roche wrote:
> >> A while back, we (wolfSSL) added support for wolfSSL
On 7/28/22 20:48, Bart Van Assche wrote:
On 7/27/22 09:27, Hayden Roche wrote:
A while back, we (wolfSSL) added support for wolfSSL to net-snmp 5.9.1
for a
customer. You can find the patch here:
https://github.com/wolfSSL/osp/tree/master/net-snmp
Is this something you'd be interest
On 7/27/22 09:27, Hayden Roche wrote:
A while back, we (wolfSSL) added support for wolfSSL to net-snmp 5.9.1
for a
customer. You can find the patch here:
https://github.com/wolfSSL/osp/tree/master/net-snmp
Is this something you'd be interested in having upstream?
Support for wolfSSL se
Hi,
A while back, we (wolfSSL) added support for wolfSSL to net-snmp 5.9.1 for a
customer. You can find the patch here:
https://github.com/wolfSSL/osp/tree/master/net-snmp
Is this something you'd be interested in having upstream?
Best,
Hayden
On Thu, Dec 09, 2021 at 09:45:38PM +0530, Feroz wrote:
> In the NetSNMP sample code I see the following block.
> I would like to understand if NetSNMP support "CreateAndWait"
>
> File: ipAddressTable.c
>
> if (ROWSTATUS_CREATEANDWAIT == ipAddressRowStatus
In the NetSNMP sample code I see the following block.
I would like to understand if NetSNMP support "CreateAndWait"
File: ipAddressTable.c
if (ROWSTATUS_CREATEANDWAIT == ipAddressRowStatus_val) {
DEBUGMSGTL(("ipAddressTable", "createAndWait not suppo
t; *To:* [email protected];
> [email protected]
> *Subject:* How to support SNMPv2 mib traps per VRF.
>
> Hi ,
>
>
> We are supporting Multiple snmp servers (snmp server for each VRF).I want
> to enable authenticationfailure traps for each VR
Hi All
My C++ application running(on windows-64 bit application with Apache 2.4
(Daemon )and this application support only SNMP V1 V2 using net-snmp API our
C++ application get snmp call (for SNMPGET,SNMP walk using Windows OS provided
SNMP Service using ExtensionAgents C:\Windows\system32
Spell check has done in line.
From: chandrasekharreddy chinnapareddygari
Sent: Wednesday, 20 October, 2021, 14:15
To: [email protected]; [email protected]
Subject: How to support SNMPv2 mib traps per VRF.
Hi ,
We are
Hi ,
We a supporting Multiple snmp servers (snmp server for each VRF).I want to
enable authenticationfailure traps for each VRF.
Net-snmp has inbuilt token authtrapenable .Authentication Failure traps are
sending to the receivers ,If authtrapenable is set to 1 in /etc/snmp/snmpd.conf
.
But,/
inux
Net-SNMP Version: 5.9
Network transport support: Callback Unix Alias TCP UDP TCPIPv6 UDPIPv6
IPv4Base SocketBase TCPBase UDPIPv4Base UDPBase IPBase IPv6Base
SNMPv3 Security Modules: usm
Agent MIB code:default_modules mibII snmpv3mibs =>
snmpv3mibs mibII ucd
linux
Net-SNMP Version: 5.9
Network transport support: Callback Unix Alias TCP UDP TCPIPv6 UDPIPv6
IPv4Base SocketBase TCPBase UDPIPv4Base UDPBase IPBase IPv6Base
SNMPv3 Security Modules: usm
Agent MIB code:default_modules mibII snmpv3mibs =>
snmpv3m
#x27;--enable-ipv6' '--with-pic' '--with-cc=gcc'
'CC=gcc' 'CFLAGS=-m64' '--with-mib-modules=mibII,snmpv3mibs'*
'--enable-blumenthal-aes'*
==
-
Net-SNMP configuration summary:
-
On Wed, 24 Feb 2021 at 01:59, Simon Chamlian wrote:
> When these flags (--with-security-modules and --with-transports) are not
> specified, what does snmpv3 uses by default?
>
The default set of security modules is defined in
configure.d/config_modules_security_modules and is just usm.
USM is th
Hi,
Compiling Net-SNMP with TLS and DTLS Support
Just ensure you have a recent version of OpenSSL
<http://net-snmp.sourceforge.net/wiki/index.php/OpenSSL> installed as well
as run configure with the following two options in addition to your normal
options:
# ./configure *--with-security-m
On Sun, Sep 06, 2020 at 07:34:57PM -0700, Bart Van Assche wrote:
> On 2020-08-18 10:28, Magnus Fromreide wrote:
> > I think the child code in the vfork case should be exactly
> >
> > execv(argv[0], argv);
> > _exit(1);
> >
> > as that seems to be about what POSIX allows.
> >
> >
On 2020-08-18 10:28, Magnus Fromreide wrote:
> I think the child code in the vfork case should be exactly
>
> execv(argv[0], argv);
> _exit(1);
>
> as that seems to be about what POSIX allows.
>
>(From POSIX.1) The vfork() function has the same effect as fork(2),
>
variant. On the other hand I usually am far from
> >> the most conservative one in discussions like this one.
> >
> > I think off by default makes a lot more sense than an out-right removal.
>
> How about restoring uClinux support with the patch below? parse_cmd() and
&g
discussions like this one.
>
> I think off by default makes a lot more sense than an out-right removal.
How about restoring uClinux support with the patch below? parse_cmd() and
dup() are called before fork(). That change makes it possible to use a
regular pipe between the parent and the child,
Magnus Fromreide writes:
> That is a more lenient option than just dropping it so I think 'happy with
> dropping it' covers this variant. On the other hand I usually am far from
> the most conservative one in discussions like this one.
I think off by default makes a lot more sense than an out-r
tter but we are sadly lacking in the CLOEXEC department.
> >
> > To be honest the calls to perror and exit if exec fails is more suspicious
> > as
> > that is explicitly stated to cause undefined behaviour.
> >
> > With all this I should probably repeat that I a
On Wed, May 27, 2020 at 10:42:09AM +, Yefetluzzatto, Inbal wrote:
> Hello,
>
> I currently use NET-SNMP Version: 5.7.2 which has limited SNMP V3 support.
> I am trying to set up a manager that can use Authentication protocols -
> SHA-256 and MD5 with Privacy protocols A
On Thu, 11 Jun 2020 at 04:13, Yefetluzzatto, Inbal
wrote:
> ../include/net-snmp/library/snmpAAL5PVCDomain.h:18:17: fatal error: atm.h:
> No such file or directory
>
atm.h is a system library header. In Debian, you would find this in
libatm1-dev package which you would need to have installed for n
Hello,
I currently use NET-SNMP Version: 5.7.2 which has limited SNMP V3 support.
I am trying to set up a manager that can use Authentication protocols -
SHA-256 and MD5 with Privacy protocols AES-256 and 3DES (TDES).
I was trying to install version 5.8 on my vd (running CentOS Linux 7
Hi,
I was reached with question about $SUBJ, that I am not sure, if it's possible.
Imagine this situation.
Someone have linux system, on which is disabled IPv6 support via grub file
(/etc/default/grub -> ipv6.disable=1). After reboot, this will cause following
error message by snmpd [
*Question : Does netsnmp support IPv6 varbind as type IPAdress?*
1- *I "get bad notation" error when I am trying to send trap having IPv6
address with type IPAdress(a) as highlighted(in red italics underlined)*
[root@IWFVM00141 ~]# snmptrap -d -v 2c -c public 16.166.98.19
David Hauck writes:
> I noticed the recent 'CHANGES' file entry in the V5-8-patches branch
> references the following:
Thanks. That came from a log message, but I assume your text is correct
so have changed the file.
--
Wes Hardaker
Please mail all replies to [email protected]
Hi,
I noticed the recent 'CHANGES' file entry in the V5-8-patches branch references
the following:
- Add support for OpenSSL 1.1.0
Should this instead read:
- Add support for OpenSSL 1.1.1
These are two different versions of OpenSSL, with the former going EOL this
month
On Fri, Jan 25, 2019 at 11:37 AM Magnus Fromreide
wrote:
> On Sun, Oct 28, 2018 at 01:54:22PM -0700, Bart Van Assche wrote:
> > Hello,
> >
> > As you may have noticed multiple people asked to add SO_BINDTODEVICE
> support
> > to Net-SNMP. This patch series ad
On Sun, Oct 28, 2018 at 01:54:22PM -0700, Bart Van Assche wrote:
> Hello,
>
> As you may have noticed multiple people asked to add SO_BINDTODEVICE support
> to Net-SNMP. This patch series adds such support by allowing to specify the
> name of the network interface to bind a Net-S
I was thinking about adding text below the table instead - "When specifying
*hostname*, *IPv4-address* or *IPv6-address* in the tcp, udp, tcp6 or udp6
transports, you can also ...". I don't want to clutter up the main
documentation with these kind-of-corner-cases.
Bill
On Fri, Jan 25, 2019 at
What about something like this ( I skipped the "or")
diff --git a/man/snmpcmd.1.def b/man/snmpcmd.1.def
index aea3ca40a..d4f896000 100644
--- a/man/snmpcmd.1.def
+++ b/man/snmpcmd.1.def
@@ -367,12 +367,12 @@ to the following table:
.BR ""
.BR " format"
.IP "udp" 28
-hostname[:port]
-.I or
-IPv4-
On Wed, Jan 23, 2019 at 10:17 PM Bart Van Assche wrote:
> On 1/23/19 9:43 AM, Bill Fenner wrote:
> > The pattern I was trying to follow from the existing code appeared to be
> > basically
> >
> > if (cp == delimiter of optional section) {
> > *cp = '\0'; /* terminate previous section at deli
On 1/23/19 9:43 AM, Bill Fenner wrote:
The pattern I was trying to follow from the existing code appeared to be
basically
if (cp == delimiter of optional section) {
*cp = '\0'; /* terminate previous section at delimiter */
this = cp + 1; /* handle this section */
cp = ... /* find
My attempts at updating the man page formats really poorly in 80 columns:
At its simplest, the AGENT specification may consist of a host-
name, or an IPv4 address in the standard "dotted quad" notation.
In this case, communication will be attempted using UDP/IPv4 to
On Wed, Jan 23, 2019 at 12:58 AM Anders Wallin wrote:
> Hi Bill,
>
> I'm missing updates to the documentation/man pages. (I can't find that the
> man pages are update with @iface either)
>
Yes, I documented it in the same place as @intf ;-)
I'll fix that.
Bill
___
hes.
> >
> >
> https://github.com/fenner/net-snmp/compare/V5-8-patches...fenner:linux-namespace
>
> Hi Bill,
>
> The following new code in netsnmp_parse_ep_str() looks a bit fragile to me:
>
> cp = strchr(iface, '@');
> if (!cp)
>
snmp_parse_ep_str() looks a bit fragile to me:
>
> cp = strchr(iface, '@');
> if (!cp)
> cp = strchr(iface, ':');
>
> Wouldn't it be better to backtrack to the previous value of 'cp' if no
> second '
if (!cp)
cp = strchr(iface, ':');
Wouldn't it be better to backtrack to the previous value of 'cp' if no
second '@' sign is found? That will avoid that this code fails if
support for a new delimiter between '@' and ':' woul
On Wed, Nov 7, 2018 at 1:26 AM Bart Van Assche wrote:
> On 11/6/18 8:03 AM, Bill Fenner wrote:
> > Given your proposed code structure, I imagine that we could add network
> > namespaces to netsnmp_ep too - this basically ends up using "socketat(
> > /* magic */, family, type, protocol )" instead
I've applied my clientaddr parsing fix for IPv4 and IPv6, passing ":0" as
the default transport, and also modified the IPv6 address parser to handle
a bare IPv6 address (no brackets, no port). With these changes, all of the
tests pass in their original form.
I'd like to add some more tests for sp
> On Nov 7, 2018, at 1:27 AM, Bart Van Assche wrote:
>
>> On 11/6/18 12:31 PM, Bill Fenner wrote:
>> Playing with this in V5-8-patches, I see it broke my fix for using
>> clientaddr to specify the source address for traps:
>> netsnmp_sockaddr_in: addr 0xffd5e824, inpeername "127.0.0.1", defaul
On 11/6/18 12:31 PM, Bill Fenner wrote:
Playing with this in V5-8-patches, I see it broke my fix for using
clientaddr to specify the source address for traps:
netsnmp_sockaddr_in: addr 0xffd5e824, inpeername "127.0.0.1",
default_target ":0"
netsnmp_sockaddr_in: addr 0xffd5e824, inpeername ":0"
be an #ifdef in patch 5 to make the interface name
optional, both in the struct and the parser, for platforms that don't
support it? Is it better to return a parse error on the address that
includes interface name, or a "failed to open socket" without much more
information?
That
ue, Nov 6, 2018 at 11:03 AM Bill Fenner
> wrote:
>
>> Hi Bart,
>>
>> My main question is, what's the advantage of storing the IPv4/IPv6
>> address as a string and a port number, instead of as a sockaddr_*? I.e.,
>> why use netsnmp_ep_str?
>>
>&g
n is, what's the advantage of storing the IPv4/IPv6 address
> as a string and a port number, instead of as a sockaddr_*? I.e., why use
> netsnmp_ep_str?
>
> Is the API change here ok? Are we assuming that nobody ever calls
> netsnmp_foo_transport() directly?
>
> Should there be an #
be an #ifdef in patch 5 to make the interface name optional,
both in the struct and the parser, for platforms that don't support it? Is
it better to return a parse error on the address that includes interface
name, or a "failed to open socket" without much more information?
Give
an mine. Thanks for doing this.
--Sam Tannous
On Sun, Oct 28, 2018 at 5:19 PM Bart Van Assche <mailto:[email protected]>> wrote:
Hello,
As you may have noticed multiple people asked to add SO_BINDTODEVICE
support
to Net-SNMP. This patch series adds such support by allowin
te:
> Hello,
>
> As you may have noticed multiple people asked to add SO_BINDTODEVICE
> support
> to Net-SNMP. This patch series adds such support by allowing to specify the
> name of the network interface to bind a Net-SNMP endpoint to as
&
---
include/net-snmp/library/snmpIPBaseDomain.h | 2 +
snmplib/transports/snmpIPBaseDomain.c | 41 +++--
snmplib/transports/snmpIPv4BaseDomain.c | 2 +
snmplib/transports/snmpIPv6BaseDomain.c | 2 +
snmplib/transports/snmpTCPDomain.c | 7
snmplib/tra
Hello,
As you may have noticed multiple people asked to add SO_BINDTODEVICE support
to Net-SNMP. This patch series adds such support by allowing to specify the
name of the network interface to bind a Net-SNMP endpoint to as
"@". An example:
agent/snmpd -Mmibs -f -Lo -c .../snmpd
Bart Van Assche writes:
> http://net-snmp.sourceforge.net/wiki/index.php/TUT:Writing_a_Dynamically_Loadable_Object
>
> http://net-snmp.sourceforge.net/wiki/index.php/TUT:Writing_a_Subagent
Yep, this is definitely the right place to start looking. We've
supported dynamically loadable submodul
patches here to have
some opinion of other people and *if* it will be ready then submit
those initial corrections as git PR(s).
When current build framework will be more clean separating MIB by MIB
to build snmpd single MIB support as optionally loaded DSO can start.
Biggest obstacle which I see
On Tue, Aug 21, 2018 at 11:52:31AM +0100, Tomasz Kłoczko wrote:
> Hi,
>
> Looks like snmpd agent supports extending agent functionalities by
> loading on run-time DSO module with additional MIBs support.
> Have question: is it possible to build net-snmp code to support to add
>
On 08/21/18 03:52, Tomasz Kłoczko wrote:
> Looks like snmpd agent supports extending agent functionalities by
> loading on run-time DSO module with additional MIBs support.
> Have question: is it possible to build net-snmp code to support to add
> exact supported by net-snmp MIBs not
Hi,
Looks like snmpd agent supports extending agent functionalities by
loading on run-time DSO module with additional MIBs support.
Have question: is it possible to build net-snmp code to support to add
exact supported by net-snmp MIBs not as compiled in statically code
but as loadable DSOs?
If
Robert Story writes:
> The request must come from our core developer team, and only votes
> from the core developer team count.
Actually, I don't believe that's true (but it is common).
http://net-snmp.sourceforge.net/dev/release-policy.html
Specifically, anyone should be able to propose a
Josef,
Two points..
First, are you also submitting these patches to the patch database?
The mailing list if fine for discussion, but when we do patch
review we go through the database, not the mailing list.
Second, 'request for votes' is something specific to the Net-SNMP
release process. The r
t; authCommunity log,execute,net public
>
> Start snmptrapd service.
>
> # systemctl start snmptrapd
>
> Run following command.
>
> # snmptrap -v 2c -c public localhost '' .1.3.6.1.4.1.8072.2.1.3
> .1.3.6.1.4.1.8072.2.1.3 s "データ"
>
>
following line.
authCommunity log,execute,net public
Start snmptrapd service.
# systemctl start snmptrapd
Run following command.
# snmptrap -v 2c -c public localhost '' .1.3.6.1.4.1.8072.2.1.3
.1.3.6.1.4.1.8072.2.1.3 s "データ"
Check the /var/log/messages or journal
07:23:32 -0700 Bart wrote:
> >> BVA> This patch makes it possible to enable Travis and Appveyor
> >> BVA> continuous integration support. On Travis Net-SNMP is built
> >> BVA> with all MIBs, with --disable-set-support, with
> >> BVA> --enable-m
Travis and Appveyor
>> BVA> continuous integration support. On Travis Net-SNMP is built
>> BVA> with all MIBs, with --disable-set-support, with
>> BVA> --enable-mini-agent, with --enable-minimalist and with
>> BVA> --enable-read-only. All these configurations are built o
Den 17-05-2018 kl. 15:54 skrev Robert Story:
On Wed, 16 May 2018 07:23:32 -0700 Bart wrote:
BVA> This patch makes it possible to enable Travis and Appveyor
BVA> continuous integration support. On Travis Net-SNMP is built
BVA> with all MIBs, with --disable-set-support, with
BVA> -
On Wed, 16 May 2018 07:23:32 -0700 Bart wrote:
BVA> This patch makes it possible to enable Travis and Appveyor
BVA> continuous integration support. On Travis Net-SNMP is built
BVA> with all MIBs, with --disable-set-support, with
BVA> --enable-mini-agent, with --enable-minimalist
This patch makes it possible to enable Travis and Appveyor continuous
integration support. On Travis Net-SNMP is built with all MIBs, with
--disable-set-support, with --enable-mini-agent, with --enable-minimalist
and with --enable-read-only. All these configurations are built on Linux
and on OS/X
On Mon, 14 May 2018 08:45:54 -0700 Bart wrote:
BVA> On 05/14/18 05:29, Niels Baggesen via Net-snmp-coders wrote:
BVA> > The patch that went into 5.7-patches is not sufficient for
BVA> > NetBSD 8 on 5.8
BVA> >
BVA> > The following patch to 5.8.RC1 is required.
BVA> >
BVA> > May I solicit some vote
On 05/14/18 05:29, Niels Baggesen via Net-snmp-coders wrote:
The patch that went into 5.7-patches is not sufficient for NetBSD 8 on
5.8
The following patch to 5.8.RC1 is required.
May I solicit some votes?
diff --git a/agent/mibgroup/mibII/at.h b/agent/mibgroup/mibII/at.h
index 1676cb6..e89b96
The patch that went into 5.7-patches is not sufficient for NetBSD 8 on
5.8
The following patch to 5.8.RC1 is required.
May I solicit some votes?
diff --git a/agent/mibgroup/mibII/at.h b/agent/mibgroup/mibII/at.h
index 1676cb6..e89b966 100644
--- a/agent/mibgroup/mibII/at.h
+++ b/agent/mibgroup/m
On Fri, 27 Apr 2018 23:00:57 -0700 Keith wrote:
KM> > BVA> > https://sourceforge.net/p/net-snmp/code/merge-requests/14/.
KM> > BVA> > [...]
KM> Let me give this another go. I think the best solution is when
KM> --with-openssl is processed that a variable like
KM> "blumenthalcapable" be set based
On Fri, Apr 27, 2018, at 11:00 PM, Keith Mendoza wrote:
> >
> > Regardless, configure should be doing the right thing based on what
> > is currently installed.
> >
> > BVA> Regarding your pull request:
> > BVA> I'd like to avoid adding AC_CHECK_HEADERS() calls in
> > BVA> config_project_with_en
On Fri, Apr 27, 2018, at 2:40 PM, Robert Story wrote:
> On Wed, 25 Apr 2018 10:28:59 -0600 Bart wrote:
> BVA> On 04/25/18 10:04, Keith Mendoza wrote:
> BVA> > I have submitted a merge request to verify that when the
> BVA> > --enable-blumenthal-aes is used in configure that it checks
> BVA> > tha
On Wed, 25 Apr 2018 10:53:35 -0700 Keith wrote:
KM> I feel the best solution would be to remove the typecasts going
KM> on inside sc_get_openssl_hashfn(). It seems to me that having
KM> these typecasts there is triggering the implicit declaration of
KM> EVP_sha512() that lead to the crash we both e
On Wed, 25 Apr 2018 12:05:06 -0600 Bart wrote:
BVA> On 04/25/18 11:54, Keith Mendoza wrote:
BVA> > Out of curiosity, do you have a "fork" of Net-SNMP on github
BVA> > to connect it to Travis and Appveyor?
BVA>
BVA> If you are looking for a Net-SNMP repository on github, please
BVA> use https://g
On Wed, 25 Apr 2018 10:28:59 -0600 Bart wrote:
BVA> On 04/25/18 10:04, Keith Mendoza wrote:
BVA> > I have submitted a merge request to verify that when the
BVA> > --enable-blumenthal-aes is used in configure that it checks
BVA> > that OpenSSL's aes.h and evp.h are available. Merge request
BVA> > is
Hi Bart,
Also check out my travis config - configuring with different sets of
configure args - minimalist is important to me, so it's nice to have
regression testing against, and we had a couple of interesting bugs
reported agaist --disable-set-support and --enable-read-only, so I added
On 04/25/18 12:58, Robert Story wrote:
On Wed, 25 Apr 2018 09:06:28 -0600 Bart wrote:
BVA> One of the advantages of github over SourceForge is that
BVA> integration with continuous integration (CI) services like
BVA> Travis and Appveyor is easy. Adding such support however
BVA> req
On Wed, 25 Apr 2018 09:06:28 -0600 Bart wrote:
BVA> One of the advantages of github over SourceForge is that
BVA> integration with continuous integration (CI) services like
BVA> Travis and Appveyor is easy. Adding such support however
BVA> requires to add proper configuration f
On Wed, Apr 25, 2018, at 11:05 AM, Bart Van Assche wrote:
> On 04/25/18 11:54, Keith Mendoza wrote:
> > Out of curiosity, do you have a "fork" of Net-SNMP on github to connect it
> > to Travis and Appveyor?
>
> Hello Keith,
>
> If you are looking for a Net-SNMP repository on github, please use
On 04/25/18 11:54, Keith Mendoza wrote:
Out of curiosity, do you have a "fork" of Net-SNMP on github to connect it to
Travis and Appveyor?
Hello Keith,
If you are looking for a Net-SNMP repository on github, please use
https://github.com/net-snmp/net-snmp. I hope Wes will connect that
repos
Bart,
On Wed, Apr 25, 2018, at 9:28 AM, Bart Van Assche wrote:
> On 04/25/18 10:04, Keith Mendoza wrote:
> > Net-SNMP dev team,
> > I have submitted a merge request to verify that when the
> > --enable-blumenthal-aes is used in configure that it checks that OpenSSL's
> > aes.h and evp.h are avai
ion (CI) services like Travis and Appveyor is
> easy. Adding such support however requires to add proper configuration
> files and the necessary scripts in the source tree. Hence this patch. As
> one can see for Linux all regression tests are run, for OS/X some
> regression tests
On 04/25/18 10:04, Keith Mendoza wrote:
Net-SNMP dev team,
I have submitted a merge request to verify that when the
--enable-blumenthal-aes is used in configure that it checks that OpenSSL's
aes.h and evp.h are available. Merge request is at
https://sourceforge.net/p/net-snmp/code/merge-reques
Net-SNMP dev team,
I have submitted a merge request to verify that when the
--enable-blumenthal-aes is used in configure that it checks that OpenSSL's
aes.h and evp.h are available. Merge request is at
https://sourceforge.net/p/net-snmp/code/merge-requests/14/. This should fully
resolve the fol
Hello,
One of the advantages of github over SourceForge is that integration
with continuous integration (CI) services like Travis and Appveyor is
easy. Adding such support however requires to add proper configuration
files and the necessary scripts in the source tree. Hence this patch. As
t;> security service 3 error parsing ScopedPDU
>>
>> What I am missing?
>>
>
> There are two ways to take a short auth key and lengthen it for a strong
> privacy algorithm. Two things to try:
>
> 1. Use "AES192C" for the user instead of "AE
ead of "AES192" (this uses the "Cisco"
algorithm);
2. Use a stronger auth mechanism, which creates a longer auth key, which
doesn't have to be lengthened for the strong privacy algorithm, avoiding
the question of how to lengthen it. I think SHA suffices, but of course
SHA2
ser, I do a GET on one of the OID using user3 using
AES-192 and it DOES NOT work! I get the following error in the log file:
security service 3 error parsing ScopedPDU
What I am missing?
Thanks,
Simon
On Fri, Apr 6, 2018 at 8:49 PM, Bill Fenner wrote:
> Simon,
>
> The USM A
Simon,
The USM AES192 and AES256 support is based upon an Internet Draft, which
never became a standard - therefore, you have to pass
"--enable-blumenthal-aes" to ./configure. (You don't have to enable TSM or
the TLS transports; that's a whole different kettle of fish.)
;
--with-logfile="/var/log/snmp"
*--with-transports="DTLSUDP TLSTCP" --with-security-modules="tsm" *
Still when I put
createUser User2 MD5 "passwrd-00" AES192 (or AES-192) "default-00"
I get an error message:
snmpd.conf: line 27: Error: u
hat SNMPv3 RFC _does not_ specify AES192 and AES256;
they specified some older algorithms that were "latest and greatest"
at the time it was being drafted :(
Thanks,
Keith
Thanks,
Keith
On Thu, Apr 5, 2018 at 1:54 PM, Simon Chamlian wrote:
>
>
>
> Hi,
>
> Does Net-SNMP
Hi,
Does Net-SNMP support AES192 or AES256?
According to this link
http://www.net-snmp.org/wiki/index.php/Strong_Authentication_or_Encryption
The short answer is Yes, starting with release 5.8 AES193 and AES256 are an
optional configure option.
So I downloaded version 5.8.pre2 and tried
There is also a Python implementation of the command-line tooling [1]
you could play with until Net-SNMP release becomes available.
1. http://snmplabs.com/snmpclitools/snmpget.html#snmpv3-usm-security-level
On 01/05/2018 01:50 PM, Robert Story wrote:
> On Fri, 5 Jan 2018 15:47:58 +0530 Neena wro
On Fri, 5 Jan 2018 15:47:58 +0530 Neena wrote:
NMS> What is the plan to suport rfc7860 in netsnmp code ? Is beta
NMS> version available ?
Funny you should ask.. There is a pre-pre release of Net-SNMP 5.8
available, or you can use the master branch in git. I should be
making an announcement soon.
Hi NetSNMP Coders,
What is the plan to suport rfc7860 in netsnmp code ? Is beta version
available ?
Thanks in advance !
Regards,
neena
--
Check out the vibrant tech community on one of the world's most
engaging tech sit
ed version.
Josef
[1] https://sourceforge.net/p/net-snmp/bugs/2757/
- Original Message -
| From: "Bill Fenner"
| To: "Josef Ridky"
| Cc: "Bart Van Assche" , "Net-SNMP Coders"
| Sent: Tuesday, October 31, 2017 1:43:37 PM
| Subject: Re: OpenSSL 1
1 - 100 of 618 matches
Mail list logo
