aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Frysinger <vapier@gentoo.org>2021-10-22 00:18:15 -0400
committerMike Frysinger <vapier@gentoo.org>2021-10-22 00:19:44 -0400
commit60cff8d682fe7816ca0656d4da27e630855287e7 (patch)
tree097f20c21e69fc02c7f66c3d2ee4ee963d6f2493
parentlibsandbox: add xattr wrappers #672566 (diff)
downloadsandbox-60cff8d682fe7816ca0656d4da27e630855287e7.tar.gz
sandbox-60cff8d682fe7816ca0656d4da27e630855287e7.tar.bz2
sandbox-60cff8d682fe7816ca0656d4da27e630855287e7.zip
libsandbox: drop old *.py[co] hack #775416
With our eclasses & python frameworks responsible for generating these files now, we should be able to reject write attempts to these again. Lets turn it back on and see what blows up. Bug: http://bugs.gentoo.org/256953 Closes: https://bugs.gentoo.org/775416 Signed-off-by: Mike Frysinger <vapier@gentoo.org>
-rw-r--r--libsandbox/libsandbox.c14
1 files changed, 0 insertions, 14 deletions
diff --git a/libsandbox/libsandbox.c b/libsandbox/libsandbox.c
index beaf305..4e92cbe 100644
--- a/libsandbox/libsandbox.c
+++ b/libsandbox/libsandbox.c
@@ -868,20 +868,6 @@ static int check_access(sbcontext_t *sbcontext, int sb_nr, const char *func,
goto out;
}
- /* A very common bug (apparently) is for .py[co] files to fall out
- * of sync with their .py source files. Rather than trigger a hard
- * failure, let's just whine about it. Once python itself gets
- * sorted out, we can drop this #256953.
- */
- size_t len = strlen(resolv_path);
- if (len > 4) {
- const char *py = resolv_path + len - 4;
- if (!strcmp(py, ".pyc") || !strcmp(py, ".pyo")) {
- sbcontext->show_access_violation = false;
- goto out;
- }
- }
-
/* If we are here, and still no joy, and its the access() call,
* do not log it, but just return -1 */
if (sb_nr == SB_NR_ACCESS_WR) {