similar to: weak password checking for samba 3 ?

I got rsyncd v2.6.6 protocol version 29 running on Suse Enterprise Server 10. Here's what my /etc/rsyncd.conf looks like - max connections = 0 log format = %a %h %o %f %l %b log file = /var/log/rsync/rsync.log [nibbler] path = /backup/nibbler comment = nibbler read only = no use chroot = no timeout = 3600 transfer logging = yes [remote] path = /backup/remote/ comment = remote read only = no

Hello, I'm looking at compiling some pieces of the standard library with llvm but I'm running into problems with some functions being renamed by dragonegg. For example, when I compile the acos implementation with plain gcc I get: $ nm acos.o 0000000000000000 r .LC1 0000000000000048 r .LC10 0000000000000050 r .LC11 0000000000000058 r .LC12 0000000000000060 r .LC13 0000000000000068 r .LC14

Hi Gregory, > I'm looking at compiling some pieces of the standard library with llvm but I'm > running into problems with some functions being renamed by dragonegg. For > example, when I compile the acos implementation with plain gcc I get: > > $ nm acos.o > 0000000000000000 r .LC1 > 0000000000000048 r .LC10 > 0000000000000050 r .LC11 > 0000000000000058 r .LC12

Hey all. I've got four computers in a small network (Actually more, but keeping it simple to get to the point) 1> Linux Server (RH7.3) Running Samba (Default version with RH7.3) 2> Windows 2000 Workstation 3> Windows XP Pro. 4> Windows 98SE All of the windows boxes can connect, without problems, to the SAMBA server, and all the shares. No problems

Hi, I have reciently been attempting to connect an OS\390 system to a windows file server using the smbclient program that is part of the MVS port of samba. The problem I have encountered is this. When I try to connect from MVS to windows without a password I can connect with no problem at all. Files transfer fine and the encoding is fine. However the moment that i put a password on the

Hi Duncan, Ah, non-unicode email... In the llvm output there should be a "1" character, i.e. (char) 0x01, prepended to acos and __GI_acos. I'm unable to get it on smaller things, but it happens when I try to compile uClibc with llvm. I've attached the .o and the .bc for comparison. The text file is the result after preprocessing (to avoid having to download a bunch of stuff).

I've got no responce to my mail with subject 'samba 3.0.7 cannot join NT4 domain', so I dug deeper. I also read carefully these docs: swat/help/Samba-HOWTO-Collection/domain-member.html swat/help/Samba-HOWTO-Collection/winbind.html This is what I observe: 1.I srtart from clean state: PDC has no HUNTER machine account (chkd with L0phtcrack) HUNTER has empty var/{lock,private} samba

David Allan Finch wrote: > Has anyone considerd modify the Unix encypt to use > the same system as NT. IE the encypted pasword in the > /etc/passwd or NIS/NIS+ table is the same for both? Err. That would be a *really* bad idea. See the l0phtcrack source for details :-). Seriously, though. The password hashes used on NT are very poor. They don't use salt and people are now

network. I did read somewhere on the web (several years ago) of a guy who managed to boot windows from the net. With the start of Win 98/ME/ etc.etc it's not posible anymore. I currently use PXE to install machine from the net using bpbatch that works great only bpbatch is not really under developnt and the script language is a bit buggy. I see only one option to boot windows from the net and

Hi, at our local computer pool in the school we've a samba3 server and about 40 winnt-4.0 workstations. the main problem is, that the workstations have to wait for about 3 minutes after they started, before a user can login. in other words: the computer starts and if you try to login then immediatly you'll get "domain manos not available" or something like this. but if you wait