Markus Wernig wrote:
And by making security updates more difficult, you think you have
improved security, right?
As you have demonstrated, you have not. If an attacker can use your
system's compile tools, they can also install the compile tools. But
it DOES take you longer to do all you can to keep them out in the first
place.
> I would thus need to pre-compile libssl on a 4.2 buildhost
yes, just make a release, and install that.
Or, install the compilation tools where you need them and be done with
it.
Nick.
| Theodore Tso | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 011/196] sysfs: Fix a copy-n-paste typo in comment |
git: | |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
