similar to: [Bug 2043] New: memleak in import_environments

https://bugzilla.mindrot.org/show_bug.cgi?id=2208 Bug ID: 2208 Summary: memleak in servconf.c Product: Portable OpenSSH Version: -current Hardware: Other OS: FreeBSD Status: NEW Severity: trivial Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org

https://bugzilla.mindrot.org/show_bug.cgi?id=2088 Bug ID: 2088 Summary: meoory leak in do_gen_krl() Classification: Unclassified Product: Portable OpenSSH Version: 6.2p1 Hardware: All OS: FreeBSD Status: NEW Severity: minor Priority: P5 Component: ssh-keygen Assignee:

There is a minor problem with the PAM support in OpenSSH 3.8p1. If you use POSIX threads (as specified by defining USE_POSIX_THREADS) in auth-pam.c, PAM authentication will fail in routine import_environments(). The purpose of this routine is to import variables returned by do_pam_account() in sshpam_thread(). However, those variable are only exported if USE_POSIX_THREADS is NOT set.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ================================================================ "Always keep an open mind and a compassionate heart." Phil Jackson ================================================================ Release Announcements ===================== This is a bug fix release of the Samba 3.2 series. Major enhancements included in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ================================================================ "Always keep an open mind and a compassionate heart." Phil Jackson ================================================================ Release Announcements ===================== This is a bug fix release of the Samba 3.2 series. Major enhancements included in

https://bugzilla.mindrot.org/show_bug.cgi?id=2134 Bug ID: 2134 Summary: invalid prototype for get_last_login_time() Product: Portable OpenSSH Version: 6.2p1 Hardware: Other OS: FreeBSD Status: NEW Severity: enhancement Priority: P5 Component: Build system Assignee:

https://bugzilla.mindrot.org/show_bug.cgi?id=2139 Bug ID: 2139 Summary: re-exec fallback problem Product: Portable OpenSSH Version: -current Hardware: Other OS: FreeBSD Status: NEW Severity: minor Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org

Hi All. Attached is another patch that attempts to do pam_chauthtok() via SSH2 keyboard-interactive authentication. It now passes the results from the authentication thread back to the monitor (based on a suggestion from djm). Because of this, it doesn't call do_pam_account twice and consequently now works on AIX 5.2, which the previous version didn't. I haven't tested it on any

On 18 April 2018 at 18:13, Manoj Gupta via cfe-dev <cfe-dev at lists.llvm.org> wrote: > Therefore, I would like to implement support for this flag (maybe with a > different name), I'd suggest -mdo-what-i-mean; the whole idea is horribly underspecified, and basically rips up the LangRef in favour of a nebulous set of good and bad optimizations (probably as dictated by the ones that

In Solaris 10 6/06, etc. I used to do things like pid$target::malloc:entry { ustack(); } and got stack traces from my application calling malloc as expected. In Solaris 10 8/07 I only see stack traces from functions inside libc calling a function called lmalloc() but not my malloc calls: ld.so.1`lmalloc ld.so.1`tsort+0xb4

New branch 'org' available with the following commits: commit 2ddba438108342502c59bc4f09d96118a59b5e33 Author: Benjamin Otte <otte at gnome.org> Date: Sat Jan 19 03:27:03 2008 +0100 we need to clear the stylesheet reference if the style sheet dies before us sems signals aren't the proper way to do this marshalling either commit

I've been looking for a while and can't figure out for sure if variables allowed by AcceptEnv are readable by a PAM module. I looked through the openssh source code and found a few calls to pam_putenv(), which looks like the relevant call, but I don't see anything that would copy over AcceptEnv variables. Am I correct that the variables are not available to PAM? I'm

We're using an internal PAM module (Linux) that sets a few environment variables using pam_putenv (on pam_sm_authenticate). In version 3.6.1p1i such variables are visible to the user (as expected), but since 3.7p1 they are not... Is this the expected behaviour? Thanks in advance, Jose ____________________________________________________________________________ Jose A. Rodriguez

I'm getting these over and over again in my dovecot [CVS] logs. I'm using PAM for authentication- something that worked a few weeks ago. Apr 6 15:22:11 [PAM-env] Unknown PAM_ITEM: <XAUTHORITY> Apr 6 15:22:11 [dovecot-auth] PAM pam_putenv: delete non-existent entry; XAUTHORITY dovecot: Apr 06 15:22:16 Warning: Killed with signal 2 dovecot: Apr 06 15:22:16 Error: child 25731 (imap)

libswfdec/swfdec_as_object.c | 3 +++ libswfdec/swfdec_loader.c | 8 +------- libswfdec/swfdec_style_sheet.c | 3 ++- libswfdec/swfdec_text_field_movie.c | 12 ++++++------ libswfdec/swfdec_text_field_movie_as.c | 4 ++++ test/swfdec_test_test.c | 1 + 6 files changed, 17 insertions(+), 14 deletions(-) New commits: commit

Hi, I'm one of the Swfdec[1] Flash player developers. As you may be aware, Flash uses VP6 as a possible video decoder. Someone recently grabbed all of the videos at http://pown.alluc.org and threw them at ffmpeg. Surprisingly, lots of them killed the vp6 decoder and in turn my browser. I'll attached a series of patches for issues that I could fix myself, and point out issues I could not

The current specification of the behavior of the !nontemporal attribute in LLVM, and the __builtin_nontemporal_* functions in Clang, is rather spartan and underspecified. In effect, it says the following things: * Atomic !nontemporal has no defined semantics * !nontemporal may use special instructions to save cache bandwidth, such as "MOVNT" on x86. What is crucially lacking

Hi! The Netfilter project proudly presents: nftables 0.9.7 This release contains fixes and new features available up to the Linux kernel 5.10-rc1 release. * Support for implicit chain, e.g. table inet x { chain y { type filter hook input priority 0; tcp dport 22 jump { ip saddr { 127.0.0.0/8, 172.23.0.0/16, 192.168.13.0/24 }

On Mon, Apr 27, 2020 at 8:09 AM David Hildenbrand <david at redhat.com> wrote: > > On 27.04.20 16:58, Alexander Duyck wrote: > > On Mon, Apr 27, 2020 at 1:08 AM David Hildenbrand <david at redhat.com> wrote: > >> > >> On 24.04.20 18:24, Alexander Duyck wrote: > >>> From: Alexander Duyck <alexander.h.duyck at linux.intel.com> >

Hi, This is regarding support for -fno-delete-null-pointer-checks in clang (PR 9251). Linux kernel uses this flag to keep null pointer checks from getting optimized away. Since clang does not currently support this flag, it often invites comments from kernel devs that clang is not yet *ready* to compile Linux kernel. I have also heard that developers working on firmware, bare-metal tools and