Build OpenSSH client only












2















I'm trying to build OpenSSH 7.9p1 from source, but I can't find a way to delete (or not include), for instance, ssh-agent, ssh-keygen, scp, sftp, sshd, etc. – of course, assuming none of those are required for the ssh command to work.



Ideally I would only need the client: the ssh command, but again, I'm not sure what other pieces are required. I think most of what's build/installed is used by the server, not by the client.










share|improve this question

























  • Please tell us why you need a special openssh-client: 1. Are you running or creating a linux distro? Please tell us about your operating system. 2. Are you creating some 'fool-proof' system with client computers, that can only run a few necessary programs, and one of them is ssh, but not transfer files, so you want to remove sftp and scp ? 3. Or something else?

    – sudodus
    Jan 30 at 8:03








  • 1





    I have to build it from source, it's to make a Flatpak, and the SSH client is a dependency. I don't want to shovel everything-SSH there if it's not needed. I was going the route @JeffSchaller proposed but I first wanted to know if there was another way. I can identify the location(s) where the other (potentially) unneeded files are "installed" and remove them, but like I said I would like to avoid that if there is a way to tell configure to not consider some "packages", etc. For instance, the openssh-client from Ubuntu would be perfect for me case, but I can't use a .deb file.

    – x80486
    Jan 30 at 12:50
















2















I'm trying to build OpenSSH 7.9p1 from source, but I can't find a way to delete (or not include), for instance, ssh-agent, ssh-keygen, scp, sftp, sshd, etc. – of course, assuming none of those are required for the ssh command to work.



Ideally I would only need the client: the ssh command, but again, I'm not sure what other pieces are required. I think most of what's build/installed is used by the server, not by the client.










share|improve this question

























  • Please tell us why you need a special openssh-client: 1. Are you running or creating a linux distro? Please tell us about your operating system. 2. Are you creating some 'fool-proof' system with client computers, that can only run a few necessary programs, and one of them is ssh, but not transfer files, so you want to remove sftp and scp ? 3. Or something else?

    – sudodus
    Jan 30 at 8:03








  • 1





    I have to build it from source, it's to make a Flatpak, and the SSH client is a dependency. I don't want to shovel everything-SSH there if it's not needed. I was going the route @JeffSchaller proposed but I first wanted to know if there was another way. I can identify the location(s) where the other (potentially) unneeded files are "installed" and remove them, but like I said I would like to avoid that if there is a way to tell configure to not consider some "packages", etc. For instance, the openssh-client from Ubuntu would be perfect for me case, but I can't use a .deb file.

    – x80486
    Jan 30 at 12:50














2












2








2


0






I'm trying to build OpenSSH 7.9p1 from source, but I can't find a way to delete (or not include), for instance, ssh-agent, ssh-keygen, scp, sftp, sshd, etc. – of course, assuming none of those are required for the ssh command to work.



Ideally I would only need the client: the ssh command, but again, I'm not sure what other pieces are required. I think most of what's build/installed is used by the server, not by the client.










share|improve this question
















I'm trying to build OpenSSH 7.9p1 from source, but I can't find a way to delete (or not include), for instance, ssh-agent, ssh-keygen, scp, sftp, sshd, etc. – of course, assuming none of those are required for the ssh command to work.



Ideally I would only need the client: the ssh command, but again, I'm not sure what other pieces are required. I think most of what's build/installed is used by the server, not by the client.







package-management compiling packaging configure






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 30 at 6:56









Kusalananda

129k16243400




129k16243400










asked Jan 30 at 3:53









x80486x80486

274113




274113













  • Please tell us why you need a special openssh-client: 1. Are you running or creating a linux distro? Please tell us about your operating system. 2. Are you creating some 'fool-proof' system with client computers, that can only run a few necessary programs, and one of them is ssh, but not transfer files, so you want to remove sftp and scp ? 3. Or something else?

    – sudodus
    Jan 30 at 8:03








  • 1





    I have to build it from source, it's to make a Flatpak, and the SSH client is a dependency. I don't want to shovel everything-SSH there if it's not needed. I was going the route @JeffSchaller proposed but I first wanted to know if there was another way. I can identify the location(s) where the other (potentially) unneeded files are "installed" and remove them, but like I said I would like to avoid that if there is a way to tell configure to not consider some "packages", etc. For instance, the openssh-client from Ubuntu would be perfect for me case, but I can't use a .deb file.

    – x80486
    Jan 30 at 12:50



















  • Please tell us why you need a special openssh-client: 1. Are you running or creating a linux distro? Please tell us about your operating system. 2. Are you creating some 'fool-proof' system with client computers, that can only run a few necessary programs, and one of them is ssh, but not transfer files, so you want to remove sftp and scp ? 3. Or something else?

    – sudodus
    Jan 30 at 8:03








  • 1





    I have to build it from source, it's to make a Flatpak, and the SSH client is a dependency. I don't want to shovel everything-SSH there if it's not needed. I was going the route @JeffSchaller proposed but I first wanted to know if there was another way. I can identify the location(s) where the other (potentially) unneeded files are "installed" and remove them, but like I said I would like to avoid that if there is a way to tell configure to not consider some "packages", etc. For instance, the openssh-client from Ubuntu would be perfect for me case, but I can't use a .deb file.

    – x80486
    Jan 30 at 12:50

















Please tell us why you need a special openssh-client: 1. Are you running or creating a linux distro? Please tell us about your operating system. 2. Are you creating some 'fool-proof' system with client computers, that can only run a few necessary programs, and one of them is ssh, but not transfer files, so you want to remove sftp and scp ? 3. Or something else?

– sudodus
Jan 30 at 8:03







Please tell us why you need a special openssh-client: 1. Are you running or creating a linux distro? Please tell us about your operating system. 2. Are you creating some 'fool-proof' system with client computers, that can only run a few necessary programs, and one of them is ssh, but not transfer files, so you want to remove sftp and scp ? 3. Or something else?

– sudodus
Jan 30 at 8:03






1




1





I have to build it from source, it's to make a Flatpak, and the SSH client is a dependency. I don't want to shovel everything-SSH there if it's not needed. I was going the route @JeffSchaller proposed but I first wanted to know if there was another way. I can identify the location(s) where the other (potentially) unneeded files are "installed" and remove them, but like I said I would like to avoid that if there is a way to tell configure to not consider some "packages", etc. For instance, the openssh-client from Ubuntu would be perfect for me case, but I can't use a .deb file.

– x80486
Jan 30 at 12:50





I have to build it from source, it's to make a Flatpak, and the SSH client is a dependency. I don't want to shovel everything-SSH there if it's not needed. I was going the route @JeffSchaller proposed but I first wanted to know if there was another way. I can identify the location(s) where the other (potentially) unneeded files are "installed" and remove them, but like I said I would like to avoid that if there is a way to tell configure to not consider some "packages", etc. For instance, the openssh-client from Ubuntu would be perfect for me case, but I can't use a .deb file.

– x80486
Jan 30 at 12:50










1 Answer
1






active

oldest

votes


















3














Yes, you can do this with the default build system provided.



If you look at the Makefile that is generated by running the provided ./configure script, you should see that the default (first) target is



TARGETS=ssh$(EXEEXT) sshd$(EXEEXT) ssh-add$(EXEEXT) ssh-keygen$(EXEEXT) ssh-keyscan${EXEEXT} ssh-keysign${EXEEXT} ssh-pkcs11-helper$(EXEEXT) ssh-agent$(EXEEXT) scp$(EXEEXT) sftp-server$(EXEEXT) sftp$(EXEEXT)


(for Unix-like systems, $(EXEEXT) should be empty). Each has its own separate build target / rule so for example you can do:



make ssh


to make only the client.



Ex.



$ make ssh

<snip>

$ find . -type f -executable -newermt yesterday
./config.status
./ssh

$ ./ssh -V
OpenSSH_7.9p1, OpenSSL 1.1.0g 2 Nov 2017





share|improve this answer
























  • Great, let me try that first and I'll accept your answer. Thanks for the info!

    – x80486
    Jan 30 at 13:40











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497602%2fbuild-openssh-client-only%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









3














Yes, you can do this with the default build system provided.



If you look at the Makefile that is generated by running the provided ./configure script, you should see that the default (first) target is



TARGETS=ssh$(EXEEXT) sshd$(EXEEXT) ssh-add$(EXEEXT) ssh-keygen$(EXEEXT) ssh-keyscan${EXEEXT} ssh-keysign${EXEEXT} ssh-pkcs11-helper$(EXEEXT) ssh-agent$(EXEEXT) scp$(EXEEXT) sftp-server$(EXEEXT) sftp$(EXEEXT)


(for Unix-like systems, $(EXEEXT) should be empty). Each has its own separate build target / rule so for example you can do:



make ssh


to make only the client.



Ex.



$ make ssh

<snip>

$ find . -type f -executable -newermt yesterday
./config.status
./ssh

$ ./ssh -V
OpenSSH_7.9p1, OpenSSL 1.1.0g 2 Nov 2017





share|improve this answer
























  • Great, let me try that first and I'll accept your answer. Thanks for the info!

    – x80486
    Jan 30 at 13:40
















3














Yes, you can do this with the default build system provided.



If you look at the Makefile that is generated by running the provided ./configure script, you should see that the default (first) target is



TARGETS=ssh$(EXEEXT) sshd$(EXEEXT) ssh-add$(EXEEXT) ssh-keygen$(EXEEXT) ssh-keyscan${EXEEXT} ssh-keysign${EXEEXT} ssh-pkcs11-helper$(EXEEXT) ssh-agent$(EXEEXT) scp$(EXEEXT) sftp-server$(EXEEXT) sftp$(EXEEXT)


(for Unix-like systems, $(EXEEXT) should be empty). Each has its own separate build target / rule so for example you can do:



make ssh


to make only the client.



Ex.



$ make ssh

<snip>

$ find . -type f -executable -newermt yesterday
./config.status
./ssh

$ ./ssh -V
OpenSSH_7.9p1, OpenSSL 1.1.0g 2 Nov 2017





share|improve this answer
























  • Great, let me try that first and I'll accept your answer. Thanks for the info!

    – x80486
    Jan 30 at 13:40














3












3








3







Yes, you can do this with the default build system provided.



If you look at the Makefile that is generated by running the provided ./configure script, you should see that the default (first) target is



TARGETS=ssh$(EXEEXT) sshd$(EXEEXT) ssh-add$(EXEEXT) ssh-keygen$(EXEEXT) ssh-keyscan${EXEEXT} ssh-keysign${EXEEXT} ssh-pkcs11-helper$(EXEEXT) ssh-agent$(EXEEXT) scp$(EXEEXT) sftp-server$(EXEEXT) sftp$(EXEEXT)


(for Unix-like systems, $(EXEEXT) should be empty). Each has its own separate build target / rule so for example you can do:



make ssh


to make only the client.



Ex.



$ make ssh

<snip>

$ find . -type f -executable -newermt yesterday
./config.status
./ssh

$ ./ssh -V
OpenSSH_7.9p1, OpenSSL 1.1.0g 2 Nov 2017





share|improve this answer













Yes, you can do this with the default build system provided.



If you look at the Makefile that is generated by running the provided ./configure script, you should see that the default (first) target is



TARGETS=ssh$(EXEEXT) sshd$(EXEEXT) ssh-add$(EXEEXT) ssh-keygen$(EXEEXT) ssh-keyscan${EXEEXT} ssh-keysign${EXEEXT} ssh-pkcs11-helper$(EXEEXT) ssh-agent$(EXEEXT) scp$(EXEEXT) sftp-server$(EXEEXT) sftp$(EXEEXT)


(for Unix-like systems, $(EXEEXT) should be empty). Each has its own separate build target / rule so for example you can do:



make ssh


to make only the client.



Ex.



$ make ssh

<snip>

$ find . -type f -executable -newermt yesterday
./config.status
./ssh

$ ./ssh -V
OpenSSH_7.9p1, OpenSSL 1.1.0g 2 Nov 2017






share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 30 at 13:06









steeldriversteeldriver

36.1k35286




36.1k35286













  • Great, let me try that first and I'll accept your answer. Thanks for the info!

    – x80486
    Jan 30 at 13:40



















  • Great, let me try that first and I'll accept your answer. Thanks for the info!

    – x80486
    Jan 30 at 13:40

















Great, let me try that first and I'll accept your answer. Thanks for the info!

– x80486
Jan 30 at 13:40





Great, let me try that first and I'll accept your answer. Thanks for the info!

– x80486
Jan 30 at 13:40


















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497602%2fbuild-openssh-client-only%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

is 'sed' thread safe

How to make a Squid Proxy server?