similar to: Solaris packaging

Hi. Solaris packages created by buildpkg.sh don't create privsep user or group and sshd won't start until they are created (or privsep is disabled): ## Executing postinstall script. starting /usr/local/sbin/sshd... Privilege separation user sshd does not exist /etc/init.d/opensshd: Error 255 starting /usr/local/sbin/sshd... bailing. The attached patch (against -cvs) ports the relevant

A non-text attachment was scrubbed... Name: not available Type: text Size: 7366 bytes Desc: not available Url : http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20031015/02b75f40/attachment.ksh

Here is a small patch for OpenSSH 3.2.3p1.. When the package postinstall script runs, it presumes that the package will be installed relative to the current / directory.. If this package is installed as part of a Solaris Jumpstart installation, this will not be the case. Consequentially, the /etc/ssh/sshd_config.default will never get copied to /etc/ssh/sshd_config on the new operating system.

Hello, I don't know how off the wall this question will be, but first let me say that I've found your buildpkg.sh script very useful in creating an OpenSSH package for use on my Solaris systems. Currently I'm trying to set up a fully automated JumpStart system at my workplace, and I'm realizing that the 'postinstall' script (and possibly some of the other install scripts)

Hi, I created a package for OpenSSH 3.7.1p2 in UNIX (OS: Sun Solaris), the newly created package includes binaries,man pages, libraries and Configuration files. I am planning to install this package in all of my Sun server's (Approximately 200 Server's). We have SSH/OpenSSH older version are already installed and running in all of the sun boxes. I want to install the

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

Outside the pre-auth patch by Markus to fix Cygwin and a few other platforms. SEND ME (privately) ANY required patch against the lastest snapshot. I'm doing the final commits this evening. Patches that have been temporary rejected for this release. - Owl's full patch for SysV Shm if mmap fails - mmap() on /dev/zero - mmap() on sparse file .. Not looked at the BSD/OS 5.0 patch

Hi, We want to use Hostbased Authentication in OpenSSH 3.4p1 completely based on rhosts or shosts. Don't want to have any keys exchange between server and client. Created /etc/ssh/sshd_config on OpenSSH server with: RhostsAuthentication yes IgnoreRhosts no HostbasedAuthentication yes Created /etc/ssh/ssh_config on client with: Host * HostbasedAuthentication yes Created /etc/rhosts.equiv,

I have just upgraded my jumpstart server to S10 u2 b9a. It is an Ultra 10 with two 120GB EIDE drives. The second drive (disk1) is new, and has u2b9a installed on a slice, with most of the space in slice 7 for the ZFS pool I created pool1 on disk1, and created the filesystem pool1/ro (for legacy reasons). I them moved my data from the original disk0 UFS file system to pool1/ro. Initially I

> I''ve built a puppet solaris - package which is distributed via jumpstart > at installation time of a solaris 10 machine. > It''s postinstallation registers the puppetd into smf and starts puppetd > afterwards. Puppetd connects to puppetmasterd, gets ist certificate signed > (autosig on) and the configuration stuff. > Now the interesting part: a new solaris zone

Not that I''m much of a Solaris guy, and definitely not a Solaris 10 guy, but since nobody else had posted anything yet: http://reductivelabs.com/trac/puppet/wiki/PuppetSolaris#Solaris10 The good news is that it appears to be a completely hands-off puppetd installation. Just sign the client key afterwards on the puppetmaster and you''re set. The bad news is that it''s

http://bugzilla.mindrot.org/show_bug.cgi?id=1038 Summary: buildpkg.sh postinstall script does not install RC links using installroot and non-symlinks. Product: Portable OpenSSH Version: 4.0p1 Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component:

Hi All, I've been having issues getting X forwarding to work on OpenServer for OpenSSH versions 3.4p1 and 3.5p1. I have compiled OpenSSH on Redhat Linux 8.0, Solaris 8, and OpenServer 5.0.6, but the OpenServer box is the only one that exhibits the problem. I've detailed everything below. I am using PuTTY for my ssh client under Windows. If I connect to the Linux or Solaris boxes, X

Hi All, Now that we have multiboot capable pxelinux, thanks to mboot.c32, I decided to try and remove pxegrub from my x86 jumpstart infrastructure since, in theory, pxelinux can now do it all. The problem I'm having is I'm not very sure I'm following Tim's documentation correctly... I'm not 100% what comes after the --- and whether the Sun kernel needs it's arguments

Folks; During a jumpstart (2nd boot) of a Sun Fire 240 with Solaris 10 Update 3 (11/06), I noticed the following message; Jun 27 11:43:33 first fbt: NOTICE: cannot instrument return of fd_intr at 7b7d6278: non-canonical return instruction Kernel level was Generic_118833-33. Jumpstart was conducted using the standard JET modules. What gives? The jumpstart worked though. Solaris 10 installed

SecureComputing's PAM library doesn't pass back the correct context to the pam_conversation function, i.e. it passes back NULL. So this patch works around this fact. likely you'll only want this hack if you expect to use pam_safeword.so in your authentication check, and only if you run sshd in privilege separation (separate process) mode so that the PAM conversation is single

I am attempting to successfully run the buildpkg.sh script which is located in the contrib/solaris directory. I am receiving the following error: Building pkginfo file... Building prototype file... Building package.. ## Building pkgmap from package prototype file. ## Processing pkginfo file. pkgmk: ERROR: parameter <VERSION> cannot be null ## Packaging was not successful. pkgtrans: ERROR:

Hey everyone, I wanted to add support for denying PTY allocation through OpenSSH. I'm not certain if this is quite thorough enough for all cases, but for me it might work for the moment. I know that you can currently do this through authorized_keys, but as far as I know that only works for an actual key. In my use case, I wanted a user with no password which is forced to run a specific

Anyone have idea how to create ZFS pool and volumes during jumstart instalation ? (I''m using JumpStart Enterprise Toolkit) kloczek

Hi all Am i doing this right? Is this the right list to post to? If not, a quick lesson in ettiquette for me would not hurt. As I am both just starting to use newsgroups and SSH, I am not entirely familiar with the processes. I have a question about ssh-rand-helper. First an outline: I am currently using the SSH packages for Solaris 2.8 available at sunfreeware.com. The environment is