Bug 447031 - smbclient ignores the -A option
Summary: smbclient ignores the -A option
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: samba
Version: 9
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Simo Sorce
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-17 04:24 UTC by Todd J Martin
Modified: 2009-07-14 16:31 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-07-14 16:31:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Todd J Martin 2008-05-17 04:24:40 UTC
Description of problem:

The -A (--authentication-file) command line argument does not get used by
smbclient.  This makes it difficult to use scripts which need to login to access
samba resources.

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

[todd@hobbes ~]$ smbclient --version
Version 3.2.0pre3-9.fc9

How reproducible:


Steps to Reproduce:
1. Create a file with authentication information for a server
echo "username = todd" > auth
echo "password = secret" >> auth
echo "domain = MARTIN" >> auth

2. Try to get a listing from the server named perl using that authentication
information
smbclient -A auth -L perl

  
Actual results:

[todd@hobbes ~]$ smbclient -A auth -L perl
Enter todd's password:

smbclient is asking me to enter the password instead of using the password that
is in the auth file.

Expected results:

In Fedora 8, smbclient would use the authentication information from the file
like this:

[todd@perl]$ smbclient -A auth -L perl
Domain=[PERL] OS=[Unix] Server=[Samba 3.0.28a-0.fc8]

        Sharename       Type      Comment
        ---------       ----      -------
        media           Disk      Media Files
        IPC$            IPC       IPC Service (Samba Server)
        laser           Printer   laser
        todd            Disk      Home Directories
Domain=[PERL] OS=[Unix] Server=[Samba 3.0.28a-0.fc8]

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
        MARTIN               PERL



Additional info:

The samba server is running Fedora 8.

Comment 1 Bug Zapper 2009-06-10 00:55:24 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2009-07-14 16:31:08 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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