similar to: Enable gcc's -fstack-protector-all by default?

Hello, While testing recent snapshots (20131023 and 20131024) I encountered a problem with ProxyCommand. The regression tests all passed, but the use of ProxyCommand's in my ~/.ssh/config resulted in name resolution errors; even if CanonicalizeHostname was explicitly set to "no." The patch included inline below fixed the issue: Index: ssh.c

http://bugzilla.mindrot.org/show_bug.cgi?id=1347 Summary: LLONG_MAX v LONGLONG_MAX Product: Portable OpenSSH Version: 4.6p1 Platform: PPC OS/Version: AIX Status: NEW Severity: normal Priority: P2 Component: Miscellaneous AssignedTo: bitbucket at mindrot.org ReportedBy: David.Leonard at

Hi, OpenSSH 7.4 p1 still can't be build without patch on Solaris 10 (attached). Pls, may be possible to add conditional compilation/configuration to avoid manual actions before build? May be, in portable version? Otherwise seems OpenSSH stops be portable on all platforms. Thank you, WBR, Yuri. -- What is the fundamental difference between the programmer and by a fag? Fag never become

Seems like opun configury still enables visibility attributes when targeting windows. The following patch disables that. (Relies on the top-level AC_MINGW32 check, can possibly be done better.) diff --git a/configure.ac b/configure.ac index eabad3a..3bede12 100644 --- a/configure.ac +++ b/configure.ac @@ -759,14 +759,15 @@ saved_CFLAGS="$CFLAGS" CFLAGS="$CFLAGS

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The same result without CFLAGS: configure:17300: checking for mblen configure:17356: gcc -o conftest -g -O2 -Wall -Wpointer-arith -Wuninitialized -Wsign-compare -Wformat-security -Wsizeof-pointer-memaccess -Wno-pointer-sign -Wno-unused-result -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -ftrapv -fno-builtin-memset -fstack-protector-strong -fPIE

Below I've includes a patch which helps build OpenSSH outside from a read-only source tree, find OpenSSL on Mac OS X, and fix a typo. This applies to OpenSSH 2.1.1p4. You should already have gotten a note from Melissa O'Neil about a conflict with the crc32() symbol in zlib, which was causing a crash on Darwin. I've noticed another bug. If ssh is setuid, I get a permission

yo, ive been using the fstack protector for a while now and it worked fine until i was gonna compile 4.8p3 then i got these errors, sio.o(.text+0x18b7): undefined reference to `__guard' sio.o(.text+0x1da9): undefined reference to `__guard' sio.o(.text+0x1db9): undefined reference to `__stack_smash_handler' vga_isa.o: In function `isavga_probe': vga_isa.o(.text+0x10): undefined

On 2 Oct 2012, at 03:26, Magee, Josh wrote: > 1) An address of a local variable is taken in such a way as to expose the > address of a stack location. > - Example: the address of a local on the RHS of an assignment, the > address of a local passed into function. This sounds like something that would be triggered for any function containing a block, even if the

David Chisnall wrote: >On 2 Oct 2012, at 03:26, Magee, Josh wrote: > >> 1) An address of a local variable is taken in such a way as to expose the >> address of a stack location. >> - Example: the address of a local on the RHS of an assignment, the >> address of a local passed into function. > > It also sounds like it would be triggered for a

I tried building dovecot using : CPPFLAGS="-fstack-protector" LDFLAGS="-lssp" ./configure That would result in a proper build, yet the binary would complain once being run: dlopen(/usr/local/lib/dovecot/imap/lib10_quota_plugin.so) failed: /usr/local/lib/dovecot/imap/lib10_quota_plugin.so: undefined symbol: __stack_chk_fail_local Error: imap dump-capability process returned

On Mon, Feb 22, 2016 at 3:32 PM Joerg Sonnenberger via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Mon, Jan 25, 2016 at 07:57:43PM +0000, Tim Shen via llvm-dev wrote: > > A cleaner solution could be adding an IR intrinsic llvm.get_tcb_address() > > and hard code the offset of stack_guard member, since they aren't > supposed > > to change. > > It

On 8 June 2018 at 10:52, PGNet Dev <pgnet.dev at gmail.com> wrote: [...] > So, there's a problem for OpenSSH build with spec'ing LD=/usr/bin/ld ? in this particular case, apparently yes. not generally, though. [...] > What's *intended* re: openssh? Support for LD=ld or only =gcc, or undef'd ? Well the intent is you should be able to set CC and LD to whatever you

On Mon, Feb 22, 2016 at 5:00 PM Eric Christopher <echristo at gmail.com> wrote: > Yeah, for most of the architectures listed there it's not particularly > useful as they support direct access to TLS variables (as Joerg says > later). That grep isn't representative of how the data is actually > accessed. If the current address space way of specifying isn't doable on

----- Original Message ----- > From: "Eric Christopher" <echristo at gmail.com> > To: "Tim Shen" <timshen at google.com>, llvm-dev at lists.llvm.org, "Hal > Finkel" <hfinkel at anl.gov>, "Kit Barton" <kbarton at ca.ibm.com> > Sent: Wednesday, February 10, 2016 6:59:50 PM > Subject: Re: [llvm-dev] [PPC] Linker fails on

When -fstack-protector is turned on, linker fails to find the symbol "__stack_chk_guard" because at least for powerpc64le, glibc doesn't provide this symbol. Instead, they put the stack guard into TCB. x86 fixed this issue by injecting a special address space (which is later translated to TCB register access) and hard code the offset of stack_guard, but I don't see a easy way to

Hi, List, In checking the page fault problem when using pv-grub to start domU in opensuse12.3[1], found that the problem is caused by ''-fstack-protector'' flag which is introduced in rpm build: export EXTRA_CFLAGS_XEN_TOOLS="$RPM_OPT_FLAGS" export EXTRA_CFLAGS_QEMU_TRADITIONAL="$RPM_OPT_FLAGS" export EXTRA_CFLAGS_QEMU_XEN="$RPM_OPT_FLAGS" with

hi is there any way to build 4.8 release with this fstack protection? or atleast some ports is there any good info on this? the only page i found was that ibm page but it seemed outdated. //martin

Hello, Does the -fstack-protector option work on CLANG 3.1 and 3.2? There is thread on FreeBSD forums about the stack protector and ports and I'm wondering if it's possible to use the -fstack-protector option with CLANG. http://forums.freebsd.org/showthread.php?t=36927 -Kimmo

On Thu, Jun 07, 2018 at 06:14:42PM -0700, PGNet Dev wrote: > On 6/7/18 6:08 PM, Darren Tucker wrote: > > Well the intent is you should be able to set CC and LD to whatever you > > want as long as they work. In this case, the OSSH_CHECK_LDFLAG_LINK > > test invokes autoconf's AC_LINK_IFELSE with uses CC not LD. I'm not > > sure what to do about it yet though. I

On Tue, Aug 2, 2016 at 12:52 AM, Darren Tucker <dtucker at zip.com.au> wrote: [...] >> Seems can't. But why? 7.2 does. > > Dunno, I can't think of any obvious changes to compiler flags. Maybe > try it without setting CFLAGS? OK, I think I see why it started in 7.3: it was when the wide character support was added. In configure.ac: dnl Wide character support. Linux