Task #31556
Check security-related stuff from Inside TYPO3
| Status: | Closed | Start date: | 2011-11-03 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 100% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 0 |
Description
Manual "Inside TYPO3" has a chapter about security:
http://typo3.org/documentation/document-library/core-documentation/doc_core_inside/4.2.0/view/2/10/
It's rather short and - after taking a quick look - most of its material seems out of date, but please check it out to see if there's anything worth adding to the Security Guide.
Please also report if you think that this chapter can be entirely removed from Inside TYPO3 in a future update, or - if not - what should stay there. Thanks!
Related issues
| related to Inside TYPO3 - Task #32087: Point to the Security Guide | Accepted | 2011-11-25 |
History
Updated by Michael Schams over 1 year ago
- Status changed from New to Under Review
My first impression: seems like old and outdated, as you said. Mentions TYPO3 version 3.x and security-related issues from 2002. However, some of the advices are still valid but in general I would suggest to have ONE document instead of two or more that deal with security advices. Simply for consistency purposes and to make our life easier (only maintain one document) as well as the users/admins of TYPO3 (it is confusing to read multiple documents and maybe the information are inconsistent).
I will have a closer look soon but I am incline to recommend to drop this chapter from the "TYPO3 Inside" doc and reference to the (new) Security Guide when it is finished and released.
Updated by Chris topher over 1 year ago
Michael wrote:
(...) I am incline to recommend to drop this chapter from the "TYPO3 Inside" doc and reference to the (new) Security Guide when it is finished and released.
Sounds reasonable, I would do the same.
Updated by Chris topher over 1 year ago
I have just opened #32087, which aims to modify "Inside TYPO3" accordingly.
So I would say this issue can be closed. :-)
Updated by Chris topher over 1 year ago
- Status changed from Under Review to Closed
- % Done changed from 0 to 100