summaryrefslogtreecommitdiff
path: root/WUR-REPORT
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2007-07-12 18:26:36 +0000
committerJakub Jelinek <jakub@redhat.com>2007-07-12 18:26:36 +0000
commit0ecb606cb6cf65de1d9fc8a919bceb4be476c602 (patch)
tree2ea1f8305970753e4a657acb2ccc15ca3eec8e2c /WUR-REPORT
parent7d58530341304d403a6626d7f7a1913165fe2f32 (diff)
downloadglibc-0ecb606cb6cf65de1d9fc8a919bceb4be476c602.tar.gz
2.5-18.1
Diffstat (limited to 'WUR-REPORT')
-rw-r--r--WUR-REPORT45
1 files changed, 45 insertions, 0 deletions
diff --git a/WUR-REPORT b/WUR-REPORT
new file mode 100644
index 0000000000..ef407cfdbe
--- /dev/null
+++ b/WUR-REPORT
@@ -0,0 +1,45 @@
+<unistd.h>:
+
+lssek: Probably should be __wur but lseek(fd,SEEK_SET,0) will succeed if
+ the descriptor is fine.
+lseek64: same
+
+setuid: will always succeed given correct privileges, so there might
+ be places which don't check for it.
+setreuid: same
+seteuid: same
+setgid: same
+setregid: same
+setegid: same
+setresuid: same
+setresgid: same
+
+
+<stdio.h>:
+
+setvbuf: if stream and buffer are fine and other parameters constant,
+ it cannot really fail.
+fseek: see lseek
+fseeko: likewise
+fgetpos: similarly
+fsetpos: likewise
+
+
+<stdlib.h>:
+
+atexit: it is guaranteed that a certain number of handlers can be
+ registered, so some calls might need not be checked
+on_exit: same
+random functions: one might want to discard a number of results. In any
+ case, no security problem
+
+
+putenv: probably SHOULD be marked, but we'll wait a bit.
+setenv: likewise
+unsetenv: likewise
+clearenv: likewise
+
+mbstowcs: probably SHOULD be marked
+wcstombs: likewise
+
+ptsname_r: probably SHOULD be marked