Running Oolite-Fedora Core 5 - Revision history

Cholmondely: Tagged as Help page

2021-07-12T22:56:40Z

Tagged as Help page

Debresser: moved Oolite on Fedora Core 5 to Running Oolite-Fedora Core 5: Like all other instruction articles.

2016-01-24T19:05:40Z

moved Oolite on Fedora Core 5 to Running Oolite-Fedora Core 5: Like all other instruction articles.

Debresser: Category:Factual

2016-01-24T19:04:38Z

Category:Factual

Svengali at 18:49, 9 June 2012

2012-06-09T18:49:45Z

Winston at 14:41, 11 July 2006

2006-07-11T14:41:02Z

Winston at 18:11, 21 March 2006

2006-03-21T18:11:49Z

Winston at 18:11, 21 March 2006

2006-03-21T18:11:12Z

New page

== Oolite on Fedora Core 5 ==

Fedora Core 5 has greatly increased the security level of a desktop Linux build. It includes SElinux, a mandatory access control security system that is unmatched outside of the mainframe world. However, due to the way GNUstep works, this spells trouble for Oolite. GNUstep uses something called 'trampolining' when running, which puts executable code (deliberately) on the heap. The default SElinux policy on Fedora Core 5 forbids an executable heap (for the very good reason that it neuters all buffer overflow attacks against software, since an executable heap allows a malicious person to inject code into buggy programs. No executable heap - and the exploit will not run, because SElinux will abort the process).

To run Oolite, at present you must allow an executable heap. This is not an ideal state of affairs, but will have to suffice until GNUstep is fixed or an SElinux policy is created for Oolite to allow this to only apply to the Oolite executable. This is what you need to do to make the Autopackage or tarball installers work on Fedora Core 5.

1. Go to System -> Administration -> Security Level and Firewall
2. Enter your root password
3. Select the SElinux tab
4. Select 'Modify SElinux policy'
5. Scroll down to 'Other' and select it.
6. Tick the checkbox 'allow_execheap'
7. Click OK

Oolite should now be able to run.

You can also turn SElinux from 'Enforcing' to 'Permissive', but it this is not recommended since SElinux does a great deal to help keep your system secure.

@@ Line 21: / Line 21: @@
 * [[Running_Oolite-Unix|Running Oolite on Unix]]
-[[Category:Oolite]]
+[[Category:Oolite]][[Category:Help pages]]
 [[Category:Factual]]

← Older revision		Revision as of 19:04, 24 January 2016
Line 22:		Line 22:

	[[Category:Oolite]]		[[Category:Oolite]]
		+	[[Category:Factual]]

← Older revision		Revision as of 18:49, 9 June 2012
Line 16:		Line 16:

	This may apply to other distributions that have SElinux enabled by default.		This may apply to other distributions that have SElinux enabled by default.
		+
		+	==Links==
		+	* [[Running_Oolite-Linux\|Running Oolite under Linux]]
		+	* [[Running_Oolite-Unix\|Running Oolite on Unix]]

	[[Category:Oolite]]		[[Category:Oolite]]

← Older revision		Revision as of 14:41, 11 July 2006
Line 16:		Line 16:

	This may apply to other distributions that have SElinux enabled by default.		This may apply to other distributions that have SElinux enabled by default.
		+
		+	[[Category:Oolite]]

← Older revision		Revision as of 18:11, 21 March 2006
Line 1:		Line 1:
−	== Oolite on Fedora Core 5 ==
−
	Fedora Core 5 has greatly increased the security level of a desktop Linux build. It includes SElinux, a mandatory access control security system that is unmatched outside of the mainframe world. However, due to the way GNUstep works, this spells trouble for Oolite. GNUstep uses something called 'trampolining' when running, which puts executable code (deliberately) on the heap. The default SElinux policy on Fedora Core 5 forbids an executable heap (for the very good reason that it neuters all buffer overflow attacks against software, since an executable heap allows a malicious person to inject code into buggy programs. No executable heap - and the exploit will not run, because SElinux will abort the process).		Fedora Core 5 has greatly increased the security level of a desktop Linux build. It includes SElinux, a mandatory access control security system that is unmatched outside of the mainframe world. However, due to the way GNUstep works, this spells trouble for Oolite. GNUstep uses something called 'trampolining' when running, which puts executable code (deliberately) on the heap. The default SElinux policy on Fedora Core 5 forbids an executable heap (for the very good reason that it neuters all buffer overflow attacks against software, since an executable heap allows a malicious person to inject code into buggy programs. No executable heap - and the exploit will not run, because SElinux will abort the process).

Line 16:		Line 14:

	You can also turn SElinux from 'Enforcing' to 'Permissive', but it this is not recommended since SElinux does a great deal to help keep your system secure.		You can also turn SElinux from 'Enforcing' to 'Permissive', but it this is not recommended since SElinux does a great deal to help keep your system secure.
		+
		+	This may apply to other distributions that have SElinux enabled by default.

← Older revision	Revision as of 19:05, 24 January 2016
(No difference)