Bug 165032 - kerberized rcp can't copy files over 2GB
Summary: kerberized rcp can't copy files over 2GB
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: krb5 (Show other bugs)
(Show other bugs)
Version: 3.0
Hardware: All Linux
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Brian Brock
Depends On:
Blocks: 168426 198824
TreeView+ depends on / blocked
Reported: 2005-08-03 18:25 UTC by Neil Horman
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version: RHEA-2006-0080
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-15 15:42:47 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch to correct typing of size variable so as not to overflow and break rcp transfer (441 bytes, patch)
2005-08-03 18:25 UTC, Neil Horman
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2006:0080 qe-ready SHIPPED_LIVE krb5 enhancement update 2006-03-14 05:00:00 UTC

Description Neil Horman 2005-08-03 18:25:30 UTC
Description of problem:
kerberized rcp can't transfer files over 2GB in size.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.set up a client on a kerberos realm
2.kinit to a user that has access to both the rcp client and rcp server machine
3.rcp a file more than 2GB in size from the server to the client
Actual results:
rcp fails with lost connection, or size not delimited error.

Expected results:
file should be transferred w/o errors

Additional info:

Comment 1 Neil Horman 2005-08-03 18:25:31 UTC
Created attachment 117419 [details]
patch to correct typing of size variable so as not to overflow and break rcp transfer

Comment 14 Red Hat Bugzilla 2006-03-15 15:42:47 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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