similar to: openssh-unix-dev Digest, Vol 19, Issue 8

I have installed 2.5.1p1 on two systems, one running Digital Unix 4.0F and the other running Red Hat Linux 7.0. I am having trouble connecting using the 2.5.1p1 client and the version 2 protocol. Here is a connect attempt from the Linux box (this is after I blew away my ~/.ssh directory to make sure there was no "cruft" in it). Note that this also has the all zero key fingerprint that

I had a power hiccup yesterday and a server connected to a Best Ferrups 18KVA shutdown. The problem is that the UPS is reporting remaining runtime in minutes but nut treats it as seconds (so nut thought it only had 46 seconds left). Simple patch: diff -urN nut-2.2.1-dist/drivers/bestfcom.c nut-2.2.1/drivers/bestfcom.c --- nut-2.2.1-dist/drivers/bestfcom.c 2008-06-13 14:04:07.000000000 -0500

I know it is just after a release, but I'm trying to see how the regression tests look on Tru64. I hadn't had a chance to really look at them before because I didn't have sudo installed on Tru64 (now I do). Anyway, for the 3.9p1 release, all of them run except for a couple of problems: - agent-ptrace fails; it looks like setgid isn't enough to kill tracing under Tru64, and I

Well, after digging around and thinking some more, I'm giving up on the idea of preallocating a TTY to get post-auth privsep working on Tru64. I don't think it will work, because just allocating a TTY doesn't fix the problem - there's no valid way to tie that TTY back to the client process (because it hasn't requested a TTY yet and may not ever do so). The problem is that the

If a user doesn't have a ~/mail directory and logs in, the directory is created for them. However, it is created with insecure permissions, 0770 (full group access). The problem is this bit in src/lib-storage/index/mbox/mbox-storage.c: #define CREATE_MODE 0770 /* umask() should limit it more */ The code then uses CREATE_MODE as an argument to mkdir_parents(), but mkdir_parents()

I have an old (1997) Best Ferrups (model FE18KVA) that I am trying to monitor for the first time, but all the Best drivers fail to communicate with it. In ups_sync() in bestuferrups.c and bestfcom.c, the "time" command is sent and a one-line response is read. However, on my UPS, that command returns the current time and then prompts for a new time setting. I worked around that by just

The terminal programs (xterm, gnome-terminal, etc.) in Fedora have all supported 256 colors for quite a while, so there's a proposal for Fedora to switch them to using "xterm-256color" for $TERM. One drawback would be when you SSH to another host that doesn't have an up-to-date terminal database and doesn't recognize "xterm-256color" (but does know

Is it possible to have memdisk emulate multiple drives? Here's why I'm asking: I have a Dell server that I replaced the motherboard. I want to reset the service tag to the correct tag for the system, and the only way to do that is to run a Dell tool under DOS. I have downloaded the tool, but it is doubly-wrapped: a self-extracting ZIP file (which I unzipped under Linux) which contains a

I have been using PXELINUX with the "ipappend 2" option for a long time. To make things a little more user friendly, I decided to set up menus (text menus with menu.c32), but they wouldn't work (blank screen and corrupted menu flashes by when you hit a key). I went through all kinds of combinations of options, and finally found that commenting out the "ipappend 2" line

The ls_file function in sftp-server.c calls snprintf with "%8llu" as part of the format string and a "unsigned long long" type argument. The "%ll" format is not a valid format on Tru64 (at least 4.0F). Apparently it can confuse snprintf as well - sftp-server will segfault and core dump if the user types "ls". This isn't really a needed format string on

I think I've seen this come up before, but I couldn't find an answer in the archives. I'm trying to use the PAM "pam_mail.so" module on Linux to set the MAIL environment variable (so I don't have to try to do it in various shell init scripts), but the MAIL setting doesn't get passed through unless I disable PrivilegeSeparation. Is there a way to have PAM set

I'm trying to set up a full server backup using rsync 3.0.6. I'm using --fake-super, and SSH keys to access a remote server as a normal user. My problem is that there is a local directory that has permissions 0111 ("d--x--x--x"), and rsync throws an error trying to set the xattr: rsync: failed to read xattr user.rsync.%stat for "/roach/backup/root/tcb/lib":

I have "PermitRootLogin no" in my sshd_config, but under Tru64 and SIA, the root login attempts still get passed to the SIA system (so I get lots of warnings about failed root logins). On systems with a "max failed attempts" setting, the root account can be locked out this way. I started looking at the code, and I'm not sure I understand what I see. In auth-passwd.c,

Hi, Got this mail. It looks like he has a ups with revision before K, and need another startup. The 'PW_SET_REQ_ONLY_MODE' is not implemented, so to make it work we have to follow the protocol and send a 'PW_ID_BLOCK_REQ'. This in comsetup of bcmxcp_ser.c Also the standard id block ends with 'Statistics Map', so we have to Skip after reading the length of the 'Size

Well, I had just finally gotten around to downloading a snapshot to test the latest on Tru64 a couple of days ago but hadn't had a chance to build it yet, and 3.7p1 has now been released. Sigh. The problem is that Tru64 setreuid() and setregid() are broken, so privsep doesn't work. This could also be a security problem for SIA authentication in general (any version of OpenSSH on Tru64,

https://bugzilla.samba.org/show_bug.cgi?id=5027 Summary: Perms in do_mkstemp are not always valid Product: rsync Version: 2.6.9 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: cmadams@hiwaay.net

http://bugzilla.mindrot.org/show_bug.cgi?id=306 ------- Additional Comments From cmadams at hiwaay.net 2002-06-28 00:31 ------- I'm not seeing this on Tru64 4.0G or 5.1A with OpenSSH 3.4p1. What does "rsh [server]" say? Are you using IPv6? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

I have discovered that the JUNOS DHCP server in Juniper J-series routers doesn't support setting the next-server IP address field (I have filed a bug report with Juniper and they are working on it). Instead, it puts the "boot server" in the sname field, which PXELINUX currently ignores. Here's a simple patch (vs. 3.36) that will take an IP string in the field. My assembly is

Here is a long-overdue (sorry about that) patch for Tru64. It is pretty minor mostly (minor formatting and removal of a couple of unneeded calls), and it disables post-auth privsep (so that OpenSSH will work "out of the box" on Tru64, avoiding the many questions). I'm also looking at getting setproctitle working. For Tru64 4.x, it isn't a big deal (normal PS_USE_CLOBBER_ARGV

Okay, here is a fixed version of the patch I sent before for fixing the problems I know about with Digital Unix SIA: displaying too much info (MOTD, last login, etc.) when access is denied, and the loss of the error message sometimes when access is denied. It does break some code out of do_login into a couple of separate functions. I did this to avoid duplicating the code in a couple of places.