similar to: [PATCH 3/3] Add support for OpenBSD

Displaying 20 results from an estimated 100 matches similar to: "[PATCH 3/3] Add support for OpenBSD"

2013 Nov 27
20
[PATCH 0/4] efi: PE header generation fix
The PE headers of the generated efi file were quite buggy. And since OVMF perform a few consistency checks, syslinux was unable to run on it. I don't pretend to have a thorough understanding of the PE+ headers, some bugs may remain. :) Celelibi (4): efi: Fix PE header field rva_and_sizes_nr efi: Location, size and alignment of .text section efi: Useless relocations in PE file efi: PE
2006 May 26
3
Integrating ProPolice/SSP into FreeBSD
Hi, first sorry for cross-posting but I thought this patch might interest -CURRENT users as well as people concerned by security. I wrote a patch that integrates ProPolice/SSP into FreeBSD, one step further than it has been realized so far. It is available here : http://tataz.chchile.org/~tataz/FreeBSD/SSP/ Everything is explained on the web page, but I will repeat some informations here.
2005 Oct 26
1
Non-executable stack
Hi all Does FreeBSD support a non-executable stack on any of the tier 1 and 2 platforms that has this feature? If not, are there any plans of implementing this and is there a patch I can use for 6.0 (when it is released)? Best regards db
2007 Dec 25
3
ProPolice/SSP in 7.0
Hi there, I'm still running 6.2 on various servers without any tweaks (GENERIC kernel, binary updates via freebsd-update etc.) but lots of ports (apache, postgresql, diablo-jdk etc.) and would like to use stack smashing protection in order to harden my boxes and avoid many potential exploits. I've known about ProPolice/SSP for a while now (from the Gentoo world) and am aware that
2010 May 18
7
How to build a 64 bit xen
Hi experts,'' I build xen on my 64 bit redhat with "make xen", I got the image xen-4.0.0.gz then $gunzip xen-4.0.0.gz $file xen-4.0.0 it tells me it''s 32 bit,but I saw it link the 64 bit lib Thanks Lei -- "We learn from failure, not from success!" _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com
2010 May 18
7
How to build a 64 bit xen
Hi experts,'' I build xen on my 64 bit redhat with "make xen", I got the image xen-4.0.0.gz then $gunzip xen-4.0.0.gz $file xen-4.0.0 it tells me it''s 32 bit,but I saw it link the 64 bit lib Thanks Lei -- "We learn from failure, not from success!" _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com
2013 Jul 12
14
[PATCH] xen: arm: make zImage the default target which we install
From: Ian Campbell <ian.campbell@citrix.com> The zImage compatible binary is the useful one on real hardware. The relocated ELF thing is only really useful when booting directly on Fast Models. The customary suffix for that case is .axf so provide that as a target. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Cc: Wookey <wookey@linaro.org> --- xen/arch/arm/Makefile |
2006 Feb 25
1
[PATCH] fix mkelf32 when cross compiling on i386 for x86-64
Use strtoull to parse the final_exec_addr value from the command line. Whe cross compiling on i386 for x86-64 unsigned long is 32 bit, which leads to final_exec_addr being truncated to 32 bits by strtoul, which leads to grub refusing to load the resulting image. Please apply. Signed-Off-By: Muli Ben-Yehuda <mulix@mulix.org> diff -r 86eba2e17a39 -r ef4fe9970b03 xen/arch/x86/boot/mkelf32.c
2017 Jun 20
2
Dovecot >=2.2.29 + Filesystem quota = incorrect storage information
Hi, I have problem with quota storage information in dovecot-2.2.29 (and newer versions, too - 2.2.30.2). I use FS quota backend. ............................ # 2.2.29.1 (e0b76e3): /etc/dovecot/dovecot.conf # OS: Linux 4.4.68-1 x86_64 mail_plugins = quota plugin { quota = fs:User quota:mount=/poczta:user quota2 = fs:Group quota:mount=/poczta:group } protocol imap {
2005 Jan 12
1
sshd runs with -R flag?
Hi All, Sorry to interrupt, but I recently downloaded and installed a pre-compiled package of OpenSSH 3.9p1 for Solaris. After installation everything seems to work well, but I notice that all of the child sshd daemons are running with a flag '-R' i.e. sh-3.00# ps -ef | grep sshd root 475 1 0 13:45:23 ? 0:00 /usr/local/sbin/sshd -4 root 643 475 0 14:10:55 ?
2017 Jun 21
2
Dovecot >=2.2.29 + Filesystem quota = incorrect storage information
W dniu 20.06.2017 o 21:25, Timo Sirainen pisze: > On 20 Jun 2017, at 15.49, Macka <dovecot at macka.pl> wrote: >> Hi, >> >> I have problem with quota storage information in dovecot-2.2.29 (and >> newer versions, too - 2.2.30.2). >> I use FS quota backend. > . >> After upgrade from 2.2.27 to 2.2.29 (newest 2.2.30.2 too), dovecot >> returns
2020 Jul 17
2
hardlinks
Il 17/07/20 10:54, Karl Vogel ha scritto: > It depends on the size of the variables in the structure used by the > stat() call. In ext4, the "links" variable is an unsigned 16-bit integer, > so you have your limit of 64k or so. I've worked with systems where > the limit was a signed 16-bit integer, so it maxed out at 32k. > > XFS may be a full 32-bit integer, so
2013 Nov 29
1
[PATCH 1/4] efi: Fix PE header field rva_and_sizes_nr
On Wed, 27 Nov, at 02:38:28PM, Celelibi wrote: > The value of the field rva_and_sizes_nr is used by OVMF to check the > consistency of the PE file with respect to the field optional_hdr_sz. It > now have the right value. > > Signed-off-by: Celelibi <celelibi at gmail.com> > --- > efi/wrapper.c | 6 +++--- > efi/wrapper.h | 28 ++++++++++++++++------------ > 2
2008 Jan 19
1
Questions about building the world
1. I noticed the WITHOUT_SSP switch in src.conf(5). Does this mean that Propolice is currently used by default? 2. For debugging purposes, I'd like to rebuild my whole world with debugging symbols. Adding -g to the flags in make.conf seemed to do the trink until right before the installation of the new files. Doing a nm on libc.so.7 yielded all the symbols, as expected. However, after
2008 Dec 27
5
[LLVMdev] Controlling the stack layout
Hi everyone, As a front-end developer, I'd like to add a language-specific information at a fixed location of each stack frame. The reason is that I want to retrieve this information when dynamically walking the stack. For example, X86 has the following stack layout for a function with two arguments and two locals: 12(%ebp) - second function parameter 8(%ebp) - first function
2008 Dec 28
0
[LLVMdev] Controlling the stack layout
> I'd like to generate this layout: > > 12(%ebp) - second function parameter > 8(%ebp) - first function parameter > 4(%ebp) - old %EIP (the function's "return address") > 0(%ebp) - old %EBP (previous function's base pointer) > -4(%ebp) - My language specific information > -8(%ebp) - first local variable > -12(%ebp) -
2004 Feb 05
1
using libparanoia
Hi there, I was looking for stack smashing protection under freebsd, so i found libparanoia (/usr/ports/security/libparanoia), i had only one question using the normal 'make install' (so no copy-to-libc). If i add in /ert/make.conf: CFLAGS= -O -pipe -lparanoia -L/usr/local/lib COPTFLAGS= -O -pipe -lparanoia -L/usr/local/lib Will EVERYTHING build from that time (including
2008 Jun 10
1
[LLVMdev] LLVM on OpenBSD
Hello, Edd > I am a student considering a compiler design based dissertation with > llvm. I am having problems building llvm on OpenBSD-current. I hope to > make a port of llvm for OpenBSD once I have figured out how to build What is the gcc version used there? -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.
2004 Aug 06
1
Problems loading chan_h323 on Opteron 64 bit
Hi, I compiled asterisk and chan_h323 on an Opteron in 64 bit mode. In the h323's Makefile I replaced in line 24 CFLAGS += -march=$(shell uname -m) by CFLAGS += -march=k8 and also tried CFLAGS += -m64 -march=k8 Both solutions do compile, but when starting asterisk, a load error occurs: undefined symbol: _ZN14H323Connection24OnUserInputInlineRFC2833ER15OpalRFC2833Infoi When I grep
2013 Dec 01
0
[PATCH v2 4/4] efi: PE file size differ from in-memory size
PE headers code_sz and image_sz indicate more or less, the size of the file and the size of the in-memory image. They are now given the right value. In the ELF format, only the program headers are reliable to determine the actually needed part of the file and the in-memory size. The .bss section should always be marked as NOLOAD for ld since its content shouldn't be included into the binary