similar to: shadow file question

Hi , I am ruuning Senmail with MailScanner on CentOS 4.4. It has updated to kernel 2.6.9-42.0.8.EL from its past kernel 2.6.9-42.0.3.EL. Now the Server can not boot up and gives the below error. mkrootdev: label / not found Mounting root filesystem mount: error 2 mouting ext3 switchroot: mount failed: 22 Kernel panic - not syncing: Attempted to kill init! But I can boot up from its

http://bugzilla.mindrot.org/show_bug.cgi?id=811 Summary: locked /etc/shadow password prefix on linux Product: Portable OpenSSH Version: 3.8p1 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org ReportedBy:

I am installing Dovecot-2.1.13 on Slackware 13.37.0 for the first time to replace ipop3d and I have overcome all of the roadblocks as they have developed except this last one and I finally have to say ?uncle?. The error messages that are showing up in the dovecot.log are as follows. Jan 24 12:27:27 tux2 dovecot: auth: Error: passwd-file /etc/shadow: open(/etc/shadow) failed: Permission denied

So after troubleshooting this for about a week, I was finally able to create a raid 10 device by installing the system, copying the md modules onto a floppy, and loading the raid10 module during the install. Now the problem is that I can't get it to show up in anaconda. It detects the other arrays (raid0 and raid1) fine, but the raid10 array won't show up. Looking through the logs

From: Feizhou > I know what a Kerberos authentication system is. > You mean a core component in Samba 3.0's functionality as an ADS client. You're still artificially limiting your understanding. Kerberos (with the MS extensions in the case of 200x/XP) is how objects authenticate each other and grant tickets for access in a Kerberos realm. Samba can use Kerberos how it sees fit.

On 29 August 2007, "Ross S. W. Walker" <rwalker at medallion.com> wrote: > Message: 39 <snip> > I wouldn't worry too much about the OS HD configuration, you are > always going to want RAID1 for the OS, whether software or hardware. > > Reason I say not to worry too much about the OS HD config is because > you are almost certainly going to put the

I'm using an alternate password/shadow combo to authenticate IMAP users and I can't seen to get it working... I'm using: passdb shadow { args = /etc/dovecot/shadow } Can somebody please give me some hints on how to get this to work.... Thanks JB

Hi everyone, I'm still debuging my installation of samba. in /textdocs/DIAGNOSIS.txt under test 7, it suggested that - you have shadow passords (or some other password system) but didn't compile in support for them in smbd How do I check if my shadow passwords isn't compiled in support for them in smbd, if they are not, how do I go about compiling them? - you enabled password

On 9/3/07, Feizhou <feizhou at graffiti.net> wrote: > > > Now, I can find some files @ /etc/mail > > > > below are files. > > > > mimedefang-filter > > sa-mimedefang.cf <http://sa-mimedefang.cf> > > sa-mimedefang.cf.example > > > > I first want to block Bcc and limit Cc to about 5 users. I googled a > > lot. But, I am still

Hello, I have a very weird problem on a CentOS 5.2 system. A few months ago, encrypted passwords in the shadow file were MD5'ed - allowing for long passwords, rather than only 8 characters max. Today, passwords are 3DES'ed only. No way to find how the system reverted to DES-encrypting. But what's more bothersome is we cannot get the system to go the MD5 way again, despite all our best

Hi, currently /etc/shadow is edited manually when needed (i.e. when setting the password for an user), and it is not changed when removing users. Import the upstream shadow.aug (currently in their development serie, but not part of any released version yet), and use it only when the augeas version is less than a potential 1.2.1 (covering also the case when the new version is just 1.3.0). Pino

If you are using Bind as your caching name server, please take note. http://www.net-security.org/secworld.php?id=5366 I use DJB's dnscache so I could care less.

Hello, i installed zfs-auto-snapshot with Samba/Windows Shadow Copy. If the share contains "path = /srv/userdata/" it runs for me. But if I use "path = /srv/userdata/%U" I get no "Previous Versions" on my Win10 Client. I think the problem is the variable "shadow: snapdir = .zfs/snapshot". I tried with "shadow: snapdir = ../.zfs/snapshot" and

Hi, Robert, I found out another confusing code snippet: in void xi_invl_mfn(struct domain *d, unsigned long mfn) if (ext && pfn < ext->large_page_aligned_size) According to the code, it should be if (ext && (pfn>>SPT_ENTRIES_ORDER) < ext->large_page_aligned_size) If I made any mistake, please point it out.

Hi there I'm having some troubles with Shadow Copy2 & zfs Snapshots. I have hourly and daily snapshots. If I use the following settings it works (but omits daily snapshots): vfs objects = shadow_copy2 shadow:snapdir = .zfs/snapshot shadow:sort = desc shadow:localtime = yes shadow:format = easysnap-hourly_%Y-%m-%d-%H-%M-UTC However when I try to use the BRE with the prefix,

https://bugzilla.samba.org/show_bug.cgi?id=6116 Summary: Cannot access files in exposed shadow drive in version 3.0.5 Product: rsync Version: 3.0.5 Platform: x86 OS/Version: Windows NT Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

I tried creating a new partition on a disk. After the partition table was written, I got a message about the kernel still using the old partition table. How do I get whatever system to register the new partition short of rebooting the box?

Hello, This patch fix order of checking password in systems that contains /etc/shadow file (Linux for example). The order is exactly like in linux-shadow-password package. First is checked /etc/passwd but if password field contains "x" then password is read from /etc/shadow instead. Best regards, Krzysztof Ol?dzki -------------- next part -------------- A non-text attachment was

I've prepared a preliminary set of patches that makes ASan work with 32-byte shadow granularity, and I would like to get some feedback on those patches as well as my general plan. Some background: I am porting ASan to the Myriad platform. I'm looking to break up that port into components that may be useful/relevant to other platforms -- the first of those pieces is the ability to use a

I'm trying to get authentication to work without PAM and just use the standard shadow and passwd files. auth default { userdb passwd { } passdb shadow { } } This seems to be valid code to use /etc/passwd and /etc/shadow. My linux distro is using Salted MD5. Though Dovecot keeps telling me that authentication failed. It doesn't give me any error messages regarding the config. Any