similar to: SSH_MSG_USERAUTH_PASSWD_CHANGEREQ and 3.1.0 F-SECURE SSH - Proces s Software SSH for OpenVMS

Darren, > -----Original Message----- > From: Darren Tucker [mailto:dtucker at zip.com.au] > Sent: Thursday, June 17, 2004 11:08 PM > To: Scott Rankin > Subject: Re: SSH_MSG_USERAUTH_PASSWD_CHANGEREQ and 3.1.0 > F-SECURE SSH - Pr oces s Software SSH for OpenVMS > > > Scott Rankin wrote: > >>That will depend on which versions exhibit the problems. Is it >

Below is a patch against the current OpenBSD OpenSSH CVS to workaround a behavior I have observed when converting from SSH 1.2.27 to OpenSSH while using the same old RSA1 host key for protocol 1. In several cases I saw that old SSH sshd reported a host key size of 1024 bits when OpenSSH saw it as 1023 bits. Without the patch, when OpenSSH's ssh client connects to an old SSH sshd it warns

I sent in a patch a week or so ago for a problem a customer of mine was seeing when trying to connect to their OpenVMS system with an 3.8.1p2 OpenSSH client (running on a linux box or in cygwin) and trying to login to an account who had an expired password. The problem continues although now it has nothing to do with what my patch handled as they have since upgraded their SSH software on the VMS

Hi. I don't do much with routers any more but recently I was configuring a Cisco via SSH when my session disconnected while pasting large amounts of text. I'm told this is common. I've had this patch for a while but I've not been able to test it. If anyone is regularly experiencing this kind of issue could you please tell me if the attached patch helps? (The buffer size limit

http://bugzilla.mindrot.org/show_bug.cgi?id=147 Summary: ssh dies if it gets SSH_MSG_USERAUTH_PASSWD_CHANGEREQ Product: Portable OpenSSH Version: 3.0p1 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: P4 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org

> Turns out the problem is the new protocol extension for sending host keys to > the client after user authentication (section 2.5 of the PROTOCOLS > document). Commenting out the notify_hostkeys() call in sshd.c fixes the > issues with Cisco scp. Maybe a new bug compatibility flag in on order to > add to the "Cisco-1.*" client string that was added in 6.9? There's

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

I've watched this list for a while and posted twice for information on a OpenVMS version of Rsync and had no replies. Is there no version?

On Thu, 2020-06-11 at 17:02 -0600, Swift Griggs via samba wrote: > 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,

This is my first time posting on this list, so please excuse me if this is the wrong list to post on (if it is please just let me know). I've recently upgraded my old Redhat 8.0 box to Redhat Fedora Core 8 which comes with Samba 3.x while my old Redhat 8.0 box had Samba 2.x. On my old box I had SMB map a drive from an older OpenVMS server using Pathworks. I performed this by simply doing:

Hello, I am using SAMBA 2.0.3 on Open VMS and i have the problem that from files which are smaller than 8193 bytes the content is not saved. The file is created in the directory but it has no content. On VMS i see the file which has allocated 0 blocks. OpenVMS $ dir/full ajosg.txt AJOSG.TXT;1 File ID: (275,3,0) Size: 16/0 Owner: [20,3003]

I am trying to find source/object files for Samba for OpenVMS using Multinet 5.0. Install guide would also be helpful. Currently run Samba on Unix. Thanks

Does anyone have a version of RSync built for OpenVMS I64? James T Horn Systems Administrator IV Sam Houston State University AB1, Room 320 Office: 936-294-1042 horn at shsu.edu<mailto:horn at shsu.edu> IT at Sam Communicate+Collaborate -------------- next part -------------- An HTML attachment was scrubbed... URL:

Is there a version ready to run for OpenVMS AXP?

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

Hello, I searched through the mailing list archives here, at securityfocus.com, at HP and google and have come up dry. Sorry in advance if my search was not complete enough or I missed something but I sure as heck didn't see anything. ENV: Slackware 10 w/ ssh (SSH-2.0-OpenSSH_3.8.1p1) connecting to an alpha with OpenVMS 7.3-2 w/ sshd (Remote protocol version 2.0, remote software version

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

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

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

> 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