| Summary: | openssh segfaults when malformed keys are used. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Chad Granum <granum> |
| Component: | Current packages | Assignee: | Daniel Ahlberg (RETIRED) <aliz> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | critical | CC: | kugelfang, rockoo, tigger, vapier |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | these are the keys I was using for a long tiem until the a64 box decided it would be difficult. | ||
|
Description
Chad Granum
2005-02-19 21:38:39 UTC
I decided to generate a new rsa key and abondon the other key types, as well as my long used well distributed keys. now the amd64 no longer segfaults, it works fine, so do all but one of my systems, a pentium4 that now segfaults with the new key. This sounds like a general openssh bug. Reassigning... Chad: can you provide us with the key that generates this segfault? Mike: Sounds for me like a malformed key generates that segfault. Created attachment 52951 [details]
these are the keys I was using for a long tiem until the a64 box decided it would be difficult.
I am afriad the newer keys I tried generating have been lost, I currently am
using a system that works ok where I generated a seperate key for each of the 3
computers and coped the public for each to each and rmeote.
Can you run sshd under gdb so we can get a backtrace please? If you're not sure how, check the instructions at: http://dev.gentoo.org/~tigger/blog/guidexml/auditing-system.html Ask if you need any help. I am sorry it has taken so long to reply, end of quarter at my school been busy, I am afraid I can't do the trace right now, my amd64 system is down from the new glibc bug combined with my own mistakes. My other systems are also down for various changes I have been making since my last final 2 days ago. I might also note that in my flags I used -O3 at the time of the bug report, but I have decided to go to -O2 and wipe the drives (already started before getting the last e-mail about this bug) After everything is set up again I will try the keys and try to post a trace.
-Chad Granum
chad - do u still have the prob w/ openssh-4.0? I am not currently experiencing the bug, I am using the keys I generated a few days after the initial problems on several systems w/ different configs and it all works fine. so closing this one ... lets close it when we have some verification ... the large keys patch has been dropped |
