similar to: Dashboard table resource_statuses growing uncontrollably

Folks, On AIX 4.3.3-08ML with the IBM C Compiler, and ssh configured to use the prngd-socket "/dev/egd-pool", the make bombs out at: /usr/bin/cc -g -I. -I. -I/usr/local/include -DSSHDIR=\"/usr/local/etc\" -D_PATH_SSH_PROGRAM=\"/usr/local/bin/ssh\" -D_PATH_SSH_ASKPASS_DEFAULT=\"/usr/local/libexec/ssh-askpass\"

Hello, OpenSSH 2.5.1p1 running under AIX 4.3.3ML06. When I send a HUP signal to the parent sshd, that parent process dies, it's children get "adopted" by init, and the following message is put in the error log ... Mar 13 12:01:48 whippet sshd[31644]: Received SIGHUP; restarting. Mar 13 12:01:48 whippet sshd[31644]: RESTART FAILED: av[0]='sshd', error: No such file or

Folks, I've been tasked to find a solution that will create file-transfer-only accounts that are jailed or chrooted to a specific directory. (Not an uncommon task, I think.) Using the OpenSSH server and the OpenSSH scp client program, I can achieve the goal of having a file transfer only account jailed to a specified directory, by using the "scpjail" script (attached) as a

Some of the Red Hat Enterprise Linux servers in our environment sometimes get assigned virtual IP addresses (eth0:1, eth0:2, etc). Puppet Dashboard''s parameters seem like an ideal way to define and provision virtual IPs on these servers. One could create a "vip1" parameter on a node, and define a value of the IP address to use for that vip. A manifest could then be written to

I''m using puppet-dashboard 1.1.0-1 on Ubuntu. I remove old reports using this command: nice -n +1 rake RAILS_ENV=production reports:prune upto=1 unit=mon This seems to work fine, and the amount of reports returnd by this mysql query seems to drop by the proper amount: select count(*) from reports; Right now it returns a value of 12591. So far so good. The problem is the

Hi, I was looking through the source, and I noticed that the following code appears twice in the file serverloop.c. Is it supposed to, and if not, would there be any ill effect? +289 +290 /* Read and buffer any available stdout data from the program. */ +291 if (!fdout_eof && FD_ISSET(fdout, readset)) { +292 len = read(fdout, buf,

An error I managed to hit today, trying to migrate puppet dashboard from 1.2.2 to 1.2.4 (after upgrading the master to puppet 2.7.9 seemed to prevent the dashboard from importing new reports). I''m trying to re-run it now, but as you might guess, the DB is pretty huge and the process takes a while to execute. Executed from the puppet-dashboard directory: sudo rake db:migrate

... who are nervous because: (a) it seems that there will be a widely-known vulnerability and/exploit for OpenSSH available in the coming days, and (b) the advertised fix for the problem, privilege separation, doesn't seem to be working on AIX as of the latest release version of OpenSSH (based on the comments I've read; I haven't tried it yet) ... ... what should we do? I've

Recently we made somemajor changes to do_child() in OpenSSH -current. Those changes included splitting it up into smaller chunks to help with readability and also to extract out IRIX and AIX specific code to reduce the number of lines in our diffs against the OpenSSH tree. I need people to do some testing on different platforms to ensure that all the right #ifdef/#endif bits got put back in

Can we do this? Or should we drop the whole char *tty; ? There will be no way of setting the TTY= correctly while using privsep (Mainly for multiple streams over single session). The only thing we really could do is do: In do_setusercontext() if (use_privsep) aix_usrinfo(pw, NULL); and back in the old spot put: if (!use_privsep) aix_usrinfo(pw, s->ttyfd == -1 ? NULL : s->tty);

I was discussing with Don about a private topic..and while skimming the code I noticed that during a 'ssh mouring at site ls' the /etc/environment is *ONLY* read if the remote machine is an AIX box. This is undocumented and I'm wondering if someone using AIX could explain WHY it exists in the session.c:do_child()? No other OS has this. I don't see why AIX should require it.

Hi everybody. I posted this also to comp.sec...ssh, so excuse me for multiple emails. I downloaded openssh-3.5p1 and compiled under AIX. Now, if I run that program, Sandor W. Sklar in bugzilla #124 suggested (see below), it works in linux, not in AIX 5.1. in AIX it produces the same "hang" as the original problems Ihave with "tclsh"-command. sshd hangs with this output:

I hope someone can help. I've installed 2.9p2 on a number of AIX boxes and it works great. The problem is that a HUGE >700 number of defunct processes get generated by sshd. Did I do something wrong ? Any suggestions ? Please email chuck at fiu.edu as I don't subscribe to the list. TIA, Chuck -------------- next part -------------- A non-text attachment was scrubbed... Name:

We are heading into a lock here. So we need to get people to test their respective platforms if they wish them to be supported out of the tar file. So if you have any patches you need to ensure your platform works speak up. We are looking at a lock on the 17th. I believe I have an AIX/Cray patch and a Tru64 patch sitting in my mailbox that I'll be looking at soon and more than likely

Hi, We have upgraded the openssh 4.6P1 on Solaris 8 servers. After upgrade we get the below error message whenever we execute the remote commands using ssh. Please let me know what the fix is for this. Apr 8 03:03:43 dvsrv10 sshd[25379]: [ID 800047 auth.info] Accepted publickey for osteam from 10.0.93.31 port 35856 ssh2 Apr 8 03:03:50 dvsrv10 sshd[25381]: [ID 800047 auth.error] error:

How would I convert this program to output exactly the same thing but only for all the (noop) operations. We keep puppet in noop mode to audit its actions before they are applied. Thus it is necessary to ensure we understand exactly what all the nodes noop operations would be if we listed the noop restriction for a normal apply. This program will report in a reasonable format for those non-noop

Hello, The item that causes me the most difficulty in deploying OpenSSH (and the commercial ssh, as well) is confusion over the large number of options for the configuration file; while the man page gives an explanation of each one, they are listed alphabetically there, with no "logical" grouping. For my own use, I've created a heavily annotated sample sshd_config file,

Hello, I believe that there is a bug in OpenSSH that affects its usage on AIX 4.3.3 - Maintenance Level 3 and higher. This bug was introduced by a change by IBM in the "/usr/lib/drivers/ptydd" driver, and it affected IBM's own telnetd daemon (reference

On pop3 logout, we're seeing log lines where the deleted count is blank (using default pop3_logout_format), so "del=%d/%m" is displaying in the logs as: "del=/1186" for example. In src/pop3/pop3-client.c:552: tab[4].value = client->delete_success ? dec2str(client->deleted_count) : 0; Shouldn't this be: tab[4].value =

puppet agent --verbose shows a verbose output of the changes done by puppet, such as: notice: /Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner: owner changed ''root'' to ''logstash'' notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed ''stopped'' to ''running''