1 |
On Fri, Mar 30, 2018 at 10:37 AM, Robert Sharp |
2 |
<selinux@×××××××××××××××.org> wrote: |
3 |
> I requested a quote from GRsecurity and they told me that although they are |
4 |
> looking at providing a package for personal customers they don't have one at |
5 |
> the moment. They recommended minipli as the next best thing... |
6 |
> |
7 |
|
8 |
Is there any way for you to try again while presenting yourself as a |
9 |
business? In some jurisdictions saying you are a business is all it |
10 |
takes to start a sole proprietorship. Otherwise, just pretend you are |
11 |
affiliated with a (legally fictional) business. |
12 |
|
13 |
It is necessary that I present myself as working on behalf of business |
14 |
when requesting quotes for electronic components, etc., for personal |
15 |
projects. They have a tendency to not care otherwise. A past employer |
16 |
lets me use their email for this reason. |
17 |
|
18 |
Perhaps Mr. Ceccarelli can indicate the size of his employer before I |
19 |
try to contact them myself? |
20 |
|
21 |
Cheers, |
22 |
R0b0t1 |
23 |
|
24 |
> What about the grsecurity-source overlay? |
25 |
> |
26 |
> |
27 |
> On 29/03/18 11:47, Guillaume Ceccarelli wrote: |
28 |
> |
29 |
> Hi all, |
30 |
> |
31 |
> I’ve been a grsecurity customer for a little over two years now, and my use |
32 |
> of it is as a small business, on Gentoo server installations. While I can’t |
33 |
> disclose the amount of money I’m paying publicly because every deal is |
34 |
> customized, I would encourage you to get in touch using the contact form on |
35 |
> grsecurity.net and ask for a quote if you haven’t already. |
36 |
> |
37 |
> You might just end up with an arrangement you can afford, and grsec is still |
38 |
> certainly worth having today. Not only for the feature set, but also for the |
39 |
> constant looking over the mainline Linux kernel code, including fixing and |
40 |
> backporting more fixes than the regular kernel stable releases, and for |
41 |
> knowledge / emails giving context to important kernel vulnerabilities when |
42 |
> they occur. |
43 |
> |
44 |
> |
45 |
> Best, |
46 |
> |
47 |
> – Guillaume Ceccarelli |
48 |
> |
49 |
> On 28 Mar 2018, at 20:22, R0b0t1 <r030t1@×××××.com> wrote: |
50 |
> |
51 |
> On Wed, Mar 28, 2018 at 12:40 PM, Alex Efros <powerman@××××××××.name> wrote: |
52 |
> |
53 |
> Hi! |
54 |
> |
55 |
> |
56 |
> On Wed, Mar 28, 2018 at 06:06:00PM +0100, Robert Sharp wrote: |
57 |
> |
58 |
> Does anyone know of a good, post GRSecurity guide to reasonable security |
59 |
> |
60 |
> for the kernel? In the absence of anything else I will have to go back |
61 |
> |
62 |
> to the KSPP list and start removing stuff until I can get a stable kernel. |
63 |
> |
64 |
> |
65 |
> I'm using https://github.com/minipli/linux-unofficial_grsec, but it lacks |
66 |
> |
67 |
> Spectre and Meltdown mitigation at the moment (see issues). Still, I |
68 |
> |
69 |
> believe it's the best we can have now (better is probably paid GrSec, but |
70 |
> |
71 |
> AFAIK it's impossible or too costly to buy it for home or small business). |
72 |
> |
73 |
> |
74 |
> |
75 |
> Previous contributors have access to the code, but it doesn't seem |
76 |
> like there is any way to go that route anymore. |
77 |
> |
78 |
> |