openssh unix dev - May 2003 - SSH FTP Directories

I am making a SSH FTP client implementation, and I have run into a problem 
with directory listings.  Some servers (e.g. Solaris) place * at the end of 
executable filenames, and when a directory listing is done, these are in 
the listing.  As the * character is a valid filename character in UNIX, I 
need a way to determine if its indeed just an executable file, or if its 
actually part of the filename and should not be truncated.  Is there a good 
way to determine what scenario I'm dealing with?

Thanks,
David

On Tue, 13 May 2003, David Turner wrote:
>
> I am making a SSH FTP client implementation, and I have run into a problem
> with directory listings.  Some servers (e.g. Solaris) place * at the end of
That only happens if you specified the -F flag to ls.  I think you are
confusing what the /bin/ls command does versus what the system calls that
it calls do.  The Solaris kernel certainly does not add a * to the end of
a file name.

Check your shell aliases, if someone is calling /bin/ls to do any listing
then it is quite possible it is picking up your shell aliases.


-- 
Darren J Moffat

I have had the same problem in the past but it was actually related to the
client software.  Clients were using filezilla (terrible product in my
opinion, but unfortunately the standard for windows machines here).  I had
them update their clients and the * after the filename automagically
disappeared.  I would look into your client settings as well as possibly
updating the software.

-
Sonny J Zambrana
Systems Administrator
University Of Pennsylvania

On Tue, 13 May 2003, David Turner wrote:
>
> I am making a SSH FTP client implementation, and I have run into a problem
> with directory listings.  Some servers (e.g. Solaris) place * at the end of
> executable filenames, and when a directory listing is done, these are in
> the listing.  As the * character is a valid filename character in UNIX, I
> need a way to determine if its indeed just an executable file, or if its
> actually part of the filename and should not be truncated.  Is there a good
> way to determine what scenario I'm dealing with?
>
> Thanks,
> David
>
> _______________________________________________
> openssh-unix-dev mailing list
> openssh-unix-dev at mindrot.org
> http://www.mindrot.org/mailman/listinfo/openssh-unix-dev
>