search for: skalasoft

On command: #kill -9 `cat /var/run/sshd.pid` sshd leave pid file ! sshd.c code: =============== .... /* * Arrange to restart on SIGHUP. The handler needs * listen_sock. */ signal(SIGHUP, sighup_handler); signal(SIGTERM, sigterm_handler); signal(SIGQUIT, sigterm_handler); .... =============== Missing line is : signal(SIGKILL, sigterm_handler);

http://bugzilla.mindrot.org/show_bug.cgi?id=413 markus at openbsd.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From markus at openbsd.org 2003-02-03 19:50 ------- i'll look into this. ------- You are

http://bugzilla.mindrot.org/show_bug.cgi?id=431 ------- Additional Comments From gfernandez at livevault.com 2002-11-08 00:36 ------- Created an attachment (id=174) --> (http://bugzilla.mindrot.org/attachment.cgi?id=174&action=view) adds readonly flag to scp this change applies to scp.c ------- You are receiving this mail because: ------- You are the assignee for the bug, or are

Hello All. As promised, here is what I needed to do to get the regression tests to work on AIX & HPUX. It goes into a bit of detail in the hope that others might be able to get them running on their platforms. I've run these mods on AIX 4.3.3, HP-UX 11.00, Solaris 8, Redhat 7.3 and OpenBSD 3.0. The problems I encountered: * prereqs (pmake, md5sum) * bad directory owner/mode causing auth

Folks: Thanks to all who helped me get ssh up and running on my development box. Now I want to make a distribution package to take and install on the rest of my network. I am not sure what to transfer from box to box and what to run to get started. I did the install on the dev box and all tested fine. Is there a "standard distribution" list of only files required for running ssh on

I am just finished support for x509 certificate. More information on this page: http://satva.skalasoft.com/~rumen/openssh/

Hi All, Please visit http://satva.skalasoft.com/~rumen/openssh/ to get new version with support for x509 certificate. - added authorization by 'Distinguished Name'; - added x509 CA store (new options in sshd_config); - client certificate is verified against CA certificates in x509 store; - added shell scripts to create 'Test CA...

New version "x509e" is out on http://satva.skalasoft.com/~rumen/openssh/ . Now OpenSSH (client and server) can use x509 certificates for hostkeys too. Try it and give to forum (prefered) feedbacks, comments, suggestions, etc.

Hi all, I have pleasure to announce new version f of "X.509 certificates support in OpenSSH" Please to update your bookmarks/favorites with new location: http://roumenpetrov.info/openssh Old location is available too: http://satva.skalasoft.com/~rumen/openssh What's new: * support "Certificate Revocation Lists" (CRLs) * ssh-keyscan can show hostkey with certificates * information about X.509 certificates support added to all necessary manual pages * Distinguished name/Subject in RFC2253 format and item order...

Hi, Could anyone pls help by telling me how the DH pubkey from the server (f) is encoded when it is sent back to me? I understand that it comes across as an mpint, but after I decode the mpint into the bytes that make up the number, what does this number represent? Is it a X509 encoded key? Or is it something else? The reason for my question: I am trying to write a ssh client in Java,

As of Sunday evening, OpenSSH has an interactive sftp client. It should be in the more recent snapshots. It would be appreciated if you could test new client and find all the bugs :) Please also have a read of the manpage and ensure that it matches what is implemented. I am working on fixing the ones that I know about, so please try to stay up to date with the snapshots. Thanks, Damien

Q: What platform don't run this script: ---------------------------------------- #!/bin/sh export X0='x0' export X1a="$X0/1" export X1b='$X0/1' export X2a="$X1a/2" export X2b='$X1b/2' $SHELL <<EOF_2 $SHELL <<EOF_1 cat <<EOF #define a "$X2a/aa" #define b "$X2b/bb" EOF EOF_1 EOF_2

environment 1)compiler: cc -v Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/2.95.2/specs gcc version 2.95.2 19991024 (release) 2)openssh: CVS from 31 jan 2001 3)libc: GNU libc 2.2.1 output form make pty.o is: #make pty.o gcc -g -O2 -Wall -I/usr/local/ssl/include -I. -I. -DETCDIR=\"/etc\" -D_PATH_SSH_PROGRAM=\"/usr/bin/ssh\"

I find that adding -D_GNU_SOURCE is useful for linux. This define enable more features from header files. First) i found that define enable declaration/definition of following methods - grantpt(...) - unlockpt(...) - ptsname(...) for device "/dev/ptmx" ( support for ptys, preferred is method openpty (...) ) Second) _GNU_SOURCE enable use of utmpx and wtmpx ( support for login

Some system have getline method. Place rename 'getline' to 'Linebuf_getline' in ssh-keyscan.c !

remove last line in Makefile.in -rm -f $(DESTDIR)${ASKPASS_PROGRAM} ----------------------------------------- ${ASKPASS_PROGRAM} is external program 'make uninstall' don't needed to remove it

'Public Key Authentication' works for me. SERVERs: OpenSSH3.3p1 on linux - 2.4.x and 2.2.x kernels CLIENTs: Putty 0.52; OpenSSH 2.5.2p2,3.1p1,3.3p1 - with Public key ! SAMPLE: $ ssh -v SERVER echo 'NO problem to CONNECT' OpenSSH_2.5.2p2, SSH protocols 1.5/2.0, OpenSSL 0x0090600f debug1: ...... debug1: Remote protocol version 2.0, remote software version OpenSSH_3.3 debug1:

patches in attached file: - correct message in key_demote() - new error message when cannot create pid file -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: moremsg.patch Url: http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20021008/2ece6e84/attachment.ksh

When sshd is not running as root on linux with pam we recieve error like this fatal: monitor_read: unsupported request: 24

Makefile.in is not fixed ! in old ssh.h # define SSH_ASKPASS_DEFAULT "/usr/X11R6/bin/ssh-askpass" in new pathnames.h #define _PATH_SSH_ASKPASS_DEFAULT "/usr/X11R6/bin/ssh-askpass" but in Makefile.in PATHS=...-DSSH_ASKPASS_DEFAULT=\"$(ASKPASS_PROGRAM)\" ----------------------------------------------------------- about patch: - remove unused defines: