similar to: debian lintian warn: hardening-no-fortify-functions

Displaying 20 results from an estimated 1000 matches similar to: "debian lintian warn: hardening-no-fortify-functions"

2018 Mar 30
0
debian lintian warn: hardening-no-fortify-functions
> On 30 March 2018 at 15:08 "A. Schulze" <sca at andreasschulze.de> wrote: > > > Hello, > > to build + packages dovecot I use the usual Debian tool chain. That includes build with selected GCC options and running lintian. > > I notice since a long time (read: many earlier versions, up to 2.2.35) this lintian warnings: > > I: dovecot-core:
2017 Aug 15
4
v2.2.32 release candidate released
https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz.sig There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level
2017 Aug 15
4
v2.2.32 release candidate released
https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz.sig There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level
2024 May 21
1
Default CXXFLAGS
On Tue, 21 May 2024 14:48:48 +0200 Kurt Hornik <Kurt.Hornik at wu.ac.at> wrote: > I guess foer the CXXFLAGS we want dpkg-buildflags --get CXXFLAGS? It must be the case. It's both the documented option [1] and it currently differs from CFLAGS in the offending flag: root at 93e09ba5b6fb:/# diff -u <(dpkg-buildflags --get CFLAGS | sed 's/ /\n/g') <(dpkg-buildflags --get
2024 May 21
1
Default CXXFLAGS
>>>>> Ivan Krylov writes: > On Tue, 21 May 2024 07:08:02 -0500 > Dirk Eddelbuettel <edd at debian.org> wrote: >> You cannot undo what it is in R's own /etc/R/Makeconf via a >> programmatic way via some sort of option or alike. > I think this is about the following line in debian/rules: Without having looked in much detail, I guess foer the CXXFLAGS
2024 May 21
1
Default CXXFLAGS
On Tue, 21 May 2024 07:08:02 -0500 Dirk Eddelbuettel <edd at debian.org> wrote: > You cannot undo what it is in R's own /etc/R/Makeconf via a > programmatic way via some sort of option or alike. I think this is about the following line in debian/rules: optimflags = `DEB_BUILD_MAINT_OPTIONS=optimize=-lto dpkg-buildflags --get CFLAGS`
2011 Apr 03
1
another question on shapefiles and geom_point in ggplot2
Manuel: I changed your variable names from x to 'long' and y to 'lat' on the riqueza_out.csv file. The code below should do what you want. Also, since the legend title is kind of long, I broke it down into three lines so you can see more plot area. I am cc'ing the other groups so more people use it if needed. library(rgdal) library(ggplot2) library(sp) library(maptools)
2013 Jan 07
0
[LLVMdev] Disabling Fortify in llvm
Hi, I couldn't find an equivalent GCC flag -D_FORTIFY_SOURCE in llvm. May I ask how can I disable the fortify source checking in LLVM please? More specifically, I want to bypass/ignore the errors like __fortify_fail Cheers, Ahmad -------------- next part -------------- An HTML attachment was scrubbed... URL:
2023 Sep 08
1
[Bridge] [PATCH AUTOSEL 4.14 6/8] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> [ Upstream commit a7ed3465daa240bdf01a5420f64336fee879c09d ] When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following warning appears: In function ?fortify_memcpy_chk?, inlined from ?size_entry_mwt? at net/bridge/netfilter/ebtables.c:2118:2: ./include/linux/fortify-string.h:592:25: error: call to
2023 Sep 08
0
[Bridge] [PATCH AUTOSEL 6.5 33/45] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> [ Upstream commit a7ed3465daa240bdf01a5420f64336fee879c09d ] When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following warning appears: In function ?fortify_memcpy_chk?, inlined from ?size_entry_mwt? at net/bridge/netfilter/ebtables.c:2118:2: ./include/linux/fortify-string.h:592:25: error: call to
2023 Sep 08
0
[Bridge] [PATCH AUTOSEL 6.1 20/26] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> [ Upstream commit a7ed3465daa240bdf01a5420f64336fee879c09d ] When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following warning appears: In function ?fortify_memcpy_chk?, inlined from ?size_entry_mwt? at net/bridge/netfilter/ebtables.c:2118:2: ./include/linux/fortify-string.h:592:25: error: call to
2023 Sep 08
0
[Bridge] [PATCH AUTOSEL 6.4 30/41] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> [ Upstream commit a7ed3465daa240bdf01a5420f64336fee879c09d ] When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following warning appears: In function ?fortify_memcpy_chk?, inlined from ?size_entry_mwt? at net/bridge/netfilter/ebtables.c:2118:2: ./include/linux/fortify-string.h:592:25: error: call to
2023 Sep 08
0
[Bridge] [PATCH AUTOSEL 5.10 11/14] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> [ Upstream commit a7ed3465daa240bdf01a5420f64336fee879c09d ] When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following warning appears: In function ?fortify_memcpy_chk?, inlined from ?size_entry_mwt? at net/bridge/netfilter/ebtables.c:2118:2: ./include/linux/fortify-string.h:592:25: error: call to
2023 Sep 08
0
[Bridge] [PATCH AUTOSEL 5.15 12/15] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> [ Upstream commit a7ed3465daa240bdf01a5420f64336fee879c09d ] When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following warning appears: In function ?fortify_memcpy_chk?, inlined from ?size_entry_mwt? at net/bridge/netfilter/ebtables.c:2118:2: ./include/linux/fortify-string.h:592:25: error: call to
2023 Aug 16
0
[Bridge] [PATCH net-next v4] netfilter: ebtables: fix fortify warnings in size_entry_mwt()
From: "GONG, Ruiqi" <gongruiqi1 at huawei.com> When compiling with gcc 13 and CONFIG_FORTIFY_SOURCE=y, the following warning appears: In function ?fortify_memcpy_chk?, inlined from ?size_entry_mwt? at net/bridge/netfilter/ebtables.c:2118:2: ./include/linux/fortify-string.h:592:25: error: call to ?__read_overflow2_field? declared with attribute warning: detected read beyond
2010 Jun 23
1
Plotting Data on a Map
Hi: I am practicing with the attached shapefile and was wondering if I can get some help. Haven't used 'rgdal' and 'maptools' much but it appears to be a great way bring map data into R. Please take a look at the comments and let me know if I need to explain better what I am trying to accomplish. library(rgdal) library(maptools) library(ggplot2) dsn="C:/Documents and
2010 Jun 23
1
Shapefile
Hopefully the attachment will make it this time... Hi: I am practicing with the attached shapefile and was wondering if I can get some help. Haven't used 'rgdal' and 'maptools' much but it appears to be a great way bring map data into R. Please take a look at the comments and let me know if I need to explain better what I am trying to accomplish. library(rgdal)
2009 Jun 02
2
Adding a method to a generic in another package
I am the maintainer of the 'tis' package. One of the functions in my package is 'nberShade'. A user wants to make nberShade generic, with the old version renamed as nberShade.default, all of which is fine with me. And he wants to add a new method, nberShade.ggplot, which works for objects of class ggplot. He also wants to add a method fortify.tis for the generic fortify defined
2019 Dec 03
5
clang and -D_FORTIFY_SOURCE=1
Hi folks (CCing llvm-dev, but that's probably more of a cfe-dev topic), As a follow-up to that old thread about -D_FORTIFY_SOURCE=n http://lists.llvm.org/pipermail/cfe-dev/2015-November/045845.html And, more recently, to this fedora thread where clang/llvm -D_FORTIFY_SOURCE support is claimed to be only partial: https://pagure.io/fesco/issue/2020 I dig into the glibc headers in
2010 Jun 09
1
[R-sig-Geo] How to extract coordinates values from a shapefile?
I'm not sure if this is what you want. But the function coordinates() in sp package gives you the coordinates of SpatialObjects. Regards. Rodrigo. 2010/6/9 Nikhil Kaza <nikhil.list@gmail.com> > You need to execute gpclibPermit() to enable gpclib. > > library(maptools) should have issued a warning to that effect. > > > Nikhil Kaza > Asst. Professor, > City and