Hi I find many places in net-snmp code "compairing array with NULL"
e.g.:
1.
if ((NULL == tbl_idx->ipDefaultRouterAddress) ||
(tbl_idx->ipDefaultRouterAddress_len <
(ipDefaultRouterAddress_val_ptr_len))) {
snmp_log(LOG_ERR, "not enough space for value\n");
return
On 03/15/2010 07:57 PM, Robert Story wrote:
> On Sun, 14 Mar 2010 12:11:42 -0300 Leonardo wrote:
> LC> > There is a patch in Red Hat Bugzilla:
> LC> > https://bugzilla.redhat.com/show_bug.cgi?id=532672. It keeps track of
> LC> > already used indexes and tries to read /etc/mtab in the same ord
Hi Dave,
Thanks for the patch, the patch fixed the issue, but seems to have introduced
another issue.
For now the access (OR) rouser approach is not yet changed, leaving that the
issue is:
The new issue is found for the below two configurations, both the issues are
for AES128 protocol (
On Wed, Mar 17, 2010 at 10:09 AM, Dave Shield
wrote:
> I've had a quick look at the code for winExtDLL.c
> (in response to bug #2971257), and there's something
> that confuses (/concerns) me.
>
> Within the var_winExtDLL handler, there's the usual
> (for request = requests; request; request = r
Bart,
I've had a quick look at the code for winExtDLL.c
(in response to bug #2971257), and there's something
that confuses (/concerns) me.
Within the var_winExtDLL handler, there's the usual
(for request = requests; request; request = request->next )
loop, to work through all the relevant va
