search for: secdev

In creating a test case for a bug fix in llvm-objdump, I noticed that it differs in its output of pc-relative immediates from objdump: [secdev:/tmp] s$ cat a.s main: jmp .LBL0 .LBL0: ret [secdev:/tmp] s$ llvm-mc -filetype=obj a.s > a.o [secdev:/tmp] s$ objdump -d a.o |tail -n 2 0: eb 00 jmp 2 <main+0x2> 2: c3 retq [secdev:/tmp] s$ llvm-objdump -d a.o |tail -n 2...

On Thu, Oct 17, 2013 at 10:55 AM, Stephen Checkoway <s at pahtak.org> wrote: > In creating a test case for a bug fix in llvm-objdump, I noticed that it > differs in its output of pc-relative immediates from objdump: > > [secdev:/tmp] s$ cat a.s > main: > jmp .LBL0 > .LBL0: > ret > [secdev:/tmp] s$ llvm-mc -filetype=obj a.s > a.o > [secdev:/tmp] s$ objdump -d a.o |tail -n 2 > 0: eb 00 jmp 2 <main+0x2> > 2: c3 retq > [sec...

Hi list, I am starting a academic security related project and I was wondering if there is any documentation on compiling xen/dom0 with a recent kernel? I''ve seen a few good intentioned threads, but no real documentation so far. Any helpful pointers will be greatly appreciated! Thanks in advance, - SDG P.S: First mail, not sure if I should post it here...let me know if I am on the

...t that? I haven't looked into it but while building Chromium with LTO, I get: ../../third_party/gold/gold64: fatal error: out of file descriptors and couldn't close any clang: error: linker command failed with exit code 1 (use -v to see invocation) ninja: build stopped: subcommand failed. [secdev:~/chromium/src/out/Release] (master) s$ ulimit -Sn 10000 Looking in /proc, it has 10013 open file descriptors. With only 2 objects loaded at a time, I'd expect many fewer file descriptors to be open. Maybe it only has 2 objects in memory at once but keeps all the file descriptors open? -- St...

...oked into it but while building Chromium with LTO, I get: > > ../../third_party/gold/gold64: fatal error: out of file descriptors and couldn't close any > clang: error: linker command failed with exit code 1 (use -v to see invocation) > ninja: build stopped: subcommand failed. > [secdev:~/chromium/src/out/Release] (master) s$ ulimit -Sn > 10000 > > Looking in /proc, it has 10013 open file descriptors. With only 2 objects loaded at a time, I'd expect many fewer file descriptors to be open. Maybe it only has 2 objects in memory at once but keeps all the file descriptors...

...e building Chromium with LTO, I get: >> >> ../../third_party/gold/gold64: fatal error: out of file descriptors and couldn't close any >> clang: error: linker command failed with exit code 1 (use -v to see invocation) >> ninja: build stopped: subcommand failed. >> [secdev:~/chromium/src/out/Release] (master) s$ ulimit -Sn >> 10000 >> >> Looking in /proc, it has 10013 open file descriptors. With only 2 objects loaded at a time, I'd expect many fewer file descriptors to be open. Maybe it only has 2 objects in memory at once but keeps all the fil...

...with LTO, I get: >>> >>> ../../third_party/gold/gold64: fatal error: out of file descriptors and couldn't close any >>> clang: error: linker command failed with exit code 1 (use -v to see invocation) >>> ninja: build stopped: subcommand failed. >>> [secdev:~/chromium/src/out/Release] (master) s$ ulimit -Sn >>> 10000 >>> >>> Looking in /proc, it has 10013 open file descriptors. With only 2 objects loaded at a time, I'd expect many fewer file descriptors to be open. Maybe it only has 2 objects in memory at once but keeps...

> Letting the module own MDNodes may not be a win for gold since it is going > to create multiple copies of MDNodes that could be shared with Context > owning MDNodes. > > For example, with debug info type uniquing, the type nodes can be shared > across modules, but with module owning MDNodes, each module will create its > own copy of the type nodes. The advantage is that the

...1.36.2.6.2.1 src/sys/netinet6/in6_proto.c 1.32.2.4.2.1 src/sys/netinet6/route6.c 1.11.2.1.2.1 - ------------------------------------------------------------------------- VII. References http://www.secdev.org/conf/IPv6_RH_security-csw07.pdf http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2242 The latest revision of this advisory is available at http://security.FreeBSD.org/advisories/FreeBSD-SA-07:03.ipv6.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD4DBQFGMTlvFdaIBMps...

On Wed, Nov 13, 2013 at 7:58 PM, Rafael Espíndola < rafael.espindola at gmail.com> wrote: > > It sounds like the linker could call lto_module_dispose() right after > > lto_codegen_add_module() to help reduce the memory footprint. That > would be > > a simple linker change. A slightly larger linker change would be to > > immediately call lto_codegen_add_module()

...moron - making fine-grained memory randomization practical by allowing code sharing. In USENIX Security Symposium, 2014. https://www.usenix.org/node/184466 [2] S. Crane, A. Homescu, and P. Larsen. Code randomization: Haven’t we solved this problem yet? In IEEE Cybersecurity Development Conference (SecDev), 2016. http://www.ics.uci.edu/~perl/sd16_pagerando.pdf

...tion practical by allowing code sharing. In USENIX Security >> Symposium, 2014. https://www.usenix.org/node/184466 >> >> [2] S. Crane, A. Homescu, and P. Larsen. Code randomization: Haven’t >> we solved this problem yet? In IEEE Cybersecurity Development >> Conference (SecDev), 2016. >> http://www.ics.uci.edu/~perl/sd16_pagerando.pdf >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > Out of curiosity, Did you me...

...SENIX Security > >>> Symposium, 2014. https://www.usenix.org/node/184466 > >>> > >>> [2] S. Crane, A. Homescu, and P. Larsen. Code randomization: Haven’t > >>> we solved this problem yet? In IEEE Cybersecurity Development > >>> Conference (SecDev), 2016. > >>> http://www.ics.uci.edu/~perl/sd16_pagerando.pdf > >>> _______________________________________________ > >>> LLVM Developers mailing list > >>> llvm-dev at lists.llvm.org > >>> http://lists.llvm.org/cgi-bin/mailman/listinfo/ll...

...1.36.2.6.2.1 src/sys/netinet6/in6_proto.c 1.32.2.4.2.1 src/sys/netinet6/route6.c 1.11.2.1.2.1 - ------------------------------------------------------------------------- VII. References http://www.secdev.org/conf/IPv6_RH_security-csw07.pdf http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2242 The latest revision of this advisory is available at http://security.FreeBSD.org/advisories/FreeBSD-SA-07:03.ipv6.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD4DBQFGMTlvFdaIBMps...

...Symposium, 2014. https://www.usenix.org/node/184466 >>> >>> >>> >>> [2] S. Crane, A. Homescu, and P. Larsen. Code randomization: Haven’t >>> >>> we solved this problem yet? In IEEE Cybersecurity Development >>> >>> Conference (SecDev), 2016. >>> >>> http://www.ics.uci.edu/~perl/sd16_pagerando.pdf >>> >>> _______________________________________________ >>> >>> LLVM Developers mailing list >>> >>> llvm-dev at lists.llvm.org >>> >>> http://li...