This is, by design, an informational resource. However, due to various reasons, including the large amount of variations to technology that may exist, no guarantees are made towards the accuracy of any information provided. Also, no legal warranties are made. All information is provided without the provider of the information claiming any responsibility about potential or existing risks and/or problems that may occur from acts such as creating, compiling, or sharing such information. Recipients of such inforamation must not attempt to have site staff (including any owners) be responsible for any negative consequences from determining how information is applied. Further legal information is on CyberPillar website's Copyright page (which mentions Copyright, but also has other information related to law).

[#mainpghi]:

Introduction

Welcome. If you are a new visitor wanting to know what all the hubbub is about, here's the brief synopsis: In short, ][Cyber Pillar][ intends to be a technical resource of information and to be sufficient for two tasks: helping people troubleshoot technical setups, and to provide guides for things such as setting up an IPv6 network of machines (that may be physical machines and/or partially/mostly virtual machines) using multiple possible software solutions. This provides people with performable tasks once an operating system is set up, and allows one to more easily implement a new technology or switch from one implementation to another.

It is critical that people be aware of some of the dangers that may exist. Know that while this website strives to help people, this site offers no warranties or positive guarantees that everything will work well when following even the best of instructions. The disclaimer near the top of this page (before the introduction) is important to understand. A technology warning is not just provided to help give legal protection to any owners of this website, but also because AN EXPECTATION IS THAT PEOPLE WILL LOSE DATA WHEN USING INFORMATION FROM THIS SITE! (This does not mean that all people following instructions will experience data loss, but some may. Hopefully the site will allow even more data may be successfully saved, by being recovered or never-lost in the first place, and hopefully security will be enhanced by following recommendations on this site. However, although there may be some net gain, there may be cases of loss as well. Hopefully warnings are heeded.

To see recommended resources on this site, check out the Recommendations section on the site's introduction page.

To reduce overall scrolling for repeat visitors, this page starts out by first having a section for the latest notices/announcements/news for those who regularly visit the site.

[#sitenews]:

Notices/Announcements/News

A section dedicated to Site News has been created to provide an area to review recent announced changes to the site. The section also discusses any anticipated upcoming changes that may be of interest to people wanting to monitor the development of ][Cyber Pillar][.

Meanwhile, if there are any particularly major announcements, they may be made here (on the main page).

Major highlights of more recently posted announcements

Public accessability

This website has been made publicly accessible, starting prior to the end of the Year 2012 (at least in most time zones of the creator/founder's resident nation, which is The United States of America, including the Pacific Time Zone where the site was launched).

[#sitearea]:

Site Areas

Glossary
A reference containing a large number of technical terms and their abbreviations.
[#keylegnd]: Key/Legend
Information about example addresses used on this site, and the meaning behind some styles used on the site. If there is a style being used, this page may provide a description of what is conveyed by the choice in style being used.
[#tutorial]: Tutorial Area
Looking for a tutorial/guide to set things up? Check out this area. For those seeking a guide to cover each of the steps, be familiar with the concepts noted in the Basics section and then proceed to follow one of the guides in this Tutorial Area. The tutorial(s) in this section may make heavy reference to the Technologies, Techniques, and Technicians' Technical Details section.
[#techns]: Techn's Section: Technologies, Techniques, and Technicians' Technical Details

The techn's terms in this section refer to the following when they are being used as part of the title of this section:

Technologies
This includes things such as software protocols
Techniques
Information about how to set up one or more popular implementations of the technologies. The information here is likely to be fairly simple (or as simple as possible): More complex configurations may be discussed in other sections like the Tutorial Area.
Technicians' Technical Details
Other information which may be useful for a technician, such as the startup process of computer systems

The terms that this section was named after are not necessarily meant to be separate sub-sections of this section.

In essense, this is meant to be an information dump which can be referenced (due to having many hyperlinks), and which references a lot of authoritative material, and which references itself. If you're wanting to know how something specific works, this may be your best bet. If you're looking for a guide on how to complete a process, be sure to check out the tutorial area.

Software

Information about various implementations of various types of software, such as the Operating Systems section which lists operating systems and references further details such as operating system home pages, requirements, logos/mascots, and installation guides.

If seeking software to run within an operating system, check out the list of packages which may be used with a package manager. For software designed to run directly under DOS-compatible operating systems including MS-DOS, 16-bit and 32-bit Windows, and OS/2, also see TOOGAM's software archive. (That site may also have software for newer versions of Windows and a small amount of software for other operating systems such as the those designed for Apple Macintosh platforms.)

[#tasks]: Tasks
Details about performing some specific tasks, such as performing audits, choosing certifications to pursue, and other moves one may make in a professional career. Information about hardening systems or making money might go in this section. Actually, some of what is just mentioned may go into another section, like providing services professionally.
[#provserv]: Providing Professional Services
Information about how to provide the technologies as sellable services. This has a bit of a financial focus: how to decide what to do that would help an organization/business/etc., how to make such an offering seem appealing, and how to implement such things. Includes information about some various careers for which people are commonly needed in order to fulfill common technical needs, implementing ways to make money, etc.
[#helpout]: Helping Out
Network administrators: Be good!
Don't become a zombie farm: resist attackers

Learn about security.

Always seek how to remain secure.

Review Best Current Practice memo #46: “Recommended Internet Service Provider Security Services and Procedures” (RFC 3013)

Participate in Internet standards
RFC-Ignorant.org

See RFC-Ignorant.org and look in the left frame for the “Listing Policy” pages. Review those and ensure full compliance.

This may be a bit controversial: If running a mail server, consider using the RFC-Ignorant.org Delivery Status Notification (Registered Black List).

Help ][Cyber Pillar][

Help ][Cyber Pillar][ today!

Okay, so, admittedly, this was a little selfish to be putting this request before some of the remaining generalized hints.

Please help.

Providing money
Pay for the products you use
Pay for free software/services
  • e.g.: If using JP Software's Take Command Console Limited Edition, pay for a full version of Take Command.
  • e.g., if any free protection software such as SuperANTISpyware Free helped, and if there is a paid version available, show some appreciation by paying for the paid-for version.
Donate to open source projects

As some examples:

Operating Systems
OpenBSD
OpenSSH

This is one of the more well-known projects by the OpenBSD team. Please see the section about donating to the people behind the OpenBSD operating system.

Perhaps free Anti-Virus solutions?
ClamAV?
...
e.g. Perhaps ClamWin?
...
e.g. Perhaps Clam Sentinel?
...
e.g. Perhaps websites?
e.g. ][Cyber Pillar][

Donation information is not currently available. For other ways to help, see: Help ][Cyber Pillar][ today!

e.g. perhaps the OpenBSD Journal @ Undeadly.org?
Just an example that was thought of... Actually, the upper-right corner mentions donating to OpenBSD.
Wikimedia
Donating to the Wikimedia Foundation helps out the organization behind their most famous website, Wikipedia.
Wayback machine
You may wish to Donate to the Wayback Machine Internet Archive @ archive.org
Pay for related projects
e.g.: Need tunnels? Like devio.us? Use the sister project, tunnelr.com
Helping to raise money

Start a fundraiser. Host a booth at a convention.

Help software development

Many people think that they may need to have some really serious computer programming skills to even think about helping with software development. Nay, this is not so.

Submit feeedback

The biggest thing to do is to submit feedback. A very easy and automated way may be to participate in automatic error reporting programs. Other data gathering programs might be less useful, though certainly an organization running such a program would encourage participation.

Software development
Those with talent, use it. Realize that starting your own project may be good for self-educational purposes, but often a more useful way to help out is to find an existing project, and see whether it is worthwhile, and if it may be helped. If the project is poorly implemented, then perhaps find another implementation. If there is none, then starting your own project may be a most helpful endeaver, if the new project ends up being any better than other implementations.
Testing

OpenBSD's guide to ports testing describes some steps that may be taken. This may involve spending some time, and may require some resources such as disk space. Those who can help, and are also willing to, please do.

Documentation

See a program that lacks documentation? Or, worse yet, has documentation which is misleading? Contact the people running the project and try to get involved.

User support

If people are asking questions on a forum, and you have an answer, and you have time to register on the forum so that you may post, then help out.

Here are some known requests:

OpenBSD

Another thoughts/ideas:

[#reallife]: Information other than just that which is directly related to using computers
See also Entertainment software.
[#thissite]: This site
Information about people familiar with the site and interested in knowing what the plans are for the site.
[#sites]: Sites
Information about other web sites, including announcements of security vulnerabilities, computer/technology-related news, etc.
[#interact]: Contact/Interaction

Contact information, community details, etc.

Page comments
This is not yet implemented at the time of this writing. The idea here is that pages will have a comments section. Helpers, such as staff members, may review the oldest comments that haven't yet been addressed (by reviewing a web page that lists where the most recent unaddressed comments were posted). Comments about a page's text, or requests for assistance about a topic related to that text, may then be addressed. (Requests for assistance may be addressed by providing the answer, or posting a hyperlink to a forum post.)
Forums
Info may be forthcoming
Request for technical assistance

When making a request, please provide a hyperlink to the section of the site which was reviewed. This helps to ensure that the person requesting the information has spent the time needed to locate that information, and also helps the assister to be able to quickly jump to the relevant information.

See sections about page comments, and forums. In some cases, perhaps it would be most appropriate to contact staff members who wrote the text of the web page.

Assisting with the web site
Current specific requests
Assistance with forums...
Errors
Cyber Pillar does not want to be having these. Help stomp them out.
Verification
Help the website by verifying details. As a side benefit, this often involves going through various steps which may provide experience and/or education as well.
Deeper assistance
Partnering with CyberPillar
Submitting new content
Translating Content
Staff contact information
Information on contacting staff member(s)
[#sitemap]: Site Map
A listing to many of the pages on the site. Those who prefer not to traverse the hierarchy in a more manual fashion.