11 Commits (bf7dc2f2e7a4ef82db38d10deebfdfaebdac4b13)

Author	SHA1	Message	Date
Daniel Kesselberg	dd3fa88b36	chore: check enums for since and experimental comments ... Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>	1 year ago
provokateurin	72571a19dd	build(psalm): Configure unstable namespace ... Signed-off-by: provokateurin <kate@provokateurin.de>	1 year ago
provokateurin	a94249d1d5	build(psalm): Enforce named attribute arguments ... Signed-off-by: provokateurin <kate@provokateurin.de>	1 year ago
Andy Scherzinger	3a161f74fb	fix: move SPDX info of generated files to dep5 definition ... Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>	2 years ago
Andy Scherzinger	1df96b0417	chore: Add SPDX header ... Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>	2 years ago
Joas Schilling	887c061fc8	fix(OCP): Check for typos in "deprecated" ... Signed-off-by: Joas Schilling <coding@schilljs.com>	2 years ago
jld3103	e7926b9644	Refactor AppFrameworkTainter to make it more readable ... Signed-off-by: jld3103 <jld3103yt@gmail.com>	3 years ago
jld3103	14283001a5	Update AppFrameworkTainter to use non-deprecated interface ... Signed-off-by: jld3103 <jld3103yt@gmail.com>	3 years ago
Daniel Kesselberg	258c919b3c	ci: migrate ocp since checker to psalm ... Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>	3 years ago
dependabot-preview[bot]	eb502c02ff	Bump nextcloud/coding-standard from 0.3.0 to 0.5.0 ... Bumps [nextcloud/coding-standard](https://github.com/nextcloud/coding-standard) from 0.3.0 to 0.5.0. - [Release notes](https://github.com/nextcloud/coding-standard/releases) - [Changelog](https://github.com/nextcloud/coding-standard/blob/master/CHANGELOG.md) - [Commits](https://github.com/nextcloud/coding-standard/compare/v0.3.0...v0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>	5 years ago
Lukas Reschke	47ac8e0028	Add Psalm Taint Flow Analysis ... This adds the Psalm Security Analysis, as described at https://psalm.dev/docs/security_analysis/ It also adds a plugin for adding input into AppFramework. The results can be viewed in the GitHub Security tab at https://github.com/nextcloud/server/security/code-scanning **Q&A:** Q: Why do you not use the shipped Psalm version? A: I do a lot of changes to the Psalm Taint behaviour. Using released versions is not gonna get us the results we want. Q: How do I improve false positives? A: https://psalm.dev/docs/security_analysis/avoiding_false_positives/ Q: How do I add custom sources? A: https://psalm.dev/docs/security_analysis/custom_taint_sources/ Q: We should run this on apps! A: Yes. Q: What will change in Psalm? A: Quite some of the PHP core functions are not yet marked to propagate the taint. This leads to results where the taint flow is lost. That's something that I am currently working on. Q: Why is the plugin MIT licensed? A: Because its the first of its kind (based on GitHub Code Search) and I want other people to copy it if they want to. Security is for all :) Signed-off-by: Lukas Reschke <lukas@statuscode.ch>	5 years ago