Najnowsze wypowiedzi
Je¿eli to mia³ byæ ¿art - nie by³ ¶mieszny.
Skoro juz to otworzyles w piatek zostaniesz pocalowany przez milosc twojego zycia, a jutro bedzie najlepszy dzien w twoim zyciu , lecz jesli nie wyslesz tego do 20 osob do 12 dzisiaj w nocy bedziesz...
W±tpiê, ¿eby to by³a kwestia ma³ej pamiêci. S±dzê, ¿e to wina zbyt ma³ej czêstotliwo¶ci od¶wie¿ania. Czyli czê¶ciej jej przypominaæ albo kupiæ jej pamiêæ statyczn± (za drogie)
Mówi±c mniej zawile. Masz dane i tworzysz tablice wype³nion± tymi danymi (jak±¶ procedur±) chcesz powiêkszyæ t± tablice o X nowych rekordów. Oczywi¶cie da siê to zrealizowaæ deklaruj±c wymiary...
w temacie wszystko chyba wyja¶ni³em. W excelu to wystarcza³o mi thiswork.path
Kurs
Rozdział 25. Installed as an Apache module
When PHP is used as an Apache module it inherits Apache's user permissions (typically those of the "nobody" user). This has several impacts on security and authorization. For example, if you are using PHP to access a database, unless that database has built-in access control, you will have to make the database accessible to the "nobody" user. This means a malicious script could access and modify the database, even without a username and password. It's entirely possible that a web spider could stumble across a database administrator's web page, and drop all of your databases. You can protect against this with Apache authorization, or you can design your own access model using LDAP, .htaccess files, etc. and include that code as part of your PHP scripts.
Often, once security is established to the point where the PHP user (in this case, the apache user) has very little risk attached to it, it is discovered that PHP is now prevented from writing any files to user directories. Or perhaps it has been prevented from accessing or changing databases. It has equally been secured from writing good and bad files, or entering good and bad database transactions.
A frequent security mistake made at this point is to allow apache root permissions, or to escalate apache's abilities in some other way.
Escalating the Apache user's permissions to root is extremely dangerous and may compromise the entire system, so sudo'ing, chroot'ing, or otherwise running as root should not be considered by those who are not security professionals.
There are some simpler solutions. By using open_basedir you can control and restrict what directories are allowed to be used for PHP. You can also set up apache-only areas, to restrict all web based activity to non-user, or non-system, files.
| Poprzedni | Spis treści | Następny |
| Case 4: PHP parser outside of web tree | Początek rozdziału | Filesystem Security |
Obsługa wielowątkowości, jak to wykonać, przykład gdy wątki próbują robić coś równocześnie (jak temu zapobiec, lub jak to obsłużyć) np w przypadku obiektu klasy RECORDSET jeden cos tam jeszcze myka pobiera, się wcina i przed pobraniem następuje zamkniecie (close()) obiektu recordset.