similar to: Samba 3.0.28 buffer overflow

Folks, Got an odd one here that's had me scratching my head for a few days! Samba 3.3.4-31 from SuSE's RedHat repository, RHEL5 on x86. Compiled OK once I'd worked out how to force a build on the libraries I needed, I also added the code back in to support the 'winbind: ignore domains' directive in smb.conf. Discovered the hard way that 'make install' doesn't

Folks, I'm trying to get said Samba version connecting to a new domain controller. Previously it was v3.0.33 talking to a Win2k3 DC. Smb.conf is correct with new domain and Kerberos realms, /etc/krb5.conf has the new info, I can kinit successfully with a domain user but net join ads fails with: "kinit succeeded but ads_sasl_spnego_krb5_bind failed: Decrypt integrity check failed"

Folks, Having some fun with winbind on Samba 3.5.5 on RHEL5 and/or Centos5. I?ve got it working so ssh logins work correctly and file permissions are seemingly correct with created files etc. Backend authentication is from a Win2K3R2 box running RFC2372 extensions (ie not SFU) and all UIDs etc are assigned for the users who need them. However, wbinfo returns some interesting things. We?re in a

Hello, I'd like to introduce myself, my company, and our upcoming use of LLVM. My name is John Reagan. I've been working on compilers and assemblers since 1983 (yes, 31 years). Most of that time was spent on compilers for VAX/VMS (later renamed to OpenVMS), then OpenVMS on Alpha, and OpenVMS on Itanium. I've also worked with the HP NonStop platform and was directly involved

As part of our port of OpenVMS to x86-64, we are using LLVM with our own frontends on OpenVMS Itanium. We are writing a converter between our old backend's IR and the LLVM IR. We can cross-compile (hosted on OpenVMS Itanium) and link/execute on x86-64 CentOS. At present, we pass over 88% of our C test suite. Porting starts with being able to compile the code. Since we are stuck with a

Refer to this: https://legacyos.org/vsi-introduces-new-samba-release/ I noticed that VSI, the new owners of VMS, have created a package for Samba4 under OpenVMS. I also notice the samba-vms list appears to be abandoned (for years). So, I apologize for posting here on the general list, but it seemed fruitless trying the dedicated list. I am under the impression that the GPL v3 compels all

Compaq C 6.5 OpenVMS Alpha 7.3 The config.h.in template file is missing the line: #undef HAVE_INET_NTOP This caused the resulting CONFIG.H on OpenVMS to not test for the existance of the inet_ntop() routine in it's system tables. This configure bug exposed that the prototype in inet_ntop() in RSYNC.H does not match the one in the Compaq C header files. This stopped the build. I am

I'm looking at need to duplicate some drives data from one OpenVMS site to another OpenVMS site. Clustering is not an option, so was wondering if Rsync could be used between two OpenVMS sites and if there would be any issues with the files. James Horn SHSU 2449 Computer Services Sam Houston State University Huntsville TX 77340 Phone: (936) 294-1042 -------------- next part -------------- An

Yes. We currently build LLVM 3.4.2 on our OpenVMS Itanium box with an older EDG/Intel C++03 compiler to create legacy cross-compilers to our OpenVMS x86 box (well, VirtualBox). We do have a few tweaks to the relocations to access static data always through the GOT (including CodeGen's static data). Our linker sees references to code (which might be in 64-bit space) and creates trampolines

Hi all, I have two queries regarding WINE. 1) Is there support for VMS(OpenVMS) and MAC OS in WINE. I mean that can I install/build WINE over OpenVMS OS and MAC OS. 2) I have heard that WINE doesnot have support for WIN64 bit API's. Is this true that I cannot port WIN64 applications via WINE on Linux 64 bit. If this is possible for anyone among you then plz list the name of all the OS where

Hi all, We're at the point in our port of OpenVMS to x86-64 that we're working on the unwind code.  The current ABI and the current codebase doesn't have enough support for true asynchronous unwinding from any point (most notably in the prologue/epilogue) in the code that OpenVMS needs.  We're working on a set of changes to the compact unwind information to handle the additional

We use .note descriptors with ELF on OpenVMS.  We have self-describing entries with tags and lengths.  The compiler encodes stuff for the linker such as compiler version, compilation date-time, module name, final severity of the compilation, etc.  The linker itself then adds/modifies the .note entries to insert linker version, link date/time, etc.  We also use .notes to record floating point

> -----Original Message----- > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of JF > Bastien via llvm-dev > Sent: Thursday, June 13, 2019 12:25 PM > To: John Reagan > Cc: llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] [RFC] Coding Standards: "prefer `int` for, regular > arithmetic, use `unsigned` only for bitmask and when you, intend to

Dear community, My company is interested in porting LLVM to OpenVMS. To do so, we need to look at extending the AMD64 calling convention to suit the existing calling conventions available on OpenVMS. We realize LLVM is a big and complex project and for some people who has not worked on it before, it's going to be a big and tough job that is going to take a lot of time. Still, the job has to

On Fri, 12 Jun 2020, Andrew Bartlett via samba wrote: > I can't find any evidence in the source code for new patches to have > Samba build on VMS Okay, well, at least I didn't just overlook something. > it certainly wasn't something we actively targeted when we moved from > autoconf to WAF with Samba 4.1. I'd be shocked if you did. Python 3.x isn't available on

On Wed, May 18, 2016 at 01:10:50PM +0000, Daniel Sanders via llvm-dev wrote: > It's my understanding that llvm-mc is intended to be a testing tool > for LLVM developers rather than an assembler for end users. Users > should be assembling with clang. Not all LLVM users are clang users. For example, we're using LLVM to build OpenVMS cross-compilers to x86 for our porting effort.

> Qualities > > 1. Be reasonably portable: at least in principle, it should be > possible to port to Windows, OS X, and various Unixes without major > changes. In general, I would like to see OpenVMS in that list. > Principles > > 1. Clean design rather than micro-optimization. A clean design allows optimization to be done by the compiler, and tight optimization

As one of the OS' without current CMake support, I'm closely watching this discussion. We currently have LLVM 3.4.2 hosted on OpenVMS Itanium (as a host only, x86 target) using configure/make with little hassle. We plan to port CMake to OpenVMS, but that has been trickier than you'd think (others have tried, I haven't found anybody who has done it). Looks like I'll want to

As part of our OpenVMS-specific changes, we're adding an arg-count to all of our calls. We've done this as part of callLowering to put the # of slots used into %ah and leaving %al to hold the standard info about vector registers.  That part is working. However, we're struggling somewhat on the code in the prologue to capture the %ah value to then be obtained by our

I have found that this server, <snip> debug1: Remote protocol version 1.99, remote software version 3.1.0 F-SECURE SSH - Process Software SSH for OpenVMS debug1: no match: 3.1.0 F-SECURE SSH - Process Software SSH for OpenVMS </snip> does not follow the IETF secsh draft [1] related to the SSH_MSG_USERAUTH_PASSWD_CHANGEREQ message. <snip> ... Normally, the server responds