<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:blogger='http://schemas.google.com/blogger/2008' xmlns:georss='http://www.georss.org/georss' xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-9175444989789525666</id><updated>2024-10-11T18:19:28.310-06:00</updated><category term="2 factor auth"/><category term="bizdev"/><category term="google authenticator"/><category term="kingphisher"/><category term="linux"/><category term="pam"/><category term="phishing"/><category term="rpm"/><category term="sales"/><category term="security"/><category term="ssh"/><category term="ssh keys"/><category term="training"/><category term="ubuntu 14.04"/><title type='text'>At the Intersection of Security and Technology</title><subtitle type='html'>A place to learn more about security and technology.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://blog.bjtaylor.net/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9175444989789525666/posts/default?redirect=false'/><link rel='alternate' type='text/html' href='http://blog.bjtaylor.net/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>BJ</name><uri>http://www.blogger.com/profile/08849027700769508769</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>5</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-9175444989789525666.post-6233751662451465704</id><published>2017-04-30T21:12:00.000-06:00</published><updated>2017-04-30T21:31:42.934-06:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="bizdev"/><category scheme="http://www.blogger.com/atom/ns#" term="sales"/><title type='text'>An Open Letter to My Friends in Sales and Biz Dev</title><summary type="text">

To my Friends in Sales:



I get a lot of sales calls, and I don&#39;t mind it, but it means that I&#39;ve got to keep them quick or they quickly take up too much time. So I created this list of tips for you so we can make the best of your time and mine:


I will ask questions on the introductory call about features and prices. Please be ready to answer those. I want that information so I can decide if</summary><link rel='replies' type='application/atom+xml' href='http://blog.bjtaylor.net/feeds/6233751662451465704/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://blog.bjtaylor.net/2017/04/an-open-letter-to-my-friends-in-sales.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9175444989789525666/posts/default/6233751662451465704'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9175444989789525666/posts/default/6233751662451465704'/><link rel='alternate' type='text/html' href='http://blog.bjtaylor.net/2017/04/an-open-letter-to-my-friends-in-sales.html' title='An Open Letter to My Friends in Sales and Biz Dev'/><author><name>BJ</name><uri>http://www.blogger.com/profile/08849027700769508769</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjmF3Ha8yuCDQNxC0AhDjF4WCCu5EQiUOnr0pGzTBgRgNxbCe6pB8Fwnc_sLlflOdnLGOg1k9QXTdL2bYDH2s0MXRjwQnTDG8Xl9FE8e0GF5uD0WHOk26zwZpNlPQ8G8qrKByBaAMiBT_E/s72-c/old-telephone.jpg" height="72" width="72"/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9175444989789525666.post-9176260230825653881</id><published>2017-04-17T22:36:00.000-06:00</published><updated>2017-04-18T10:53:29.881-06:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="kingphisher"/><category scheme="http://www.blogger.com/atom/ns#" term="phishing"/><category scheme="http://www.blogger.com/atom/ns#" term="security"/><category scheme="http://www.blogger.com/atom/ns#" term="training"/><title type='text'>Strengthening the Weakest Link </title><summary type="text">
Employees are frequently cited as being the weakest link in security. Rather than argue this point, I&#39;m just going to reference a few articles here and move on (Fortune, Fraud-magazine, Forbes). Now, in general, employees are considered the weakest link because they don&#39;t always make smart decisions.




For example, in one company I was at, a phishing email was sent out to many of the employees</summary><link rel='replies' type='application/atom+xml' href='http://blog.bjtaylor.net/feeds/9176260230825653881/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://blog.bjtaylor.net/2017/04/strengthening-weakest-link.html#comment-form' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9175444989789525666/posts/default/9176260230825653881'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9175444989789525666/posts/default/9176260230825653881'/><link rel='alternate' type='text/html' href='http://blog.bjtaylor.net/2017/04/strengthening-weakest-link.html' title='Strengthening the Weakest Link '/><author><name>BJ</name><uri>http://www.blogger.com/profile/08849027700769508769</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEheJszeBvUlnBzYeRwTkWV2TMTi9SCgl5bv_XCGg6Hx-Eaziv71ofoaf5ecxt1FM4KXrZWbiaJErY6Lrs0cXV0oDojZTanl8EBbn7LcY7T7CC6PUlMLf0JcaFhk9rGc3eCZpMIv-V3gFPk/s72-c/phishing.jpg" height="72" width="72"/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9175444989789525666.post-5720532222491986170</id><published>2017-04-17T19:24:00.000-06:00</published><updated>2017-04-17T19:24:18.902-06:00</updated><title type='text'>Helping our Children to Succeed in this New Digital World</title><summary type="text">
I was asked by Code.LikeAGirl.io to write an article for them about my time teaching kids how to code. If you&#39;d like to read it, you can see it here.


I was in 6th grade, and we were brought into the computer lab for our last lesson in coding. On the screen blinked a green cursor in one section of a screen, and there was a solid green triangle in the other. About two dozen children anxiously </summary><link rel='replies' type='application/atom+xml' href='http://blog.bjtaylor.net/feeds/5720532222491986170/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://blog.bjtaylor.net/2017/04/helping-our-children-to-succeed-in-this.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9175444989789525666/posts/default/5720532222491986170'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9175444989789525666/posts/default/5720532222491986170'/><link rel='alternate' type='text/html' href='http://blog.bjtaylor.net/2017/04/helping-our-children-to-succeed-in-this.html' title='Helping our Children to Succeed in this New Digital World'/><author><name>BJ</name><uri>http://www.blogger.com/profile/08849027700769508769</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9175444989789525666.post-7685808012023467692</id><published>2015-02-20T10:15:00.000-07:00</published><updated>2017-04-17T16:23:34.598-06:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="2 factor auth"/><category scheme="http://www.blogger.com/atom/ns#" term="google authenticator"/><category scheme="http://www.blogger.com/atom/ns#" term="pam"/><category scheme="http://www.blogger.com/atom/ns#" term="ssh"/><category scheme="http://www.blogger.com/atom/ns#" term="ssh keys"/><category scheme="http://www.blogger.com/atom/ns#" term="ubuntu 14.04"/><title type='text'>Remote two-factor authentication, with ssh public keys, and google authenticator</title><summary type="text">
Installing and using the Google Authenticator was pretty easy. I give credit to howtogeek.com&amp;nbsp;for their straight forward instructions on using it. However, I wanted to change some things about their setup. You&#39;ll find my instructions to be similar to theirs, but with some important differences. This was done on Ubuntu 14.04.

Install the google auth pam module:

sudo apt-get install </summary><link rel='replies' type='application/atom+xml' href='http://blog.bjtaylor.net/feeds/7685808012023467692/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://blog.bjtaylor.net/2015/02/remote-two-factor-authentication-with.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9175444989789525666/posts/default/7685808012023467692'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9175444989789525666/posts/default/7685808012023467692'/><link rel='alternate' type='text/html' href='http://blog.bjtaylor.net/2015/02/remote-two-factor-authentication-with.html' title='Remote two-factor authentication, with ssh public keys, and google authenticator'/><author><name>BJ</name><uri>http://www.blogger.com/profile/08849027700769508769</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9175444989789525666.post-8877694828660807656</id><published>2009-05-19T16:13:00.001-06:00</published><updated>2017-04-17T16:52:52.840-06:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="linux"/><category scheme="http://www.blogger.com/atom/ns#" term="rpm"/><title type='text'>Which rpm did this file come from?</title><summary type="text">
Need to know what rpm a certain file came from?  Sometimes I want a certain program on one machine that I have on another, and my rpm searches come up blank.  This happened with a program that I needed called lockfile, that I couldn&#39;t figure out how to install.  It ended up being in the procmail-3.22-203.1 rpm.

The command I used was this:

rpm -qf /usr/bin/lockfile

I found that tip here:
http</summary><link rel='replies' type='application/atom+xml' href='http://blog.bjtaylor.net/feeds/8877694828660807656/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://blog.bjtaylor.net/2009/05/which-rpm-did-this-file-come-from.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9175444989789525666/posts/default/8877694828660807656'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9175444989789525666/posts/default/8877694828660807656'/><link rel='alternate' type='text/html' href='http://blog.bjtaylor.net/2009/05/which-rpm-did-this-file-come-from.html' title='Which rpm did this file come from?'/><author><name>BJ</name><uri>http://www.blogger.com/profile/08849027700769508769</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>