RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1147717 - free'ing a not-connected agent closes STDIN
Summary: free'ing a not-connected agent closes STDIN
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libssh2
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: Stefan Kremen
URL:
Whiteboard:
Depends On:
Blocks: 1066486 1249581
TreeView+ depends on / blocked
 
Reported: 2014-09-29 23:34 UTC by Jakub Filak
Modified: 2016-12-01 00:48 UTC (History)
3 users (show)

Fixed In Version: libssh2-1.4.3-9.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1249581 (view as bug list)
Environment:
Last Closed: 2015-11-19 05:21:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Example (899 bytes, text/plain)
2014-09-29 23:34 UTC, Jakub Filak
no flags Details
Propsed patch (399 bytes, patch)
2014-09-29 23:34 UTC, Jakub Filak
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2140 0 normal SHIPPED_LIVE Low: libssh2 security and bug fix update 2015-11-19 08:17:03 UTC

Description Jakub Filak 2014-09-29 23:34:13 UTC
Created attachment 942543 [details]
Example

Description of problem:
I had been playing with curl_easy_perform() when I found out that I cannot read from STDIN after uploading to a "scp://" URL.

Version-Release number of selected component (if applicable):
libssh2-1.4.3-8.el7_0.x86_64

How reproducible:
Always

Steps to Reproduce:
1. run the attached example
2.
3.

Actual results:
fcntl(0, F_GETFD): 0
libssh2_agent_{init,connect,free}
fcntl(0, F_GETFD): Bad file descriptor

Expected results:
fcntl(0, F_GETFD): 0
libssh2_agent_{init,connect,free}
fcntl(0, F_GETFD): 0

Additional info:

Comment 1 Jakub Filak 2014-09-29 23:34:56 UTC
Created attachment 942544 [details]
Propsed patch

Comment 4 Kamil Dudka 2014-10-10 11:16:36 UTC
Thanks for the bug report, minimal, example, and patch!

upstream commit:
http://git.libssh2.org/?p=libssh2.git;a=commitdiff;h=1ad20ac7

Comment 5 Kamil Dudka 2014-10-10 12:01:33 UTC
fixed in libssh2-1.4.3-16.fc22, libssh2-1.4.3-16.fc21, libssh2-1.4.3-10.fc20, and libssh2-1.4.3-8.fc19

Comment 12 errata-xmlrpc 2015-11-19 05:21:00 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-2140.html


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