[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How do we intercept file saving or output to stdout directly
|
From: |
Greg Wooledge |
|
Subject: |
Re: How do we intercept file saving or output to stdout directly |
|
Date: |
Thu, 27 Aug 2020 07:24:34 -0400 |
|
User-agent: |
Mutt/1.10.1 (2018-07-13) |
On Thu, Aug 27, 2020 at 05:26:46AM +0700, Robert Elz wrote:
> 28469 28469 xkbcomp CALL unlink(0x7f7fffffec7b)
> 28469 28469 xkbcomp NAMI "/dev/stdout"
> 28469 28469 xkbcomp RET unlink -1 errno 13 Permission denied
> 28469 28469 xkbcomp CALL open(0x7f7fffffec7b,0xa01,0x1b6)
> 28469 28469 xkbcomp NAMI "/dev/stdout"
> 28469 28469 xkbcomp RET open -1 errno 17 File exists
Ahh. Then I revise my guess to "an attempt to prevent someone sneaking
in a symlink between the unlink and the open", i.e. classic race condition
security for publically writable directories like /tmp.