aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRessMic <binarynoodle44@gmail.com>2021-08-23 17:04:38 +0200
committerRessMic <binarynoodle44@gmail.com>2021-08-23 17:04:38 +0200
commit3efbac9f5067726c4d2efe84940301ff3e988e16 (patch)
treec0084d8a446b2b451e7f50f50b5e6a58652401e2
parent8112d3cfcb677617f33f154158baf6c193999153 (diff)
downloadguestbookPHP-3efbac9f5067726c4d2efe84940301ff3e988e16.tar.gz
guestbookPHP-3efbac9f5067726c4d2efe84940301ff3e988e16.tar.bz2
guestbookPHP-3efbac9f5067726c4d2efe84940301ff3e988e16.zip
Sending instructions and the filesHEADmain
-rw-r--r--README.md89
-rw-r--r--guestbook.php62
-rw-r--r--submitguest.php61
-rw-r--r--tablequery.txt6
4 files changed, 137 insertions, 81 deletions
diff --git a/README.md b/README.md
index 481311b..81ce7d1 100644
--- a/README.md
+++ b/README.md
@@ -1,91 +1,18 @@
# GuestbookPHP
-A small guestbook in PHP for personal sites and a present for a lainon.
+A small guestbook written in PHP for personal sites and a present for a lainon.
-## Getting started
+# Instructions
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+simply put the files on a server running PHP.
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+guestbook.php contains the form for guestbook and also a query to show the previously visited guests. Uses specialhtmlchars to be secure from javascript in the input.
-## Add your files
+submitrequest.php is where the form redirects to after an action is taken. There it makes a prepared statement to be secure from SQL injection.
-- [ ] [Create](https://gitlab.com/-/experiment/new_project_readme_content:e6efa09cba25e3904fca734926b7a42a?https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://gitlab.com/-/experiment/new_project_readme_content:e6efa09cba25e3904fca734926b7a42a?https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://gitlab.com/-/experiment/new_project_readme_content:e6efa09cba25e3904fca734926b7a42a?https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+tablequery.txt contains the Query to put in mysql to get the table created
-```
-cd existing_repo
-git remote add origin https://gitlab.com/RestlessMicrophone/guestbookPHP.git
-git branch -M main
-git push -uf origin main
-```
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.com/-/experiment/new_project_readme_content:e6efa09cba25e3904fca734926b7a42a?https://docs.gitlab.com/ee/user/project/integrations/)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://gitlab.com/-/experiment/new_project_readme_content:e6efa09cba25e3904fca734926b7a42a?https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://gitlab.com/-/experiment/new_project_readme_content:e6efa09cba25e3904fca734926b7a42a?https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://gitlab.com/-/experiment/new_project_readme_content:e6efa09cba25e3904fca734926b7a42a?https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Automatically merge when pipeline succeeds](https://gitlab.com/-/experiment/new_project_readme_content:e6efa09cba25e3904fca734926b7a42a?https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://gitlab.com/-/experiment/new_project_readme_content:e6efa09cba25e3904fca734926b7a42a?https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://gitlab.com/-/experiment/new_project_readme_content:e6efa09cba25e3904fca734926b7a42a?https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://gitlab.com/-/experiment/new_project_readme_content:e6efa09cba25e3904fca734926b7a42a?https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://gitlab.com/-/experiment/new_project_readme_content:e6efa09cba25e3904fca734926b7a42a?https://docs.gitlab.com/ee/user/clusters/agent/)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://gitlab.com/-/experiment/new_project_readme_content:e6efa09cba25e3904fca734926b7a42a?https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+# important!
+all echo statements in submitrequest.php are commented out. Feel free to use them though in case your code breaks on certain steps \ No newline at end of file
diff --git a/guestbook.php b/guestbook.php
new file mode 100644
index 0000000..132f25e
--- /dev/null
+++ b/guestbook.php
@@ -0,0 +1,62 @@
+<html>
+ <head>
+ <meta charset="utf-8">
+ <title>Guestbook</title>
+ </head>
+ <body>
+ <div class="input_guest">
+ <h1>Guestbook</h1>
+
+ <!--here in you submit info-->
+ <form action="submitguest.php" method="post" autocomplete="off">
+ <input type="g_name" name="g_name" placeholder="your name" id="g_name" required>
+ <input type="g_message" name="g_message" placeholder="your message" id="g_message" required>
+ <input type="submit" value="submit_button">
+ </form>
+ </div>
+ <!--here are the previous guests-->
+ <div class="input_guest">
+ <?php
+
+ //database info
+ // Change this to your connection info.
+ $DATABASE_HOST = 'YourHost';
+ $DATABASE_USER = 'YourDatabaseUser';
+ $DATABASE_PASS = 'YourDatabasePassword';
+ $DATABASE_NAME = 'YourDatabaseName';
+
+ // Create connection
+ $conn = new mysqli($DATABASE_HOST, $DATABASE_USER, $DATABASE_PASS, $DATABASE_NAME);
+ // Check connection
+ if ($conn->connect_error) {
+ die("Connection failed: " . $conn->connect_error);
+ }
+
+ $sql = "SELECT g_name, g_message FROM guestbook";
+
+ $result = $conn->query($sql);
+
+ if ($result->num_rows > 0) {
+ // output data of each row
+
+ while($row = $result->fetch_assoc()) {
+ echo'Name: '.htmlspecialchars($row["g_name"]);
+ echo'<br>';
+ echo'Message: '.htmlspecialchars($row["g_message"]);
+ echo'<br>';
+ echo'_______';
+ echo'<br>';
+
+ }
+
+ } else {
+ echo "<p>Be the first to write something here!</p>";
+ }
+ $conn->close();
+
+ ?>
+ </div>
+
+ </body>
+</html>
+
diff --git a/submitguest.php b/submitguest.php
new file mode 100644
index 0000000..96c27a9
--- /dev/null
+++ b/submitguest.php
@@ -0,0 +1,61 @@
+
+<?php
+
+// Change this to your connection info.
+$DATABASE_HOST = 'YourHost';
+$DATABASE_USER = 'YourDatabaseUser';
+$DATABASE_PASS = 'YourDatabasePassword';
+$DATABASE_NAME = 'YourDatabaseName';
+
+
+// Try and connect using the info above.
+$conn = new mysqli($DATABASE_HOST, $DATABASE_USER, $DATABASE_PASS, $DATABASE_NAME);
+// Check connection
+if ($conn->connect_error) {
+ die("Connection failed: " . $conn->connect_error);
+}
+
+
+//echo ' submitting...';
+
+$name = $_POST['g_name'];
+$message = $_POST['g_message'];
+
+//this is commented out but might be useful for debugging. NOTE: there are no special chars so javascript can be executed here
+//but it would only hurt the attacker
+/*
+echo $name;
+echo $message;
+*/
+
+//SQL query
+$stmt = $conn->prepare("INSERT INTO `guestbook` (g_name, g_message) VALUES (?, ?)");
+
+//echo 'statement prepared!';
+
+if ($stmt){
+//Prepared statement to secure from SQL injection
+$stmt->bind_param("ss", $name, $message);
+
+$stmt->execute();
+
+//echo' and done!';
+
+
+
+//to redirect after the query to your site, enter the url you want to go to
+header("Location: http://www.yourwebsite.com/");
+
+
+
+
+}
+else{
+ echo 'something went wrong!';
+}
+
+?>
+
+
+
+
diff --git a/tablequery.txt b/tablequery.txt
new file mode 100644
index 0000000..7f9a148
--- /dev/null
+++ b/tablequery.txt
@@ -0,0 +1,6 @@
+ create table guestbook(
+ g_id INT NOT NULL AUTO_INCREMENT,
+ g_name VARCHAR(100) NOT NULL,
+ g_message TEXT NOT NULL,
+ PRIMARY KEY ( g_id )
+); \ No newline at end of file