similar to: Samba on Tru64 UNIX Cluster

Hello Does anyone know why normal users can set a blank samba password with the smbpasswd kommand by inserting <CR> twice after inserting the old passwd: ben@amo:% /opt/samba/bin/smbpasswd Old SMB password:<oldpasswd> New SMB password:<CR> Retype new SMB password:<CR> Password changed for user ben After that the user can map the samba shares with a blank password even

http://bugzilla.mindrot.org/show_bug.cgi?id=933 Summary: compile problem on tru64 5.1A code outside of a #ifdef that should not be included on tru64 Product: Portable OpenSSH Version: 3.8p1 Platform: Alpha OS/Version: OSF/1 Status: NEW Severity: normal Priority: P2 Component: Build

Hi, I'm trying to get Samba on a Linux box to work. Authentication via user level worked fine, but what I really want is it to take user authentication from a win2k box, which is our "primary local server". The win2k box is not a pdc, (the real pdc is 2000km away, close to the polar circle), but according to the docs it doesn't have to be. So in smb.conf I put: security =

I have installed the icecast server on my Debian Linux 2.2. I modified the distributed icecast.conf (as far as thought was necessary), and I set up the shout.conf... Both server and shout are started from root and are set up to localhost. I could start the server, but when I started shout, it did find the server, but it was blocked with the message "BAD PASSWORD[encoder]" even if the

i've applied albert chin's patch on configure.in file: http://lists.samba.org/pipermail/rsync/2002-January/005726.html, but i still getting the error: cc: Error: lib/getaddrinfo.c, line 180: In this statement, "EAI_MAX" is not declared. (undeclared) thanks for any advice Martin Sigilfredo _________________________________________________________________ Join the world’s

http://bugzilla.mindrot.org/show_bug.cgi?id=1007 Summary: sftp client hangs on tru64 5.1A Product: Portable OpenSSH Version: 4.0p1 Platform: Alpha OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sftp AssignedTo: openssh-bugs at mindrot.org ReportedBy: paulstepowski at

All, I'm getting the following error message when trying to 'make' OpenSSH 3.7.1p2: cc: Severe: compress.c, line 19: Cannot find file "zlib.h" specified in #include directive. (noinclfilef) #include "zlib.h" -^ *** Exit 1 Stop. What can I do to get this to compile correctly? Thanks in advance, Trevor Strickland trevor.strickland at ed.gov

Dear openssh-unix-dev; I recently downloaded the tarball openssh-3.4p1 and built it for my Tru64 Unix ( OSF/1 ) 5.1a system. My configure statement is: ./configure --prefix=/usr/local/security/tools/openssh-3.4p1 \ --exec-prefix=/usr/local/security/tools/openssh-3.4p1 \ -with-ssl-dir=/usr/local/security/tools/openssl-0.9.6g \ -with-zlib-dir=/usr/local/compress/tools/zlib-1.1.3 \

Hi, I'm attempting to get openssh-3.4p1 up and running on our DEC/Compaq Alpa workstations. They are running Tru64 Unix 5.1A. I compile the package myself. Openssh-3.1 worked perfectly, with the default sshd_config file. Openssh-3.4p1 works, if I set UsePrivilegeSeparation to "no" in the sshd_config file. NOTE: I have a secondary issue with the ListenAddress default setting

Hi, I have still a 2.2.5 Samba PDC running and get from time to time printing problems. Sometimes it takes 2-3 minutes when trying to print even simple documents, but then most of the time printing starts immediately. I could not figure out why or when this is happening. It has nothing to do with a long printer queue or an (over)loaded server. Perhaps someone else had these problems too? I

OK, I got a chance to try out the Tru64 patch for privsep. I applied the patch to 3.4p1. Partial success, in that it now works for me for logins to "root". Logins to ordinary accounts fail after authentication, when trying to set tty characteristics. See the excerpt from the debug messages below. This is for Tru64 V4.0F (with enhanced_security turned on, obviously.) I guess it's time

Hello, I'm having problems to join a japanese W2K Client with SrvPck 2 installed to my samba 2.2.5 PDC controlled domain. Other Clients are no problem (Win98, W2k engl., WXP german). I check the regKey (for plaintextpassword; set to 1). Reinstalled SevPck 2, but didn't help. the problem must be on Client side because I having the same problem when jooining a other samba controlled

So, before I waste another couple of hours at this, is it possible to compile Samba 3.0.x on Tru64 at all? If so, can you tell me what the ./configure switches are? Thanks, Nate

http://bugzilla.mindrot.org/show_bug.cgi?id=653 Summary: sshd breaks logins after upgrade to 3.7.1p1 (Tru64 UNIX) Product: Portable OpenSSH Version: 3.7.1p1 Platform: Alpha OS/Version: other Status: NEW Severity: critical Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org

Hello, I want to use samba on Tru64 Unix. Can anybody let me know the location from where i can download this version. Raghu

Funciona perfecto! Gracias Carlos. Atte. Novvier Uscuchagua De: Carlos Ortega [mailto:cof en qualityexcellence.es] Enviado el: viernes, 16 de junio de 2017 13:46 Para: Novvier Marco Uscuchagua Cornelio <novvier en outlook.com.pe> CC: r-help-es en r-project.org Asunto: Re: Varios gráficos en una vista en OpenAir Hola, Prueba entonces esto, que sí que funciona... #-----------------------

Samba 2.0.7 running on Compaq Tru64 UNIX V5.0A with latest tru64 patches. "mget *" works OK, "mput *" or something like "mput *.bat" fails with the error message "find: bad option -maxdepth". Several questions - Anyone else come across this one? Would dropping back to 2.0.6 fix the problem? Could it be an issue with 2.0.7 on Tru64 V5? Regards, Brian

Tru64 patch will not make it into 3.5 (this is final) due to lack of willing people to test. I have given the Tru64/osf1 community almost a month to test it. And *ONE* person came forward to give me verification. And don't give me shit about "I don't have time." The person who tested it was LEAVING his employer with Tru64. He found time. IT IS YOUR GAWD DAMN PLATFORM. IF

We are using rsync to maintain a warm mirror of our boot disks. I just updated to rsync 2.6.0 and noticed that the rsync runs are now getting errors when copying sockets. The system is running Tru64 5.1A pk 4 on an AlphaServer 4100. Is this a bug? Is there some way to not copy sockets or should I find all of them and add them to the exclude file? rsync was built using a straight ./configure

Hi, I am trying to compile rsync 2.5.5 on a Tru64 box. I downloaded configure.in revision 1.148, which I believe is the correct fix for the getaddrinfo problem; however I still have errors compiling rsync. Also I had to change line 22 in options.c from #include "popt.h" to #include "popt/popt.h". Any suggestions or ideas? Tan Dang