Re: [ssh]: Subject emails
this can be configured with topica.com or yahoogroups.com but this list is majordomo is it? JG Volkmar \Mjoellnir\ Seifert wrote: I have a small request, could the moderator of the email list add [ssh]: to the subject of emails that go through this list please? It would be simpler to search for emails I file then and also I can reply to important emails quicker. Would anyone else be interested in this subject modification? Well - nice to have, but each email going through this list has a TO:-Line set to [EMAIL PROTECTED] - that's what I use to filter and sort the mails... But - a reply-to: [EMAIL PROTECTED]-line would be nice... so on a reply the mail goes to the list, not just the one who asked/answered... -Volkmar -- Hypermedia Research Centre Sanyo RD Headquarters, TOKYO http://www.sanyo.co.jp/R_and_D/3dm/
Re: [ssh]: Subject emails
On Fri, 10 Aug 2001, J Grant wrote: Hello I have a small request, could the moderator of the email list add [ssh]: to the subject of emails that go through this list please? It would be simpler to search for emails I file then and also I can reply to important emails quicker. Would anyone else be interested in this subject modification? This is a request, i have only just joined so I dont want to sound authoritive. Regards As a newcomer myself, I was going to ask for the exact same thing, so mails from this list are immediately identifiable in amongst the 4,000 other emails I have to handle a day! ;o) Thanks -- | Gary Wilson, Senior UNIX Analyst, | One2One UNIX Systems Group | Email: [EMAIL PROTECTED] === http://www.one2one.co.uk ===
[ssh]: Boucing emails everytime I post
Hello I think it is better if i just add [ssh]: to every email i attempt to send to this list, (along with changing the reply address to [EMAIL PROTECTED], nearly made the same mistake of replying to myself with this email!) I dont mean to create another long thread that is not SSH related but does everyone else get 2 bounced emails every time they post to the list? These are the 2 offending emails clearly the first will not be back soon so could they both be temporarily be removed and they can re subscribe when there email is working again? -- To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Date: Fri, 10 Aug 2001 3:49:40 +0100 Subject: [ssh]: Subject emails Message-ID: [EMAIL PROTECTED] X-Mozilla-Status: 8003 X-Mozilla-Status2: X-UIDL: YY!!EPk!*W`!9,P!! Von 17. Juli 2001 bis 16. Jaenner 2002 bin ich im Elternkarenz und kann daher Ihre Mails nicht persoenlich beantworten. Bitte wenden Sie sich in EDV-Angelegenheiten an die zustaendigen Personen im ZID, siehe auch: http://zidweb.boku.ac.at/?id=p_girsch From 17th July 2001 to 16th of January 2002 I will be in paternity leave and can not reply until my return. Concerning computer related problems please contact my colleagues, you can find a list of responsibilities at: http://zidweb.boku.ac.at/?id=p_girsch --- To: [EMAIL PROTECTED] Subject: Re: [ssh]: Subject emails References: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: [EMAIL PROTECTED] Precedence: bulk X-Rcpt-To: [EMAIL PROTECTED] Our message was not delivered for the following reason: E-mail Account: blurzer is over the limit of 31457280 bytes. Automated Postmaster - Regards JG Hypermedia Research Centre Sanyo RD Headquarters, TOKYO http://www.sanyo.co.jp/R_and_D/3dm/
OpenSSH 2.5.2p2, Linux, and not accepting passwords
Well this is bizarre. Default install of openssh on this linux box (originally RedHat but I think someone's put a new kernel on it -- it reports itself as 2.2.12-20 when I do uname -a. Sorry, Solaris is my forte, not Linux). It all works. Oh, except for logging in using password authentication. It prompts for a password, but reports incorrect password. And, umm, I'm pretty darn sure I type it correctly. That's not an issue. How the heck do I debug this? -roy
Re: [ssh]: Subject emails
Hello all, I agree ! I use this scheme for the Firewall-one mailling list ([FW1] in the subject), and it work perfectly. Why don't we use this simple trick ? Have a nice day, Bye J Grant wrote: Hello I think it is better if i just add [ssh]: to every email i attempt to send to this list, (along with changing the reply address to [EMAIL PROTECTED], nearly made the same mistake of replying to myself with this email!) I dont mean to create another long thread that is not SSH related but does everyone else get 2 bounced emails every time they post to the list? These are the 2 offending emails clearly the first will not be back soon so could they both be temporarily be removed and they can re subscribe when there email is working again? -- To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Date: Fri, 10 Aug 2001 3:49:40 +0100 Subject: [ssh]: Subject emails Message-ID: [EMAIL PROTECTED] X-Mozilla-Status: 8003 X-Mozilla-Status2: X-UIDL: YY!!EPk!*W`!9,P!! Von 17. Juli 2001 bis 16. Jaenner 2002 bin ich im Elternkarenz und kann daher Ihre Mails nicht persoenlich beantworten. Bitte wenden Sie sich in EDV-Angelegenheiten an die zustaendigen Personen im ZID, siehe auch: http://zidweb.boku.ac.at/?id=p_girsch From 17th July 2001 to 16th of January 2002 I will be in paternity leave and can not reply until my return. Concerning computer related problems please contact my colleagues, you can find a list of responsibilities at: http://zidweb.boku.ac.at/?id=p_girsch --- To: [EMAIL PROTECTED] Subject: Re: [ssh]: Subject emails References: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: [EMAIL PROTECTED] Precedence: bulk X-Rcpt-To: [EMAIL PROTECTED] Our message was not delivered for the following reason: E-mail Account: blurzer is over the limit of 31457280 bytes. Automated Postmaster - Regards JG Hypermedia Research Centre Sanyo RD Headquarters, TOKYO http://www.sanyo.co.jp/R_and_D/3dm/ -- David LEFEVRE CARDIF - Architecture et Sécurité Opérationnelle [EMAIL PROTECTED] - Tél : 01 41 42 76 63 [EMAIL PROTECTED] - Tel : 01 41 42 24 22
SSH logging problem
Hello I have just installed linux first time and wanted to use SSH instead of telnet. I have problem logging to OpenSSH server on it. I looked thru some posts and tried with ssh -v command to see the problem. Any help is appreciated. OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090600f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Seeding random number generator debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: restore_uid debug1: ssh_connect: getuid 3868 geteuid 0 anon 1 debug1: Connecting to servername [ipaddrs] port 22. debug1: temporarily_use_uid: 3868/573 (e=0) debug1: restore_uid debug1: temporarily_use_uid: 3868/573 (e=0) Henrikki Almusa
Re: [ssh]: Boucing emails everytime I post
Hello, Thank you for your reply, I only joined [EMAIL PROTECTED] as it was listed as the active mailing list on the website, I did not know any other mailing list existed. I do not know who is the webmaster. JG Atro Tossavainen wrote: I dont mean to create another long thread that is not SSH related but does everyone else get 2 bounced emails every time they post to the list? Yes. If you keep sending your SSH list mail to [EMAIL PROTECTED], your problem stays. That list is not maintained at all and should disappear very shortly. Use [EMAIL PROTECTED] instead. I have requested the SecurityFocus administration to remove such people from the list. It's not just that they won't be back soon, but also that their autoresponders are misconfigured to answer to all mail, not just personal mail. This behaviour should not happen on any mailing lists. Blurzer has already been removed from [EMAIL PROTECTED], the others are still being worked on. -- Atro Tossavainen (Mr.) / The Institute of Biotechnology at Systems Analyst, Techno-Amish / the University of Helsinki, Finland, +358-9-19158939 UNIX Dinosaur / employs me, but my opinions are my own. URL : http : / / www . iki . fi / atro . tossavainen / -- Hypermedia Research Centre Sanyo RD Headquarters, TOKYO http://www.sanyo.co.jp/R_and_D/3dm/
[ssh] FireWall-1 Mailing list
Just for info : Mailing list : http://www.checkpoint.com/services/mailing.html Newsgroup : http://news.checkpoint.com/nntp.html If you can't have a web access, that's what they say on the mailling list page : The address for the FireWall-1 mailing list address is [EMAIL PROTECTED] To send a command to the mailing list, send an e-mail to that address with the command in the body of the message (the subject line can be left blank). Best regards, David Auteria Wally Winzer Jr. wrote: OFF-TOPIC: What's the Firewall-1 mailing list subscription name? I'd like to subscribe to that list. Thanks. - Wally Winzer Jr. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of LEFEVRE David Sent: Friday, August 10, 2001 12:59 AM Cc: [EMAIL PROTECTED] Subject: Re: [ssh]: Subject emails Hello all, I agree ! I use this scheme for the Firewall-one mailling list ([FW1] in the subject), and it work perfectly. Why don't we use this simple trick ? Have a nice day, Bye J Grant wrote: Hello I think it is better if i just add [ssh]: to every email i attempt to send to this list, (along with changing the reply address to [EMAIL PROTECTED], nearly made the same mistake of replying to myself with this email!) I dont mean to create another long thread that is not SSH related but does everyone else get 2 bounced emails every time they post to the list? These are the 2 offending emails clearly the first will not be back soon so could they both be temporarily be removed and they can re subscribe when there email is working again? -- To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Date: Fri, 10 Aug 2001 3:49:40 +0100 Subject: [ssh]: Subject emails Message-ID: [EMAIL PROTECTED] X-Mozilla-Status: 8003 X-Mozilla-Status2: X-UIDL: YY!!EPk!*W`!9,P!! Von 17. Juli 2001 bis 16. Jaenner 2002 bin ich im Elternkarenz und kann daher Ihre Mails nicht persoenlich beantworten. Bitte wenden Sie sich in EDV-Angelegenheiten an die zustaendigen Personen im ZID, siehe auch: http://zidweb.boku.ac.at/?id=p_girsch From 17th July 2001 to 16th of January 2002 I will be in paternity leave and can not reply until my return. Concerning computer related problems please contact my colleagues, you can find a list of responsibilities at: http://zidweb.boku.ac.at/?id=p_girsch --- To: [EMAIL PROTECTED] Subject: Re: [ssh]: Subject emails References: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: [EMAIL PROTECTED] Precedence: bulk X-Rcpt-To: [EMAIL PROTECTED] Our message was not delivered for the following reason: E-mail Account: blurzer is over the limit of 31457280 bytes. Automated Postmaster - Regards JG Hypermedia Research Centre Sanyo RD Headquarters, TOKYO http://www.sanyo.co.jp/R_and_D/3dm/ -- David LEFEVRE CARDIF - Architecture et Sécurité Opérationnelle [EMAIL PROTECTED] - Tél : 01 41 42 76 63 [EMAIL PROTECTED] - Tel : 01 41 42 24 22 -- David LEFEVRE CARDIF - Architecture et Sécurité Opérationnelle [EMAIL PROTECTED] - Tél : 01 41 42 76 63 [EMAIL PROTECTED] - Tel : 01 41 42 24 22 ** L'intégrité de ce message n'étant pas assurée sur Internet, CARDIF ne peut être tenu responsable de son contenu. Si vous n'êtes pas destinataire de ce message confidentiel, Merci de le détruire et d'avertir immédiatement l'expediteur. The integrity of this message cannot be guaranteed on the Internet. CARDIF can not therefore be considered responsible for the contents. If you are not the intended recipient of this confidential message, then please delete it and notify immediately the sender. **
Re: OpenSSH 2.5.2p2, Linux, and not accepting passwords
Roy S. Rapoport wrote: Well this is bizarre. Default install of openssh on this linux box (originally RedHat but I think someone's put a new kernel on it -- it reports itself as 2.2.12-20 when I do uname -a. Sorry, Solaris is my forte, not Linux). It all works. Oh, except for logging in using password authentication. It prompts for a password, but reports incorrect password. And, umm, I'm pretty darn sure I type it correctly. That's not an issue. How the heck do I debug this? -roy Try searching the archive before submitting questions. This is from a previous post. On Wed, Aug 08, 2001 at 06:32:23AM -0500, Daniel Fayette wrote: Sir, Can you give me a break down of all the steps you did to get openssh to work with RH 6.2. I have been haveing the same problem you described. All I did was unroll openssh-2.9p2 and openssl-0.9.6a, compiled --with-pam and cp contrib/redhat/sshd.pam /etc/pam.d/sshd. I think that was it! Mike -- Wow a memory-mapped fork bomb! Now what on earth did you expect? - lkml -- Dan Fayette Senior Network Engineer USTRANSCOM / J6-TE (Test and Engineering) NCI Information Systems Inc. Phone: 618.229.1817 DSN : 779.1817
Re: OpenSSH 2.5.2p2, Linux, and not accepting passwords
Same problem here... Redhat 6.2 kernel 2.2.19 OpenSSH 2.9p2 Haven't found a solution yet. :-( regards Jan - Original Message - From: Roy S. Rapoport [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, August 10, 2001 9:56 AM Subject: OpenSSH 2.5.2p2, Linux, and not accepting passwords Well this is bizarre. Default install of openssh on this linux box (originally RedHat but I think someone's put a new kernel on it -- it reports itself as 2.2.12-20 when I do uname -a. Sorry, Solaris is my forte, not Linux). It all works. Oh, except for logging in using password authentication. It prompts for a password, but reports incorrect password. And, umm, I'm pretty darn sure I type it correctly. That's not an issue. How the heck do I debug this? -roy
Re: [ssh]: Subject emails
[ On Friday, August 10, 2001 at 10:15:04 (+0900), J Grant wrote: ] Subject: [ssh]: Subject emails I have a small request, could the moderator of the email list add [ssh]: to the subject of emails that go through this list please? It would be simpler to search for emails I file then and also I can reply to important emails quicker. Would anyone else be interested in this subject modification? NO! Absolutely not! This is a request, i have only just joined so I dont want to sound authoritive. There are at least three other headers to filter/sort with. If/when the list is moved to ssh.com it may even gain more headers. Almost every modern mail reader can trivially filter and/or sort on any of the already available headers. If yours can't it's high time you upgraded to something that can. There's absolutely no need to have the MLM software pollute a sender-defined header with redundant information that only gets in the way and takes up valuable space. -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED]
Re: OpenSSH 2.5.2p2, Linux, and not accepting passwords
Just a shot in the dark, but you probably compiled without pam support. ./configure --with-pam Either that or you didn't copy the pam config file from the distribution (under redhat in contrib) to /etc/pam.d/ --James Jan Egeriis writes: Same problem here... Redhat 6.2 kernel 2.2.19 OpenSSH 2.9p2 Haven't found a solution yet. :-( regards Jan - Original Message - From: Roy S. Rapoport [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, August 10, 2001 9:56 AM Subject: OpenSSH 2.5.2p2, Linux, and not accepting passwords Well this is bizarre. Default install of openssh on this linux box (originally RedHat but I think someone's put a new kernel on it -- it reports itself as 2.2.12-20 when I do uname -a. Sorry, Solaris is my forte, not Linux). It all works. Oh, except for logging in using password authentication. It prompts for a password, but reports incorrect password. And, umm, I'm pretty darn sure I type it correctly. That's not an issue. How the heck do I debug this? -roy --James
RE: OpenSSH 2.5.2p2, Linux, and not accepting passwords
Looks like when you built it there were some issues with getting the pam situation worked out. look at the README or INSTALL docs in the tarfile after you built the ssh package... If you are using PAM, you may need to manually install a PAM control file as /etc/pam.d/sshd (or wherever your system prefers to keep them). Note that the service name used to start PAM is __progname, which is the basename of the path of your sshd (e.g., the service name for /usr/sbin/osshd will be osshd). If you have renamed your sshd executable, your PAM configuration may need to be modified. A generic PAM configuration is included as contrib/sshd.pam.generic, you may need to edit it before using it on your system. If you are using a recent version of Red Hat Linux, the config file in contrib/redhat/sshd.pam should be more useful. Failure to install a valid PAM file may result in an inability to use password authentication. On HP-UX 11 and Solaris, the standard /etc/pam.conf configuration will work with sshd (sshd will match the other service name). Abdul Rahman, Ph.D. Manager Sevenspace 703.961.5765 D 703.625.9871 M collaborate.compete.win -Original Message- From: Roy S. Rapoport [mailto:[EMAIL PROTECTED]] Sent: Friday, August 10, 2001 3:56 AM To: [EMAIL PROTECTED] Subject: OpenSSH 2.5.2p2, Linux, and not accepting passwords Well this is bizarre. Default install of openssh on this linux box (originally RedHat but I think someone's put a new kernel on it -- it reports itself as 2.2.12-20 when I do uname -a. Sorry, Solaris is my forte, not Linux). It all works. Oh, except for logging in using password authentication. It prompts for a password, but reports incorrect password. And, umm, I'm pretty darn sure I type it correctly. That's not an issue. How the heck do I debug this? -roy
Updated: Remote Port Forwarding
OK, I found the pseudo patch for channels.c that makes this change: nextstate = (c-host_port == 0 c-type != SSH_CHANNEL_RPORT_LISTENER) ? SSH_CHANNEL_DYNAMIC : SSH_CHANNEL_OPENING; So now ssh -R 4000:localhost:25 works when I telnet localhost 4000 on the remote side. The problem now is that even with -g ssh is only binding to localhost.4000 and not *.4000. Is there a patch for this? Thanks. -- David F. Newman [EMAIL PROTECTED]
Re: [ssh]: Boucing emails everytime I post
ok now i'm confused...i just joined from the openssh page a week ago...are you saying that the list that is mentioned is not the same as the one you have mentioned or they are the same list just with different mailling addy? i would like to add my voice to the adding of [ssh] to the subject headers...i can't get pine to filter this list at all...and i have put the email addy in all the locations just to be safe. since i am sending something in...let me put us back on topic. i am relativly new to using ssh (linux user for only a year). i use ssh.com's desktop client on my win2k box and openssh (slack8 package) on my 2 servers. i am not sure if this is a bug or a feature but i can shell in from all my boxes without needing an ssh key. when i do create an ssh key i am still being authenticated by the shadow password...am i missing something?...if i need to rtfm just tell me thanks ian On Fri, 10 Aug 2001, J Grant wrote: If you keep sending your SSH list mail to [EMAIL PROTECTED], your problem stays. That list is not maintained at all and should disappear very shortly. Use [EMAIL PROTECTED] instead. I have requested the SecurityFocus administration to remove such people from the list. It's not just that they won't be back soon, but also that their autoresponders are misconfigured to answer to all mail, not just personal mail. This behaviour should not happen on any mailing lists.
