Hi,

My repositories are located at SFTP server.
I want to know, how can clients use YUM utilities, inorder to manage their packages.

I am not sure I follow you, did you actually set up a yum repository on your SFTP server or are your clients just SFTP'ing packages from the server?

Searching Yum GIT shows me it doesn't support sftp://-like URI's. Unless you can't change, for hopefully compelling reasons, you will have to curse yourself when you experience related glitches, put up with potentially reduced functionality and throughput and put in way more effort to reach your goal.
So if you can changing your setup to use FTP instead would be less error-prone, easier and efficient.

Three methods to look into if you (think you should) persist:
- SSHFS: Using a pass-phrase-less, IP-range-confined, unprivileged SSH account chrooted in the repository tree, you could make FUSE-SSHFS mount the remote tree locally and use a file:// local repo configuration.
- DeleGate/9.0.4 supports gatewaying SFTP/SSH server for FTP or HTTP clients so you can still use a ftp:// repo configuration.
- Rsync-over-SSH the repo locally and use a file:// local repo configuration file.

1 members found this post helpful.

Thank for you response
I will present with more details what are my needs:
I have equipment with Linux distribution on it.
I would like to have abilites to upgrade SW packages, from both secure (SFTP) and non secure (FTP) servers.
When the upgrade is needed, the user should define the transfer attributes; ip, path, user name, password and protocol type.

Now, regard your solutions:
Option 1 (sshfs) - The mount solution has major differ function than regular file transfer operation
Option 2 - will not enable me to function simultaneous FTP other operations
Option 3 - the same problem idea like option 1

Do you have any other idea?

No, that's FTPS (you know, like HTTPS, POP3S and IMAPS). SFTP is related to SSH.


The procedure you outlined is
0) cumbersome because with a properly configured configuration file no user should need to present that information, it does come across as
1) untrustworthy, potentially resulting in an incomplete update or worse because common usage should be to just run 'yum update' or 'yum update [packagename]' and probably
2) an erosion of the package management best practices the distribution did set.



Unless you forgot to mention even more details you best use anonymous FTP.
If Yum doesn't deal with FTPS then either don't use FTPS or bridge it to regular anon FTP.

1 members found this post helpful.

Hi,

My application must support SFTP server (over SSH) and the U/I for the user need to be like FTP configuration settings.

As I know, YUM uses Curl library for it trnasport layer.
This library support also SFTP protocol.
I wounder, how much effort does it needed, for making changes in YUM code, in order to support also SFTP protocol.
Do you have any quess for this ?