Displaying 3 results from an estimated 3 matches for "nis_nam".
Did you mean:
nis_name
1998 May 26
0
Re: Beware of dangerous enviroment (Re: Overflows in minicom)
...ue;
}
- *(pathP++) = *nlspath;
}
+ if (pathP >= path + sizeof (path))
+ {
+ goto error;
+ }
+ *(pathP++) = *nlspath;
}
*pathP = ''\0'';
if (stat(path, &sbuf) == 0 && S_ISREG (sbuf.st_mode)) {
--- libc-5.4.44/libc/nys/nis/src/nis_names.c.secenv Mon Oct 21 06:40:17 1996
+++ libc-5.4.44/libc/nys/nis/src/nis_names.c Sat May 16 15:46:52 1998
@@ -29,6 +29,8 @@
#include "nis_conf.h"
#include "xalloc.h"
+extern char *__libc_secure_getenv(const char *);
+
nis_name nis_local_directory(void)
{
@@ -152,7 +154,7...
1998 May 30
9
"Flavors of Security Through Obscurity"
This was posted not too long ago on sci.crypt... Enjoy... I think the most
relevant information is near the top, but it''s all quite good... :-)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
There is no intrinsic difference between algorithm and data, the
same information can be viewed as data in one context and as
algorithm in another. Why then do so many people claim that
encryption algorithms
2006 Oct 31
0
6362982 namespace pollution/protection in libc
...s/cache/mgr_cache.cc
update: usr/src/lib/libnsl/nis/gen/nis_cast.c
update: usr/src/lib/libnsl/nis/gen/nis_cback_xdr.c
update: usr/src/lib/libnsl/nis/gen/nis_hash.c
update: usr/src/lib/libnsl/nis/gen/nis_local.h
update: usr/src/lib/libnsl/nis/gen/nis_lookup.c
update: usr/src/lib/libnsl/nis/gen/nis_names.c
update: usr/src/lib/libnsl/nis/gen/nis_rpc.c
update: usr/src/lib/libnsl/nis/gen/nis_subr.c
update: usr/src/lib/libnsl/nis/gen/nis_tags.c
update: usr/src/lib/libnsl/nis/gen/nis_xdr.c
update: usr/src/lib/libnsl/nis/gen/npd_lib.c
update: usr/src/lib/libnsl/nis/gen/print_obj.c
update: usr/sr...