similar to: ebcdic problem in bufaux.c

Displaying 20 results from an estimated 800 matches similar to: "ebcdic problem in bufaux.c"

1998 Jul 24
1
Anybody want EBCDIC Support for Samba 1.9.18?
We've ported samba 1.9.18p1 to OS/390 Unix (nee MVS), and it seems to be very much in demand among the mainframe folks. We'd like to integrate our changes back into the mainline development stream. Our changes consist entirely of patches to ensure that the code works on an EBCDIC system, as well as a new facility that allows for ASCII/EBCDIC data conversion on the fly for files
2010 Apr 29
1
EBCDIC
Does R have package/function that can read a file that has been downloaded from a mainframe in EBCDIC format? Thanks, Mike [[alternative HTML version deleted]]
2003 Oct 08
4
OS/390 openssh
Hello Steve, Hello OpenSSH-portable developers, I am building OpenSSH for our (EBCDIC-based) BS2000 mainframe operating system, and I noticed you do the same for OS/390. Because my initial ssh port was based on IBM's OSS port (ssh-1.2.2 or some such), I thought it was fair enough to help with a little co-operation; we might come up with a unified EBCDIC patch which could be contributed to
2002 Apr 21
3
OpenSSH Security Advisory (adv.token)
A buffer overflow exists in OpenSSH's sshd if sshd has been compiled with Kerberos/AFS support and KerberosTgtPassing or AFSTokenPassing has been enabled in the sshd_config file. Ticket and token passing is not enabled by default. 1. Systems affected: All Versions of OpenSSH compiled with AFS/Kerberos support and ticket/token passing enabled contain a buffer overflow.
2002 Apr 21
3
OpenSSH Security Advisory (adv.token)
A buffer overflow exists in OpenSSH's sshd if sshd has been compiled with Kerberos/AFS support and KerberosTgtPassing or AFSTokenPassing has been enabled in the sshd_config file. Ticket and token passing is not enabled by default. 1. Systems affected: All Versions of OpenSSH compiled with AFS/Kerberos support and ticket/token passing enabled contain a buffer overflow.
2020 Jun 16
2
RFC: Adding support for the z/OS platform to LLVM and clang
> -----Original Message----- > From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Kai Peter Nacke > via llvm-dev > Sent: Tuesday, June 16, 2020 8:51 AM > To: Corentin <corentin.jabot at gmail.com> > Cc: llvm-dev at lists.llvm.org > Subject: Re: [llvm-dev] RFC: Adding support for the z/OS platform to LLVM and > clang > > > > 2) Add
2002 Nov 21
0
smbclient connection problem from MVS to Windows suspect EBCDIC to ASCII conversion problem
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
2020 Jun 10
9
RFC: Adding support for the z/OS platform to LLVM and clang
As part of IBM’s ongoing efforts to improve the z/OS ecosystem, our current plans involve adding support for the z/OS platform to LLVM and Clang. Our goal is to have a viable C and C++ LLVM compiler and runtime library that generates code for, and runs on z/OS. Long term, we expect to have a compiler and library that supports the platform more fully. We intend to support the native character
2003 Dec 19
2
SSH for OS/390 (ODBC SSH-Tunneling to OS/390)
Hi Martin, my name's Daragh, and I'm a renewal projects architect in the University of Chicago. I saw your name on a listserv - openssh-unix-dev. I was hoping you could lend some insight to a problem we're trying to solve. We are trying to find a way for an Oracle database to connect securely to a mainframe (OS/390 running Model204 DB) through ODBC (Open Database Connection
2020 Oct 02
2
[RFC] Adding a char set converter to Support library
Hi! On z/OS, there is the need to convert strings from EBCDIC to UTF-8 and vice versa. Using the POSIX iconv functions has some challenges, so I created a small wrapper around this functionality to get the same result on all platforms. This functionality is required for reading and writing GOFF object files and can also be used in the frontend. I put up the code on Phabricator
2005 Nov 04
1
[Bug 1110] memory leak in bufaux.c, function: buffer_put_bignum_ret
http://bugzilla.mindrot.org/show_bug.cgi?id=1110 Summary: memory leak in bufaux.c, function: buffer_put_bignum_ret Product: Portable OpenSSH Version: 4.2p1 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org
2005 Nov 04
1
[Bug 1109] Memory leak in file: bufaux.c, function: buffer_get_bignum2_ret
http://bugzilla.mindrot.org/show_bug.cgi?id=1109 Summary: Memory leak in file: bufaux.c, function: buffer_get_bignum2_ret Product: Portable OpenSSH Version: 4.2p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at
2020 Oct 02
2
[RFC] Adding a char set converter to Support library
My understanding is that dynamically linking should pose no problem, but I am no lawyer. On Linux, glibc is also under LGPL license, and LLVM usually links against it. (There is really no need for us to depend on libiconv. If it is deemed to risky, then I can dropped it.) From: Anton Korobeynikov <anton at korobeynikov.info> To: Kai Peter Nacke <kai.nacke at de.ibm.com> Cc:
2001 Nov 16
1
OpenSSH 2.9.9.p2 port to IBM OS/390 Unix System Services
I have done a port of OpenSSH to Unix Systems Services on IBM mainframes running OS/390. I have a version which seems to work with SSH 1 and 2, and most of the ancillary programs seem to work as well. I'd really like to see the changes (which mostly have to do with deciding which things need to be translated between ASCII and EBCDIC) incorporated into the source base. What is the best way
2004 Nov 27
0
buffer_get_bignum2: negative numbers not supported
Hi I have added smartcard support to PuTTY and this worked fine until yesterday when we replaced one of our Slackware-9 machines by a Slackware-10 one. Slackware-9 contained OpenSSH 3.5p1 while Slackware-10 has OpenSSH 3.8.1p1. Now the same keys that worked before do not work anymore and OpenSSH fails with buffer_get_bignum2: negative numbers not supported I first supected that my
2002 Jul 04
2
DH keys exchanged - encoding?
Hi, Could anyone pls help by telling me how the DH pubkey from the server (f) is encoded when it is sent back to me? I understand that it comes across as an mpint, but after I decode the mpint into the bytes that make up the number, what does this number represent? Is it a X509 encoded key? Or is it something else? The reason for my question: I am trying to write a ssh client in Java,
2011 Sep 09
1
1 TByte (99,5%) data missing on rsync backup???
Hi, I have a weird problem with RSync: On a NAS are about 1,2 TB data. When I plug in a harddisk and make a backup with RSync, "df -h" shows the backup disk filling up to nearly 1,2 TB. But after RSync has finished, there are only 3.7 GB on the backup disk. System: Linux nas 2.6.37-gentoo-r4 #1 SMP Tue May 3 19:54:31 CEST 2011 x86_64 Intel(R) Atom(TM) CPU 330 @ 1.60GHz GenuineIntel
2020 Jun 11
2
RFC: Adding support for the z/OS platform to LLVM and clang
Hubert Tong <hubert.reinterpretcast at gmail.com> wrote on 10.06.2020 23:51:54: > From: Hubert Tong <hubert.reinterpretcast at gmail.com> > To: Kai Peter Nacke <kai.nacke at de.ibm.com> > Cc: llvm-dev <llvm-dev at lists.llvm.org> > Date: 10.06.2020 23:52 > Subject: [EXTERNAL] Re: [llvm-dev] RFC: Adding support for the z/OS > platform to LLVM and clang
2008 Jan 25
1
OpenSSH for OS/390
I have been trying to compile OpenSSH_4.7p1 for OS/390 and got really stuck. IBM released a build of v3.8.1p1 several years ago, but I do not know whether anyone else has ever managed to compile it for OS/390 or OS/z. The first problem is that the build apparently performs ssh transport exchange using EBCDIC character encoding instead of ASCII (which breaks RFC 4253) and I am not sure how to do
2003 Jun 13
7
sshd refusing connections problem
We have been having a problem with sshd on our shell server. This has been happening since March 4, 2003 or before IIRC. Initially I thought the next OS upgrade, to 4.8 would fix this. I am accustomed to haveing little things go away in a month or two. I think we jumped to 4.7-STABLE on Feb 28, 2003. Some exploit fix wasn't being MFSd to RELENG_4_7 fast enough for my nerves (cvsd?). It