similar to: OpenSSH password expiration in Solaris

I'm trying to install open-ssh 34p1 on an Aix server, running 4.3.3.. I compiled openssh 0.9.6d and zlib 1.1.4. on the server , and also created the a bff pancake using the contrib/aix/buildbff.sh script. I can't start sshd either installing it as a package or without. When I tried to start sshd I received the following error: 0509-036 Cannot load program /.sshd because of the following

http://bugzilla.mindrot.org/show_bug.cgi?id=14 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |793 nThis| | ------- You are receiving this mail because: ------- You are on the CC list for

Ben, I am trying to create a package for Openssh.3-1p1, but the /contrib/solaris/buildpkg.sh script failes with the following errors: ./mkinstalldirs /tools/OpenSSH/openssh-3.1p1/contrib/solaris/package/usr/local/b in mkdir /tools/OpenSSH/openssh-3.1p1/contrib/solaris/package/usr/local/bin ./mkinstalldirs /tools/OpenSSH/openssh-3.1p1/contrib/solaris/package/usr/local/s bin mkdir

Hello, I'm having problems with expire-tool in Dovecot 1.2.6 not finding the mailboxes. I had mail_location = mbox:/var/spool/dovecotmail/%d/%n/mails:INDEX=/var/spool/dovecotmail/%d/%n/indexes in dovecot.conf, but that doesn't work with expire-tool. So I commented that out from dovecot.conf, all the data is in a database anyway. A userdb lookup returns the following for userid at

Is there a way in UNIX to make a folder with read+write permissions for some group of users, but only allow them to read and write to the folder... not actually delete the folder itself? I have some samba shares, and directories inside them that I want to remain with their current structure and permission settings -- with many similiar group-specific files inside each folder, but I don't want

Hello Christian, I tried what you suggested by adding "REFERALS off" to /etc/ldap/ldap.conf and restarting slapd and dovecot, but the error persists. On Tue, Jun 4, 2013 at 7:56 AM, Christian Wiese < christian.wiese at securepoint.de> wrote: > Hi Ron, > > I didn't had the time to check all logs but the error log. > First thing you should check if there are LDAP

Hi all! I was scanning my servers with nmap, ( i have installed ssh), and the result gave me this: 22/tcp open ssh sshv1: Server Supports SSHv1 ssh-keyhost: 1024 ea:7e:77:b7:a1:78:18:70:6c:46:ee:a0:dd:08:0e:74 (RSA1) 1024 ba:d0:8a:44:16:fc:7c:7a:38:24:2e:72:06:fe:99:56 (DSA) 1024 ff:43:15:78:98:3c:75:f9:12:36:58:92:46:6c:1c:99 (RSA) could this be a threat for intruders? i know that sshv1

Hi, At this stage, we're most of the way towards fully deprecating SSH protocol 1 - this outlines our plans to complete this task. We've had this old protocol in various stages of deprecation for almost 10 years and it has been compile-time disabled for about a year. Downstream vendors, to their credit, have included this change in recent OS releases by shipping OpenSSH packages that

https://bugzilla.mindrot.org/show_bug.cgi?id=2519 Bug ID: 2519 Summary: Obsolete SSHv1 config options Product: Portable OpenSSH Version: 7.1p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org

I was wondering if anyone could help me with this one. I am having trouble getting LDAP and samba working properly on my Debian Woody box. I am using OpenLDAP 2.0.27-3 and the unsable packaged Samba version 2.999+3.0 and am using the samba.schema for my LDAP database. Whenever I try to join the network using either W2K or smbclient the LDAP debug log shows that the following filter is being

Hi, On Fri, Mar 27, 2015 at 12:53:05PM +0100, Hubert Kario wrote: > On Thursday 26 March 2015 11:19:28 Michael Felt wrote: > > Experience: I have some hardware, on an internal network - that only > > supports 40-bit ssl. I am forced to continue to use FF v17 because that was > > the last browser to provide SSL40-bit support. My security is weakened > > because I cannot

my smb.conf looks as follows. [global] security = ads realm = AD.MYDOMAIN.TLD workgroup = AD idmap config * : backend = tdb idmap config * : range = 2000-7999 idmap config MIND:backend = ad idmap config MIND:schema_mode = rfc2307 idmap config MIND:range = 8000-9999999 winbind nss info = rfc2307 winbind use default domain = yes winbind enum users = yes winbind

Hi, after an update from dovecot 2.1.16 to 2.2.0 I encountered a problem when using multiple master user passdb's like the following: ----%<--------------------------------------------------------- passdb { args = /etc/dovecot/passwd.foo-master driver = passwd-file master = yes } passdb { args = /etc/dovecot/passwd.bar-master driver = passwd-file master = yes }

I want something like so on login Last login: Wed Feb 1 10:47:53 Password Expires: Wed March 1 00:00:00 [myaduser at machine ~]$ I just want them to know when their password expires. On Wed, Feb 1, 2017 at 9:39 AM, mathias dufresne <infractory at gmail.com> wrote: > Plop, > > You'd like to modify .bashrc to auto-disconnect user with expired > password? I thought modern

Is it possible to program the multi-purpose keys on a GXP-2000 remotely via a TFTP configuration file? If so, what are the parameters to put in the configuration file? Thanks, Daniel

I''m going to explicitly time out sessions if they''re idle more than X minutes. Like online banking sites do. How do I set things up so that, when a session expires, a set of database records and a set of files that may have been created (which are identified via a seperate set of database records) are deleted just before the session data? TIA, Bill

hi have problems to get an samba server up that offers shares for all without a password heres my smb.conf file located under /usr/local/samba/lib/smb.conf [global] netbios name = DEATHB server string = Samba %v on (%L) workgroup = LANSTRIKE encrypt passwords = yes security = share [homes] browseable = no [mp3] comment = lmh path = /var/glftpd/site/mp3/lame.r3mix/ browseable = yes read only =

https://bugzilla.mindrot.org/show_bug.cgi?id=1835 Summary: sftp should fallback to sshv1 if server doesn't support sshv2 Product: Portable OpenSSH Version: 5.6p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sftp AssignedTo:

Hi, We are planning to move all of our win2k server (currenty around 50!) alongwith AD to Linux, we are planning to use LDAP based samba domain controllers for authentication and file/print serving. We are doing a pilot and things are fine till now, just one simple problem, what should we do with our password policy, we have three restrictions relating passwords minimum password length password

openssh password expiration problemPatrick, Indeed password aging does not work with OpenSSH 3.0.1p1 on Solaris 2.6. >From what I can tell something is different with Solaris 2.6 and Solaris 2.8. I know that password expiration doesn't cause a problem on Solaris8. I'm unclear as to whether the problem is with OpenSSH code or Solaris. All I know is that the latest PAM patches are not