Trueability Testing
-
Gonna be participating in a trueability test coming up and was wondering what to expect. Has anyone had any experience with this?
-
Don't know that one. Like Previsor?
-
-
Nope, don't know it.
-
I've taken a couple of tests there(or somewhere similar)... they're kinda like knowledge tests for whatever... I had a couple of linux tests, and basically, there's a time limit to do something, and you can get it done however, you can get it done.
Like write a shell script to extract data from two files, and then combine them into a CSV or something like that.
It's not terrible, and I like the way the tests are done.
-
@dafyre Yeah, it was pretty intense. It really digs deep to see if you have the knowledge needed. I just did a test on my own accord and was given the following:
Apache Self Assess
101: Baseline Implementation
Installation and Global Configuration- Install the Apache HTTPD Webserver via the distro's packaging system (yum/apt)
- Ensure that the following modules are installed and enabled:
- Mod Rewrite
- Mod SSL
- Configure the server admin email address (globally) [email protected]
- Configure the server so that its signature is displayed on server-generated pages (such as 500 Internal Server Error), and that it also includes the server admin's email address in the signature.
- Enable the server status page at http://localhost/server-statusaccessible only by the host 127.0.0.1
Users, Groups, and Files - Create the system group webadmin
- Create the system user don.draper with the following credentials:
- Password: IXnMe2Fp
- Home Directory: /home/don.draper
- Primary Group: don.draper
- Secondary Group: webadmin
- Create the system user peggy.olson:
- Password: 3Hx1M8aS
- Home Directory: /home/peggy.olson
- Primary Group: peggy.olson
- Secondary Group: webadmin
- Create the directory /var/www/vhosts, with the following ownership and permissions:
- User Ownership / Permissions: root / Read, Write, and Execute
- Group Ownership / Permissions: webadmin / Read, Write, and Execute.
- Other Permissions: Everyone should have Read, and Execute permissions.
- All future files and directories created in the /var/www/vhosts directory should automatically inherit the same group ownership of webadmin.
Virtual Hosts
Configure the web server for the following virtual hosts, and specifications.
VirtualHost 1 - Server Name: site1.104.239.228.184.xip.io
- Document Root: /var/www/vhosts/site1/htdocs
- Access Log: /var/www/vhosts/site1/logs/access.log
- Error Log: /var/www/vhosts/site1/logs/error.log
- Copy the content of this virtual host from /root/files/site1 to the document root
Ensure that the proper content is returned when this site is accessed athttp://site1.104.239.228.184.xip.io, and there are no errors in the logs.
VirtualHost 2 - Server Name: site2.104.239.228.184.xip.io
- The virtual host should also respond to the following aliases:
- Document Root: /var/www/vhosts/site2/htdocs
- Access Log: /var/www/vhosts/site2/logs/access.log
- Error Log: /var/www/vhosts/site2/logs/error.log
- Copy the content of this virtual host from /root/files/site2 to the document root
- Configure Apache with any necessary PHP modules required for the site
Ensure that the proper content is returned when this site is accessed athttp://site2.104.239.228.184.xip.io, that the aliases for www and webreturn the proper content, and there are no errors in the logs.
VirtualHost 3 - Document Root: /var/www/vhosts/site3/htdocs
- Access Log: /var/www/vhosts/site3/logs/access.log for HTTP and/var/www/vhosts/site3/logs/ssl_access.log for HTTPS
- Error Log: /var/www/vhosts/site3/logs/error.log for HTTP and/var/www/vhosts/site3/logs/ssl_error.log for HTTPS
- Copy the content of this virtual host from /root/files/site3 to the document root
- Restrict access to this site with HTTP Basic Auth, with the user namewebadmin and password 4v2JaLuQ
- Configure the document root so that a directory listing is displayed in the browser, rather than an index page.
- Configure this site to respond on both HTTP, and HTTPS standard ports, however all traffic that comes through over HTTP must be redirected to the HTTPS virtual host. Any self-signed certificate will do.
Ensure that the proper content is returned when this site is accessed athttps://site3.104.239.228.184.xip.io and that the traffic is redirected when accessing http://site3.104.239.228.184.xip.io. No content should be returned without proper authentication as mentioned above, and there are no errors in the logs.
Was given 3 hours to finish, and unfortunately I did not. Looks like I have some studying to do
-
@antonit said:
@dafyre Yeah, it was pretty intense. It really digs deep to see if you have the knowledge needed. I just did a test on my own accord and was given the following:
Apache Self Assess
101: Baseline Implementation
Installation and Global Configuration- Install the Apache HTTPD Webserver via the distro's packaging system (yum/apt)
- Ensure that the following modules are installed and enabled:
- Mod Rewrite
- Mod SSL
- Configure the server admin email address (globally) [email protected]
- Configure the server so that its signature is displayed on server-generated pages (such as 500 Internal Server Error), and that it also includes the server admin's email address in the signature.
- Enable the server status page at http://localhost/server-statusaccessible only by the host 127.0.0.1
Users, Groups, and Files - Create the system group webadmin
- Create the system user don.draper with the following credentials:
- Password: IXnMe2Fp
- Home Directory: /home/don.draper
- Primary Group: don.draper
- Secondary Group: webadmin
- Create the system user peggy.olson:
- Password: 3Hx1M8aS
- Home Directory: /home/peggy.olson
- Primary Group: peggy.olson
- Secondary Group: webadmin
- Create the directory /var/www/vhosts, with the following ownership and permissions:
- User Ownership / Permissions: root / Read, Write, and Execute
- Group Ownership / Permissions: webadmin / Read, Write, and Execute.
- Other Permissions: Everyone should have Read, and Execute permissions.
- All future files and directories created in the /var/www/vhosts directory should automatically inherit the same group ownership of webadmin.
Virtual Hosts
Configure the web server for the following virtual hosts, and specifications.
VirtualHost 1 - Server Name: site1.104.239.228.184.xip.io
- Document Root: /var/www/vhosts/site1/htdocs
- Access Log: /var/www/vhosts/site1/logs/access.log
- Error Log: /var/www/vhosts/site1/logs/error.log
- Copy the content of this virtual host from /root/files/site1 to the document root
Ensure that the proper content is returned when this site is accessed athttp://site1.104.239.228.184.xip.io, and there are no errors in the logs.
VirtualHost 2 - Server Name: site2.104.239.228.184.xip.io
- The virtual host should also respond to the following aliases:
- Document Root: /var/www/vhosts/site2/htdocs
- Access Log: /var/www/vhosts/site2/logs/access.log
- Error Log: /var/www/vhosts/site2/logs/error.log
- Copy the content of this virtual host from /root/files/site2 to the document root
- Configure Apache with any necessary PHP modules required for the site
Ensure that the proper content is returned when this site is accessed athttp://site2.104.239.228.184.xip.io, that the aliases for www and webreturn the proper content, and there are no errors in the logs.
VirtualHost 3 - Document Root: /var/www/vhosts/site3/htdocs
- Access Log: /var/www/vhosts/site3/logs/access.log for HTTP and/var/www/vhosts/site3/logs/ssl_access.log for HTTPS
- Error Log: /var/www/vhosts/site3/logs/error.log for HTTP and/var/www/vhosts/site3/logs/ssl_error.log for HTTPS
- Copy the content of this virtual host from /root/files/site3 to the document root
- Restrict access to this site with HTTP Basic Auth, with the user namewebadmin and password 4v2JaLuQ
- Configure the document root so that a directory listing is displayed in the browser, rather than an index page.
- Configure this site to respond on both HTTP, and HTTPS standard ports, however all traffic that comes through over HTTP must be redirected to the HTTPS virtual host. Any self-signed certificate will do.
Ensure that the proper content is returned when this site is accessed athttps://site3.104.239.228.184.xip.io and that the traffic is redirected when accessing http://site3.104.239.228.184.xip.io. No content should be returned without proper authentication as mentioned above, and there are no errors in the logs.
Was given 3 hours to finish, and unfortunately I did not. Looks like I have some studying to do
Yeah, that sounds like the site I was on. It's cool, because you can use any tool at your disposal to help you get things done. Google is your friend, lol.
