search for: agedwards

I've installed Sun's SUNWski package on Solaris 8 (32-bit) that provides a /dev/random interface. It appears to as cat'ing it gives me a bunch of well, random data. However, when I ran my configure, it gives me the WARNING.RND message to the effect that I'm using the built-in. I've seen allusions on this list to building openssl with to get random support, so I rebuilt it

In case this hasn't already been reported or discussed... It took some doing for me to get openssh working on HPUX 11i. The fixes are quite simple. First, one must have the IPV6 package installed: em 512# swlist -l product | grep IPV6 IPV6AA A.01.01.5D IPv6 11i product Second, I have to edit config.h to undefine HAVE_GETADDRINFO. Without IPV6, ssh can't connect

Hi, According to IETF draft draft-ietf-secsh-transport-14.txt, different ciphers(encryption), MAC and compression can be used for one direction say server-to-client and a completely different cipher, MAC and compression for the other direction client-to-server of the same connection. Is this supported today in OpenSSH, and if not, are there plans to support it in any future releases of the code?

If there a way to may samba "handle" files like ftp does during ascii transfers. Changing the ^m to unix end of line markers

maybe this is a silly question ;-) But why is it possible to login on a machine with a locked account (passwd -l ) via pubkey-authentication (authorized_keys) ? I use OpenSSH3.01p1on Solaris8 with PAM support so I thought this should not happen. If this is the normal behaviour and built in intentionally what would be the easiest way to lock an account without deleting the users authorized_keys ?

We're trying to build OpenSSH 3.0.2p1 for Solaris 8 (among others) and are running into a problem with UseLogin and utmpx. If we set "UseLogin no" then we can login okay. finger or who won't find us, even with a TTY allocated altough "who /etc/wtmpx" will find us. But the real problem is if we set "UseLogin true" which we must do for BSM support on some

I know that there's a lot of stuff that will be on the plate for the next release in further tweaking on how privsep plays out on various platforms, but I was wondering if there is a consensus on when the PAM fixes to allow expired password changes will occur? Do enough people rely on that to make it into the next release? It seems really critical from our perspective, but I'm trying to

Could the moderator please check my e-mail address. I stopped getting messages from this list. I did send an e-mail to <mailto:clrhodes@lists.digium.com> clrhodes@lists.digium.com and it got bounced back from the remote mail server. ------------------------------------------------------------------------------------- A.G. Edwards & Sons' outgoing and incoming e-mails are

Shouldn't that acutally pull the value of EscapeChar out of the users environment (and possibly default to the old message if they don't have one defined at all)? Thanks, --Jason Lacoss-Arnold, Systems Technical Specialist Technical Services - Unix Arch. 314-955-8501 -----Original Message----- From: bugzilla-daemon at mindrot.org [mailto:bugzilla-daemon at mindrot.org] Sent: Thursday,

I'm trying to update an ssh 1.2.27 to OpenSSH 3.0.2p1 and am running into a problem. I've successfully built zlib 1.1.4, OpenSSL 0.9.6c, and tcp_wrappers , but when I attempt to run configure, I get the error about the missing posix regex. So I attempted to download and use pcre (the Perl hack to expose perl regex to posix. But I can't build that since it calls strtoul() (string to

I am setting up a small Asterisk system for use at home. I have one Budgetone 101, one Cisco 7960 and two Xten lite softphones. So far everything is working expect for an issue with the Budgetone. When a call is placed between the Budgetone and any other phone, the call is setup and sounds good. If I hang-up on the Budgetone, everything is ok. If I hang up on the other phone, the Budgetone

While this may have some benefit, if you worried about busineses at all, you may get more benefit by working on the Solaris packaging scripts and HP depot scripts that I think I saw on a TODO list in the code. My rational is this: most businesses of any size at all don't compile ssh on every server that they deploy it to (and in fact rarely have compilers on a lot of them). Instead, we build

Our admins recently rebuilt a server and put the Dec. 2001 HP patch bundle on it. The ssh software was installed from a software depot, so it is the same as was previously on the server and as is on other, functional servers. Upon such time, when sshd comes up, it will accept connections, authenticate users as normal, but their shell appears to die during connection. The only output a user will