Displaying 3 results from an estimated 3 matches for "743777".
Did you mean:
743717
2017 Feb 18
2
[RFC] Using Intel MPX to harden SafeStack
...|175297|175489|235577 |
+--------------+---------+---------+---------+-------+
|403.gcc|2420209|2545041|2545233|2727913|
+--------------+---------+---------+---------+-------+
|429.mcf|10977|105345|105537|155705 |
+--------------+---------+---------+---------+-------+
|445.gobmk|633953|743585|743777|823993 |
+--------------+---------+---------+---------+-------+
|456.hmmer|258593|358033|358225|432249 |
+--------------+---------+---------+---------+-------+
|458.sjeng|96593|192929|193121|251545 |
+--------------+---------+---------+---------+-------+
|462.libquantum|32441|127065|127257|17...
2012 Aug 31
1
dovecotadm error
When I use the following command:
doveadm expunge -A mailbox Junk savedbefore 28d
I get:
doveadm(root): Error: User listing returned failure
In the mail log file it says:
dovecot: auth-worker(18549): Error: sql: Iterate query failed: Table
'system.users' doesn't exist (using built-in default iterate_query:
SELECT username, domain FROM users)
However this is setup:
2017 Feb 08
4
[RFC] Using Intel MPX to harden SafeStack
Hi,
I previously posted about using 32-bit X86 segmentation to harden SafeStack: http://lists.llvm.org/pipermail/llvm-dev/2016-May/100346.html That involves lowering the limits of the DS and ES segments that are used for ordinary data accesses while leaving the limit for SS, the stack segment, set to its maximum value. The safe stacks were clustered above the limits of DS and ES. Thus, by