Re: sshd in current....no config files in /etc/ssh
[EMAIL PROTECTED] (FreeBSD mailing list) writes: You know people, it's quite sad that those with knowledge simply refuse to answer simple questions without "RTFM" attitudes and indirect (and more frequently direct) insults to intelligence and sensibilities. The answer `run mergemaster' will work for the next, similar, problem. The answer you gave won't work for anything but ssh. kai -- ~/.signature: No such file or directory To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sshd in current....no config files in /etc/ssh
I just finished a make world for -current todayd cvsup. All went well but I was planning on setting up ssh between my home systems and aneother system on the net, but I find there are no config files in /etc/ssh. I do have the crypto sources also. Thanks Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
On Tue, Mar 07, 2000 at 08:52:22AM -0800, Bill Woods wrote: I just finished a make world for -current todayd cvsup. All went well but I was planning on setting up ssh between my home systems and aneother system on the net, but I find there are no config files in /etc/ssh. I do have the crypto sources also. did you run mergemaster after the make world? regards, -oscar -- pgp public key: finger [EMAIL PROTECTED] pgp fingerprint: 6D 18 8C 90 4C DF F0 4B DF 35 1F 69 A1 33 C7 BC To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
No, I dident. I dident have old ssh (the port one) to merge. This is the 1st time use of ssh on this system. On 07-Mar-00 Oscar Bonilla wrote: On Tue, Mar 07, 2000 at 08:52:22AM -0800, Bill Woods wrote: I just finished a make world for -current todayd cvsup. All went well but I was planning on setting up ssh between my home systems and aneother system on the net, but I find there are no config files in /etc/ssh. I do have the crypto sources also. did you run mergemaster after the make world? regards, -oscar -- pgp public key: finger [EMAIL PROTECTED] pgp fingerprint: 6D 18 8C 90 4C DF F0 4B DF 35 1F 69 A1 33 C7 BC To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- E-Mail: [EMAIL PROTECTED] Date: 07-Mar-00 Time: 10:33:57l -- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
Regardless, without using mergemaster, the NEW config files will never have gotten placed into /etc Make world does not in and of itself in any way touch those configuration files. - Jay Oliver - Original Message - From: "William Woods" [EMAIL PROTECTED] To: "Oscar Bonilla" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, March 07, 2000 1:34 PM Subject: Re: sshd in currentno config files in /etc/ssh No, I dident. I dident have old ssh (the port one) to merge. This is the 1st time use of ssh on this system. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
OK, well, I useally merge files by hand because I am not familiar with mergemaster..how would I do this by hand? On 07-Mar-00 Jay Oliver wrote: Regardless, without using mergemaster, the NEW config files will never have gotten placed into /etc Make world does not in and of itself in any way touch those configuration files. - Jay Oliver - Original Message - From: "William Woods" [EMAIL PROTECTED] To: "Oscar Bonilla" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, March 07, 2000 1:34 PM Subject: Re: sshd in currentno config files in /etc/ssh No, I dident. I dident have old ssh (the port one) to merge. This is the 1st time use of ssh on this system. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- E-Mail: [EMAIL PROTECTED] Date: 07-Mar-00 Time: 11:14:52l -- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
William Woods wrote: OK, well, I useally merge files by hand because I am not familiar with mergemaster..how would I do this by hand? man mergemaster If you insist on doing it by hand, start with "diff -urN /etc /usr/src/etc" -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
Good god, I am saying that the files to merger dont existthere is nothing to merge... This is the eror I get when trying to run ssdd /etc/ssh/sshd_config: No such file or directory the file sshd_config does not exist on my system to merge... On 07-Mar-00 Steve Kargl wrote: William Woods wrote: OK, well, I useally merge files by hand because I am not familiar with mergemaster..how would I do this by hand? man mergemaster If you insist on doing it by hand, start with "diff -urN /etc /usr/src/etc" -- Steve -- E-Mail: [EMAIL PROTECTED] Date: 07-Mar-00 Time: 11:29:42l -- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
That is what mergemaster does, it places everything you could ever need in a temporary root, diffs it against /etc, merges anything existing, tells you if there is a file that you do not have, you answer 'i' and it installs the default file. Despite the name, mergemaster is not only for merging, it's about the most handy tool I've ever come across for make worlds, makes updating configs a very easy task indeed. Doug definately deserves a few hundred pats on the back for that program. Matt -- Matt Heckaman [[EMAIL PROTECTED]|[EMAIL PROTECTED]] [Please do not send me] !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] On Tue, 7 Mar 2000, William Woods wrote: : Date: Tue, 7 Mar 2000 14:31:26 -0500 : From: William Woods [EMAIL PROTECTED] : Reply-To: [EMAIL PROTECTED] : To: Steve Kargl [EMAIL PROTECTED] : Cc: [EMAIL PROTECTED], Jay Oliver [EMAIL PROTECTED], : [EMAIL PROTECTED] : Subject: Re: sshd in currentno config files in /etc/ssh : : Good god, I am saying that the files to merger dont existthere is nothing : to merge... : : This is the eror I get when trying to run ssdd : : /etc/ssh/sshd_config: No such file or directory : : the file sshd_config does not exist on my system to merge... : : On 07-Mar-00 Steve Kargl wrote: : William Woods wrote: : OK, well, I useally merge files by hand because I am not familiar with : mergemaster..how would I do this by hand? : : : man mergemaster : : If you insist on doing it by hand, start with : "diff -urN /etc /usr/src/etc" : : -- : Steve : : : -- : E-Mail: [EMAIL PROTECTED] : Date: 07-Mar-00 : Time: 11:29:42l : -- : : NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, : Subchapter II, 227, and all unsolicited commercial e-mail sent to this : address is subject to a download and archival fee in the amount of $500 US : : : : To Unsubscribe: send mail to [EMAIL PROTECTED] : with "unsubscribe freebsd-current" in the body of the message : To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
troutmask:root[204] locate sshd_config /usr/local/etc/sshd_config /usr/src/crypto/openssh/sshd_config man locate man 8 sshd William Woods wrote: Good god, I am saying that the files to merger dont existthere is nothing to merge... I don't see you making that statement below. You said "OK, well, I useally merge files by hand because I am not familiar with mergemaster..how would I do this by hand?" "man mergemaster" will familiarize you with the command. "diff ..." is how you might start to do it by hand. If a file does not appear to exist (oh, ah, such as /etc/sshd_config), try RTFM. This is the eror I get when trying to run ssdd /etc/ssh/sshd_config: No such file or directory the file sshd_config does not exist on my system to merge... On 07-Mar-00 Steve Kargl wrote: William Woods wrote: OK, well, I useally merge files by hand because I am not familiar with mergemaster..how would I do this by hand? man mergemaster If you insist on doing it by hand, start with "diff -urN /etc /usr/src/etc" -- Steve -- E-Mail: [EMAIL PROTECTED] Date: 07-Mar-00 Time: 11:29:42l -- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
I did the following to manually set up ssh after the world build: cp /usr/src/crypto/openssh/sshd_config /etc/ssh It's as simple as that. Then when you reboot next, the host key will be regenerated by /etc/rc.network, provided you updated that from /usr/src/etc as well. If you don't want to wait until reboot to start sshd, do: /usr/bin/ssh-keygen -N "" -f /etc/ssh/ssh_host_key This is the command used by /etc/rc.network. It Worked For Me. You know people, it's quite sad that those with knowledge simply refuse to answer simple questions without "RTFM" attitudes and indirect (and more frequently direct) insults to intelligence and sensibilities. There is absolutely no reason why you can't submit the help, with suggestion toward ones perception of "the Right Way" to do it, rather than beat the issue to death with superior posturing. Pursue your Ideal Methodologies, but try some constructiveness rather than the Attitudes of the Norm common on other development lists. -scott -- Scott G. Akmentins-Taylor InterNet: [EMAIL PROTECTED] MRY Systems [EMAIL PROTECTED] (Skots Gregorijs Akmentins-Teilors -- just call me "Skots") - Labak miris neka sarkans - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
ThanksI used that "i" option and it worked...well, almost. I have the files I need in /etc/ssh but when I start sshd I get this now. error: Could not load host key: /etc/ssh/ssh_host_key: No such file or directory On 07-Mar-00 Matt Heckaman wrote: That is what mergemaster does, it places everything you could ever need in a temporary root, diffs it against /etc, merges anything existing, tells you if there is a file that you do not have, you answer 'i' and it installs the default file. Despite the name, mergemaster is not only for merging, it's about the most handy tool I've ever come across for make worlds, makes updating configs a very easy task indeed. Doug definately deserves a few hundred pats on the back for that program. Matt -- Matt Heckaman [[EMAIL PROTECTED]|[EMAIL PROTECTED]] [Please do not send me] !Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail] On Tue, 7 Mar 2000, William Woods wrote: : Date: Tue, 7 Mar 2000 14:31:26 -0500 : From: William Woods [EMAIL PROTECTED] : Reply-To: [EMAIL PROTECTED] : To: Steve Kargl [EMAIL PROTECTED] : Cc: [EMAIL PROTECTED], Jay Oliver [EMAIL PROTECTED], : [EMAIL PROTECTED] : Subject: Re: sshd in currentno config files in /etc/ssh : : Good god, I am saying that the files to merger dont existthere is : nothing : to merge... : : This is the eror I get when trying to run ssdd : : /etc/ssh/sshd_config: No such file or directory : : the file sshd_config does not exist on my system to merge... : : On 07-Mar-00 Steve Kargl wrote: : William Woods wrote: : OK, well, I useally merge files by hand because I am not familiar with : mergemaster..how would I do this by hand? : : : man mergemaster : : If you insist on doing it by hand, start with : "diff -urN /etc /usr/src/etc" : : -- : Steve : : : -- : E-Mail: [EMAIL PROTECTED] : Date: 07-Mar-00 : Time: 11:29:42l : -- : : NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, : Subchapter II, 227, and all unsolicited commercial e-mail sent to this : address is subject to a download and archival fee in the amount of $500 US : : : : To Unsubscribe: send mail to [EMAIL PROTECTED] : with "unsubscribe freebsd-current" in the body of the message : To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- E-Mail: [EMAIL PROTECTED] Date: 07-Mar-00 Time: 11:59:10l -- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
On Tue, 7 Mar 2000, William Woods wrote: ThanksI used that "i" option and it worked...well, almost. I have the files I need in /etc/ssh but when I start sshd I get this now. error: Could not load host key: /etc/ssh/ssh_host_key: No such file or directory It will be created for you next time you boot, or you can do it by hand (man ssh-keygen).. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
Thank you... On 07-Mar-00 Kris Kennaway wrote: On Tue, 7 Mar 2000, William Woods wrote: ThanksI used that "i" option and it worked...well, almost. I have the files I need in /etc/ssh but when I start sshd I get this now. error: Could not load host key: /etc/ssh/ssh_host_key: No such file or directory It will be created for you next time you boot, or you can do it by hand (man ssh-keygen).. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- E-Mail: [EMAIL PROTECTED] Date: 07-Mar-00 Time: 12:50:01l -- NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, and all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of $500 US To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
On Tue, 7 Mar 2000, William Woods wrote: Good god, I am saying that the files to merger dont existthere is nothing to merge... This is the eror I get when trying to run ssdd /etc/ssh/sshd_config: No such file or directory the file sshd_config does not exist on my system to merge... That's because it's not under /etc until *after* you've run mergemaster. Right now it's sitting in /var/tmp/tmproot/etc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
ThanksI used that "i" option and it worked...well, almost. I have the files
I need in /etc/ssh but when I start sshd I get this now.
error: Could not load host key: /etc/ssh/ssh_host_key: No such file or
directory
If you want to track current you must use mergemaster.
This is probably because you haven't updated rc.network...
case ${sshd_enable} in
[Yy][Ee][Ss])
if [ ! -f /etc/ssh/ssh_host_key ]; then
echo ' creating ssh host key';
/usr/bin/ssh-keygen -N "" -f /etc/ssh/ssh_host_key
fi
;;
esac
My host key was generated automatically when I rebooted and I was
quite impressed.
Just type 'mergemaster' as root. It's interactive and doesn't overwrite
anything automatically.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
Thanks,
I had been doing things manually for a while now. I dod look at mergemaster and
used it for ssh and it worked well. I am planning on investigating it more
later on today.
On 07-Mar-00 Jake Burkholder wrote:
ThanksI used that "i" option and it worked...well, almost. I have the
files
I need in /etc/ssh but when I start sshd I get this now.
error: Could not load host key: /etc/ssh/ssh_host_key: No such file or
directory
If you want to track current you must use mergemaster.
This is probably because you haven't updated rc.network...
case ${sshd_enable} in
[Yy][Ee][Ss])
if [ ! -f /etc/ssh/ssh_host_key ]; then
echo ' creating ssh host key';
/usr/bin/ssh-keygen -N "" -f /etc/ssh/ssh_host_key
fi
;;
esac
My host key was generated automatically when I rebooted and I was
quite impressed.
Just type 'mergemaster' as root. It's interactive and doesn't overwrite
anything automatically.
--
E-Mail: [EMAIL PROTECTED]
Date: 07-Mar-00
Time: 14:15:25l
--
NOTICE TO BULK E-MAILERS: Pursuant to US Code, Title 47, Chapter 5,
Subchapter II, 227, and all unsolicited commercial e-mail sent to this
address is subject to a download and archival fee in the amount of $500 US
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
On Tue, Mar 07, 2000 at 12:02:38PM +, FreeBSD mailing list wrote: You know people, it's quite sad that those with knowledge simply refuse to answer simple questions without "RTFM" attitudes and indirect (and more frequently direct) insults to intelligence and sensibilities. When you have more experience helping people on a frequent basis, perhaps you will revise this statement. Try helping folks out every day on IRC for 2 or 3 years and tell me what you think THEN. Alternative: answer every question asked on freebsd-questions for same period. You'll see the point once you accomplish this. There is absolutely no reason why you can't submit the help, with suggestion toward ones perception of "the Right Way" to do it, rather than beat the issue to death with superior posturing. There is absolutely no reason why people should lift a finger to help somebody else when said question/inquiry has been documented somewhere on the web or in the manpages, or someplace else. You're right. However, there is no reason to lift a finger to not help someone either. If you don't want to help, simply don't. You save everyone energy. Being a jerk isn't going to keep people from posting elementary questions, that's a fact. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
Good god, I am saying that the files to merger dont existthere is nothing to merge... You need to be reading -current or stop running it. The issue with /etc/ssh/sshd_config has been discussed to death. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
You know people, it's quite sad that those with knowledge simply refuse to answer simple questions without "RTFM" attitudes and indirect (and What you and others don't seem to understand is that there are also "minimum responsibilities" that have been established for users of our non-mainstream branches. Those minimums are published in the Handbook and other documents and have been established in order to ensure that the developers don't spend more time answering the same questions over and over in email than they do in actually writing code and improving FreeBSD in various ways. Such a thing would be bad for everyone and so a number of people, including myself, take it upon ourselves to drive the right behavior by not simply answering "needless" questions and thus encouraging the querants, in their initial success, to follow those questions up with more. One of the requirements for running -current vs one of our mainstream releases is that people read this mailing list, for example, and that's a necessary requirement because we'd otherwise have to "announce" the same issues in -current over and over again for each person to run across some transitional thing. The -current branch is NOT intended for the average Joe, it's very directly aimed at developers and developers have to deal with the idea of minimum effective requirements every day so this shouldn't come as a shock to anyone either. If it does, you're in the wrong place and should go back to a mainstream release of FreeBSD with all due haste. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
Matt Heckaman wrote: Despite the name, mergemaster is not only for merging, it's about the most handy tool I've ever come across for make worlds, makes updating configs a very easy task indeed. Doug definately deserves a few hundred pats on the back for that program. Well, kind words are always appreciated... of course money is the universal language of appreciation... *chuckle* Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
On Tue, Mar 07, 2000 at 11:31:26AM -0800, William Woods wrote: Good god, I am saying that the files to merger dont existthere is nothing to merge... If you insist on doing it by hand, start with "diff -urN /etc /usr/src/etc" Perhaps you are not familar with the "-N" option to diff. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
