made 100 days of code into a collection and separated each day into its own post
This commit is contained in:
parent
2b7aef12b5
commit
6d3baadd5f
11 changed files with 112 additions and 72 deletions
|
@ -1,9 +1,10 @@
|
|||
---
|
||||
layout: post
|
||||
title: "100-days-of-code-challenge"
|
||||
title: "day 1"
|
||||
date: 2018-01-01
|
||||
categories: programming
|
||||
---
|
||||
# 100 Days of Code
|
||||
|
||||
With a brand new year, comes a fresh start, a clean slate. I am going to begin
|
||||
my new year with something I have just come across: [100daysofcode](http://100daysofcode.com/) challenge.
|
||||
|
@ -12,8 +13,9 @@ track my daily progress. It will be fun, and it will be a great way to keep me
|
|||
accountable for building my python knowledge. Here is an example snippet from
|
||||
the code I did for day 1.
|
||||
|
||||
Day 1:
|
||||
```python
|
||||
### Day 1:
|
||||
{% highlight python %}
|
||||
|
||||
def gen_ssh_keypair():
|
||||
""" Generate an RSA private / public keypair """
|
||||
key = RSA.generate(2048)
|
||||
|
@ -27,16 +29,5 @@ def gen_ssh_keypair():
|
|||
pubkey.write(key.publickey().exportKey())
|
||||
|
||||
return 0
|
||||
|
||||
```
|
||||
|
||||
Day 2:
|
||||
Today we are going to make a Discord chat bot. Bots have always been interesting to me.
|
||||
Trying to make a computer program behave like a human sounds like a fun
|
||||
challenge, and a great way to play some fun pranks on my friends on Discord.
|
||||
So far, I have sketched up the initial framework in my python program using the
|
||||
discordpy library. I will need to learn more about the following:
|
||||
- asyncio
|
||||
- coroutines
|
||||
These seem to be two main concepts that this library uses, and it will help aid
|
||||
my skills in the future when making programs that focus on performance.
|
||||
|
||||
{% endhighlight %}
|
|
@ -0,0 +1,19 @@
|
|||
---
|
||||
layout: post
|
||||
title: "day 2"
|
||||
date: 2018-01-02
|
||||
categories: programming
|
||||
---
|
||||
# 100 Days of Code
|
||||
|
||||
### Day 2:
|
||||
Today we are going to make a Discord chat bot. Bots have always been
|
||||
interesting to me.
|
||||
Trying to make a computer program behave like a human sounds like a fun
|
||||
challenge, and a great way to play some fun pranks on my friends on Discord.
|
||||
So far, I have sketched up the initial framework in my python program using the
|
||||
discordpy library. I will need to learn more about the following:
|
||||
- asyncio
|
||||
- coroutines
|
||||
These seem to be two main concepts that this library uses, and it will help aid
|
||||
my skills in the future when making programs that focus on performance.
|
|
@ -0,0 +1,17 @@
|
|||
---
|
||||
layout: post
|
||||
title: "day 3"
|
||||
date: 2018-01-03
|
||||
categories: programming
|
||||
---
|
||||
|
||||
# 100 Days of Code
|
||||
|
||||
### Day 3:
|
||||
Today I could not find time to work on the coding aspect of the bot, but I did
|
||||
grab some audio recordings that I need for the bot. I am mainly making this bot
|
||||
to prank my friends in discord with voice recordings of funny moments that
|
||||
occur in discord. I am going to make it queryable via prepending commands with
|
||||
a !. I still did get to code today for work. I am working on some stuff in
|
||||
python and I have to write unit tests, so I wrote a test for a couple of
|
||||
functions
|
|
@ -0,0 +1,16 @@
|
|||
---
|
||||
layout: post
|
||||
title: "day 4"
|
||||
date: 2018-01-04
|
||||
categories: programming
|
||||
---
|
||||
|
||||
# 100 Days of Code
|
||||
|
||||
### Day 4:
|
||||
Today I worked on some more unit tests with a program I am building at work. I
|
||||
learned a good deal about unit test calls and the different assert options you
|
||||
can pass. I also looked further into the discord python library and copied some of the
|
||||
example bots into an examples directory in my repo. I will need to experiment
|
||||
further with those and look up more information on asyncio and how to properly
|
||||
use it.
|
11
_100-days-of-code/index.html
Normal file
11
_100-days-of-code/index.html
Normal file
|
@ -0,0 +1,11 @@
|
|||
<!DOCTYPE html>
|
||||
<html>
|
||||
<body>
|
||||
|
||||
{% for item in site.100-days-of-code %}
|
||||
<h2>{{ item.title }}</h2>
|
||||
<p>{{ item.description }}</p>
|
||||
<p><a href="{{ item.url }}">{{ item.title }}</a></p>
|
||||
{% endfor %}
|
||||
</body>
|
||||
</html>
|
|
@ -27,6 +27,9 @@ markdown: kramdown
|
|||
theme: minima
|
||||
plugins:
|
||||
- jekyll-feed
|
||||
collections:
|
||||
100-days-of-code:
|
||||
output: true
|
||||
|
||||
# Exclude from processing.
|
||||
# The following items will not be processed, by default. Create a custom list
|
||||
|
|
|
@ -1,53 +0,0 @@
|
|||
---
|
||||
layout: post
|
||||
title: "100-days-of-code-challenge"
|
||||
date: 2018-01-01
|
||||
categories: programming
|
||||
---
|
||||
|
||||
With a brand new year, comes a fresh start, a clean slate. I am going to begin
|
||||
my new year with something I have just come across: [100daysofcode](http://100daysofcode.com/) challenge.
|
||||
I have forked the 100 days of code repo from github and am using the log to
|
||||
track my daily progress. It will be fun, and it will be a great way to keep me
|
||||
accountable for building my python knowledge. Here is an example snippet from
|
||||
the code I did for day 1.
|
||||
|
||||
### Day 1:
|
||||
{% highlight python %}
|
||||
|
||||
def gen_ssh_keypair():
|
||||
""" Generate an RSA private / public keypair """
|
||||
key = RSA.generate(2048)
|
||||
|
||||
# generate private key - output to file
|
||||
with open('rsa_privkey.pem', 'wb') as privkey:
|
||||
privkey.write(key.exportKey())
|
||||
|
||||
# generate public key - output to file
|
||||
with open('rsa_pubkey.pem', 'wb') as pubkey:
|
||||
pubkey.write(key.publickey().exportKey())
|
||||
|
||||
return 0
|
||||
|
||||
{% endhighlight %}
|
||||
|
||||
|
||||
### Day 2:
|
||||
Today we are going to make a Discord chat bot. Bots have always been interesting to me.
|
||||
Trying to make a computer program behave like a human sounds like a fun
|
||||
challenge, and a great way to play some fun pranks on my friends on Discord.
|
||||
So far, I have sketched up the initial framework in my python program using the
|
||||
discordpy library. I will need to learn more about the following:
|
||||
- asyncio
|
||||
- coroutines
|
||||
These seem to be two main concepts that this library uses, and it will help aid
|
||||
my skills in the future when making programs that focus on performance.
|
||||
|
||||
### Day 3:
|
||||
Today I could not find time to work on the coding aspect of the bot, but I did
|
||||
grab some audio recordings that I need for the bot. I am mainly making this bot
|
||||
to prank my friends in discord with voice recordings of funny moments that
|
||||
occur in discord. I am going to make it queryable via prepending commands with
|
||||
a !. I still did get to code today for work. I am working on some stuff in
|
||||
python and I have to write unit tests, so I wrote a test for a couple of
|
||||
functions
|
|
@ -1,3 +1,9 @@
|
|||
---
|
||||
layout: post
|
||||
title: "security+ notes p1"
|
||||
date: 2017-08-22
|
||||
categories: certifications
|
||||
---
|
||||
# Security Threats and Controls
|
||||
|
||||
## CIA Triade
|
||||
|
@ -6,6 +12,8 @@ Data needs to be the following:
|
|||
- Integrity
|
||||
- Availability
|
||||
|
||||
|
||||
|
||||
## Security Policy Steps
|
||||
- obtain support & committment for policy proposed throughout entire org
|
||||
- analyze risks to security within the org that the policy proposes
|
||||
|
@ -13,10 +21,14 @@ Data needs to be the following:
|
|||
the org to recover from losses
|
||||
- review, test, and update procedures continually. continued compliance.
|
||||
|
||||
|
||||
|
||||
## Security Controls
|
||||
- National Institute of Standards and Technolog (NIST)
|
||||
- Federal Information Processing Standards [(FIPS)](http://csrc.nist.gov/publications/PubsFIPS.html)
|
||||
|
||||
|
||||
|
||||
## Control Types
|
||||
- Fips 200 (Minimum Security Requirements)
|
||||
- security control will belong to 1 of 18 families of classes.
|
||||
|
@ -28,6 +40,8 @@ Data needs to be the following:
|
|||
Communications Protection, System and Information Integrity, Program
|
||||
Management
|
||||
|
||||
|
||||
|
||||
## Physical Security Control Types
|
||||
- Administrative - controls that determine the way people act, including
|
||||
policies, procedures, and guidance.
|
||||
|
@ -46,12 +60,16 @@ Data needs to be the following:
|
|||
function of the system through some other means, such as using data backup or
|
||||
an alternative site.
|
||||
|
||||
|
||||
|
||||
## Access Control and ACL
|
||||
- Identification
|
||||
- Authentication
|
||||
- Authorization
|
||||
- Accounting
|
||||
|
||||
|
||||
|
||||
## Formal Access Control Models
|
||||
- DAC - Discretionary Access Control - The owner is granted full control over
|
||||
the resource, meaning that s/he can modify its ACL to grant rights to others.
|
||||
|
@ -70,6 +88,8 @@ Data needs to be the following:
|
|||
- md5, 128 bits
|
||||
- ripemd-160 - 160 bits
|
||||
|
||||
|
||||
|
||||
## Stream ciphers and block ciphers
|
||||
- 3DES / Triple DES - block cipher - 56 bit key - 64 bit blocks
|
||||
- AES / AES25 - block cipher - 128 bit block size, variable key length
|
||||
|
|
|
@ -1,3 +1,10 @@
|
|||
---
|
||||
layout: post
|
||||
title: "security+ notes p2"
|
||||
date: 2017-08-23
|
||||
categories: certifications
|
||||
---
|
||||
|
||||
## LDAP
|
||||
- everything is done in plaintext
|
||||
- there is a TLS version of it. LDAPS
|
||||
|
|
|
@ -1,3 +1,10 @@
|
|||
---
|
||||
layout: post
|
||||
title: "security+ notes p3"
|
||||
date: 2017-08-24
|
||||
categories: certifications
|
||||
---
|
||||
|
||||
## Host Security
|
||||
- Common Criteria (CC)
|
||||
- Security Target (ST)
|
||||
|
@ -99,5 +106,3 @@ Do you have backups of your backups?
|
|||
- is there an offsite backup solution in place?
|
||||
- make you sure that you are testing backups to make sure you can restore
|
||||
everything from them
|
||||
|
||||
|
||||
|
|
|
@ -9,4 +9,8 @@ title: brendan mcdevitt
|
|||
{% for post in site.posts %}
|
||||
<li><span>{{ post.date | date_to_string }}</span> » <a href="{{ post.url }}">{{ post.title }}</a></li>
|
||||
{% endfor %}
|
||||
</ul>
|
||||
<h1>100 Days of Code</h1>
|
||||
{% for item in site.100-days-of-code %}
|
||||
<li><span>{{ item.date | date_to_string }}</span> » <a href="{{ item.url }}">{{ item.title }}</a></li>
|
||||
{% endfor %}
|
||||
</ul>
|
||||
|
|
Loading…
Add table
Reference in a new issue