similar to: [Bug 1110] memory leak in bufaux.c, function: buffer_put_bignum_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

http://bugzilla.mindrot.org/show_bug.cgi?id=1111 Summary: memory leak in openbsd-compat/getrrsetbyname.c, function: getrrsetbyname Product: Portable OpenSSH Version: 4.2p1 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo:

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.

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.

Hello, I had some difficulties in order to convert private keys between different implementations of SSH. So, I wrote the following patch to allow export of SSH2 RSA and DSA private keys into IETF SECSH format. Note that I also slightly revised the IETF SECSH key import code. Usage: use of the "-e" option on a private key file generates an unencrypted private key file in IETF SECSH

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

Hi, I recently ported OpenSSH to my hobbyist operating system. The portable release is very straightforward to work with, but it had a few minor issues where it assumes the existence of things that might not be on a POSIX 2008 system. This are the list of issues I encountered that I believe makes sense to upstream. * <sys/param.h> is included in many files and isn't a standard

Dear OpenSSH developers, I've worked this week on an alternative key exchange mechanism, in reaction to the whole NSA leaks and claims over cryptographic backdoors and/or cracking advances. The key exchange is in my opinion the most critical defense against passive eavesdropping attacks. I believe Curve25519 from DJB can give users a secure alternative to classical Diffie-Hellman (with fixed

Dear R users, I have the following script to create bins of specified time intervals bin_end=60/bin_size bin_size=bin_size*100 h=seq(070000,180000,by=10000) breaks=c() for (i in h) { for (j in 0:(bin_end-1)) { value=i+(bin_size)*j breaks=append(breaks,value) } } I would like to plot then using the time as x-axis. I tried the following prova=zoo(myseries,times(breaks)) but of

I am working on a port of Openssh 3.8p1 after already having done a port of Openssh 3.5p1. There are a couple of new lines in buffer_get_bignum2() that are causing me problems: if (len > 0 && (bin[0] & 0x80)) fatal("buffer_get_bignum2: negative numbers not supported"); The "& 0x80" check is not relevant in ebcdic. Does anyone

here's an up-to-date patch, should apply to both openbsd and non-openbsd versions of openssh. i did only test ipv4 addresses. Index: channels.c =================================================================== RCS file: /cvs/src/usr.bin/ssh/channels.c,v retrieving revision 1.191 diff -u -r1.191 channels.c --- channels.c 24 Jun 2003 08:23:46 -0000 1.191 +++ channels.c 25 Jun 2003 12:14:19

These warnings started appearing recently when building LLVM: llvm[2]: Compiling LLParser.cpp for Release build /Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp: In member function ‘bool llvm::LLParser::ParseBr(llvm::Instruction*&, llvm::LLParser::PerFunctionState&)’: /Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp:3195: warning: ‘Op1’ may be used uninitialized in

Hello, Everyone, how to use "loop" to make the process automatic and fast? When compute each sample, the script type in R almost the same, just the input and output file's name is changed(chr1 change to chr2, chr3,chr4...). The first sample's script like this: >chr1=MEDIPS.readAlignedSeqences(BSgenome="hg19", file="chr1",numrows= )

On Thu, Feb 12, 2009 at 4:47 AM, Ted Kremenek <kremenek at apple.com> wrote: > On Feb 11, 2009, at 8:14 PM, Ben Laurie wrote: > >> On Wed, Feb 11, 2009 at 8:24 PM, Ted Kremenek <kremenek at apple.com> wrote: >>> >>> Actually, neither of these methods are needed for ImmutableSet. >>> ImmutableSet already has an 'isEmpty()' method and I have

Hi all I'm trying to install asteris 1.4.22.1 on Solaris 10...the server is V120 SUN spark...During compilation (gmake) I got the following error /vis.c -o np/vis.o_a np/vis.c: In function `svis': np/vis.c:205: error: `u_int32_t' undeclared (first use in this function) np/vis.c:205: error: (Each undeclared identifier is reported only once np/vis.c:205: error: for each function it

Hi, So I screwed up when writing the support for the curve25519 KEX method that doesn't depend on OpenSSL's BIGNUM type - a bug in my code left leading zero bytes where they should have been skipped. The impact of this is that OpenSSH 6.5 and 6.6 will fail during key exchange with a peer that implements curve25519-sha256 at libssh.org properly about 0.2% of the time (one in every 512ish

On 06/11/14 08:39 PM, Chandler Carruth wrote: > > On Wed, Jun 11, 2014 at 1:44 AM, Ted Kremenek <kremenek at apple.com > <mailto:kremenek at apple.com>> wrote: > > On Jun 10, 2014, at 5:36 PM, C. Bergström > <cbergstrom at pathscale.com <mailto:cbergstrom at pathscale.com>> wrote: > > > On 06/11/14 06:58 AM, Ted Kremenek wrote: >

DOn 2007-12-24, at 01:29, Ted Kremenek wrote: > I am at revision 45341, and I am getting a build failure on Leopard > involving an unknown option to the ocaml compiler: > > llvm[3]: Compiling optimized llvm.ml for Debug build > /opt/fink/bin/ocamlopt: unknown option `-g'. > Usage: ocamlopt <options> <files> > ... > > > My ocaml binaries are compiled

Here are a couple of patches against the CVS (Jan 22 18:41 PST) Some C++ comments found their way into ssh.h The no64.patch puts ifdefs around buffer_get_int64() now in bufaux.[c,h] -- Tim Rice Multitalents (707) 887-1469 tim at multitalents.net -------------- next part -------------- --- ssh.h.old Mon Jan 22 18:40:58 2001 +++ ssh.h Mon Jan 22 19:02:02 2001 @@ -25,8 +25,10 @@ # include

Ted, Attached is the diff against TOT. It makes the VS build work for me. Solution/project files work with VS 2005. Project files in clang need not to be modified. As it happens, the solution file for clang is part of the llvm tree ( go figure... ) Thanks Dmitri --- Ted Kremenek <kremenek at apple.com> wrote: > Hi Dmitri, > > I know what you are saying, but in the end I