Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1954693 - rlwrap compiled as debug, causing /tmp/rlwrap.debug to be written
Summary: rlwrap compiled as debug, causing /tmp/rlwrap.debug to be written
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: rlwrap
Version: epel8
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Michel Alexandre Salim
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-28 15:34 UTC by Christian Wissel
Modified: 2021-06-07 00:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Christian Wissel 2021-04-28 15:34:08 UTC
Description of problem:
rlwrap has a built-in debug log, IF compiled with debug enabled, as describe here https://github.com/hanslub42/rlwrap/blob/master/BUGS
This causes rlwrap to write a debug log in /tmp/rlwrap.debug on invocation.

This log is not deleted on exit and can't be written to by other users who might be running rlwrap, due to default umask of 0022 creating the file with 0644 permissions.

Version-Release number of selected component (if applicable):
rlwrap-0.44-1.el8.x86_64

How reproducible:
Always

Steps to Reproduce:
1. invoke rlwrap as user 1
2. invoke rlwrap as user 2

Actual results:
rlwrap: error: Cannot open  debug log /tmp/rlwrap.debug for appending: Permission denied


Expected results:
no error

Additional info:
Possible workarounds:
- Change umask to 0002, if users are in a common group
- Leave the debug log in place and change its permissions to 0664 or 0666.


Note You need to log in before you can comment on or make changes to this bug.