shot in the head for saying All Lives Matter

You won't hear this on MSM

The narratives must be protected from the TRUTH!





As Biden famously said recently: "We choose truth over facts!"   

Do you how much un-constitutional horse $hit that which you just said is?
Go buy the gun you want on the black market and Fvck Hawaiian laws.
There I SAID it.
I'd suggest an MP5.
I know a place in Seattle where I can buy one
from a Samoan gang.
Given how Fvcked up our
government has become that
would be a good choice.

I just had to give a lecture to a guy who
had his Felony conviction expunged on how
to buy a gun in Hawaii and realized just how
much horse shit we tolerate.
I'm done with Democrats,
their government, and their cops.

I have a friend that has about 10,000 acres of land
and I can shoot as I please without begging
some Democrat to open up
a shooting range.

Aloha.

I only report the "news."

I leave the commentary to people like you.   

This topic reminds me of the same thing I noticed with Kwanzaa.  As far as I see, it didn't even exist until 1966!

If I were a conspiracy nut, I'd be leaning toward both of these "holidays" being promoted by the SJW academics, greeting card companies and retailers.   

Yay, capitalism!   

any ideas on getting an FTP server on a Linux box? I plan to have a portable SSD drive connected to it. I see that FTP software isn't free? Looking to set it up for a NVR.
Or should I use my 1 disk Synology NAS with a portable HD connected to its USB port. Reason to use the portable HDD on Synology NAS as its only 1 bay and my sensitive docs are on the NAS drive - a WD Red HDD

Pretty much all software is free (open source) if you run Linux.  Not sure what Ad on Google you're looking at for paid FTP SW! Just smile and wave "Good-bye".   

If you already have SSH installed, you may already have SFTP access.  I installed OpenSSH for remote connections via Secure Shell, and the package openssh-sftp-server was also installed.  If not already on your Linux machine, just use your package installer to add it.  If openssh isn't there, then of course that ought the be installed automatically by the package manager since SFTP is a dependency.

I've used ProFTPD and VSFTPD in the past, but can be complicated to configure.  Anything that's complicated usually means (1) you're not likely to need or use all the features provided, and (2) you're unlikely to take the time to properly secure the server against "misuse". 

For a one-person connection need, the SFTP server from OpenSSH works fine.  In fact, if you have SSH already working for remote shell access, try using SFTP from the same client machine to see if it's installed.  The login settings are the same for both SSH and SFTP.  Whether you use trusted keys or login/password authentication, you connect the exact same way.  Makes administration much easier.  You can run the test on that server by executing the sftp command to connect to itself:

sftp localhost
or
sftp user@localhost

If you get prompted for a password, the SFTP server connected.

Here's the info on installing SSH and SFTP on Ubuntu:

https://help.ubuntu.com/community/SSH/OpenSSH/Configuring

The answers in this article offer nice, succinct answers that help configure the OpenSSH SFTP server for added security.

https://askubuntu.com/questions/420652/how-to-setup-a-restricted-sftp-server-on-ubuntu

If you need an FTP client for windows or Mac (or any platform really), I like Filezilla.  Filezilla also offers a Windows FTP server.  BTW, all the Filezilla products are FREE!     The client is easy to use, and it can be configured to store your SSH keys and all connection information. 

An easy way to create and convert SSH keys is with the SSH client "puTTY".  It comes with a key generation utility if you install the right package.  If you are on Windows and ever use SSH, you have to have puTTY.  I think it's a law or something.  Did I mention it's free?   

SSH and SFTP certificates can get confusing when copying between different OS's.  Let me know if you run into trouble.

 

A haven't bought in a couple of years (need to sell to make room!).

I liked Aim Surplus, Classic Firearms, and Gun Broker.  I also bought from Bud's Guns. 

I've not purchased from them yet, but The Mosin Crate often gets some very nice ones in stock, and they get bought out quickly.  Have to be Johnny on the Spot with your order ready to be placed by 10AM EST the day ordering is open for that item.  You get to preview what's available to purchase the day before, so you have time to shop and decide.  Most decent items in limited quantities are sold out just seconds after 10AM!

I put a new list of guns up every couple of weeks on the shop page. I have a "preview day" where no orders are accepted to
give folks a day to view everything without feeling rushed. The next day the items will go up for sale at 10AM EST when I
open and can be ordered at that time.

If you send order in before 10AM on sale day, it will be put behind those that order at correct time of 10AM or later.

https://www.themosincrate.com/shop-1

Can they change the law?

Regardless of any specific law in effect?
Are you serious?

Nothing you quoted says they can circumvent the law.
Where does it say make public?
Which is what the new law and old law are all about.

What happened to
Always playing the shell game

You just want to scream at the sky, Snowflake.

Was that law needed for the Kealoha investigation to become public?  There are ways to make it happen in spite of current laws, such as involving federal jurisdiction.

I'd bet many violations by Cops could be within federal jurisdiction since many involve civil rights violations.

For those that have gone through this process, please clarify this situation:

1.  LG permit expiring in August.
2.  Registration appointment in September.

Can a LG be purchased in July then registered in September with an August expired permit?

Called firearms division but no one seems to be answering.

Yep.  The permit to ACQUIRE is valid in July.  No problem acquiring a long gun.

When you register, apply for a new permit.  Registration doesn't require a valid permit to acquire.

Look at all the out of state guns that come in with new residents and visitors.  Registration is required, but no permits needed.  Acquisition is separate from registration.

Chances are, they will want to keep the expired permit, so take that with you to apply for a new one.  Making you go through a background check when moving or visiting requires a permit registration process.  If you acquired using a valid permit at that time the background check was already performed.

If they give you grief, tell them you'd like to know who to report HPD to for violating the 5 day registration law -- ever since the appointment system started.

This entry is more to document these details for my own reference if/when I need them again later, but perhaps it'll interest anyone who configures web servers.

In order to set up my unRAID docker "Let's Encrypt", which contains the installed Nginx web server for unRAID, as a reverse-proxy for Apache 2.4.x web server running on an Ubuntu VM under the same unRaid OS, I had to read a million (slight exaggeration) posts with a variety of methods to get this to work with the FastCGI, or now PHP-FPM (FastCGI Process Manager).  FPM uses a socket connection between the proxy and the Apache server for PHP script execution, which many websites are almost entirely written in.  I normally use Joomla to manage my websites, which is PHP top to bottom.  The webpages the browser sees are not html files.  They are html code generated on the fly by the PHP scripts.  It's impossible for a hacker to monkey with the website if they don't have access to the PHP web repository and/or the database where the actual content is stored.    

So, I upgraded my original PHP version from 7.0 to 7.3, and also added 7.4 for testing.  In order to select the default/active version of PHP, I wrote a script (posted at the end).  It calls an interactive Linux utility from which to select a version, and then it runs the commands to not only activate that PHP version, but it also disables the previous version's config files and enables the new version's configs.  This is helpful, since some of the configuration directives contain versions, too.

The basic steps to get FPM to work are:
On the Nginx system/docker, locate the directory where website config files are stored.  For me, it's on a cache drive under <cache dir>/appdata/letsencrypt/nginx/site-confs.

If not already there, create one or more files for each virtual website you want to host on Apache.

My config file for one domain looks like:

server {
        listen 80;
        listen [::]:80;
        server_name mydomain.com;
        return 301 https://$host$request_uri;
}

server {
        listen 443 ssl http2;

        server_name mydomain.com;

        include /config/nginx/ssl.conf;
        include /config/nginx/proxy.conf;

        location / {
           proxy_pass "https://10.0.1.220:447";
        }
}

The name "mydomain.com" would be registered with a domain name registrar if this is for public access.  Or, for testing/in-house-access-only, you can add the name to your internal DNS or hosts files for each computer being used as a client.  As long as you have a unique name, and it can be resolved to THE PROXY'S IP ADDRESS, you should be good.

Once the proxy gets a request, if it was sent over unsecured HTTP (port 80), it does a permanent redirect (301) to the more secure HTTPS (port 443).  That allows clients to request connections to port 80 without problems, but the connection will be replaced with the better port 443.

The last directive in the 443 block says to proxy the request, sending it to the upstream Apache web server at IP address 10.0.1.220, which is obviously a private IP address.  The port, 447, is configured on the Apache server as a substitution for 443, just to avoid conflicts with other services like NextCloud which by default needs port 443.

Create one file for every virtual server you want to proxy, and just change the ServerName to match that site's domain name on 2 lines.  Super simple.   

Now, for Apache.  You need to install apache2 (of course) and at a minimum the modules listed:

For FPM to work, you have to add:
libapache2-mod-php
libapache2-mod-fcgid
php
php-fpm
php-cli

Other modules will be loaded by default which are needed, but these are the ones to make sure are installed other than those.

Once installation is done, restart the Apache webserver and the PHP-FPM processes:

systemctl start apache2
systemctl start php7.2-fpm

If already running, use "restart" instead of "start".

Many examples/tutorials online say to place the code for FPM in each individual virtual host's config file, but that, to me, invites more work to maintain.  Since I intend to use PHP for most, if not all, of my virtual hosts, I want to make the change in one place that works for all sites.  The kicker to either approach is, if you ever want to change PHP versions, you'd have to remember to manually update the version for the socket being used.  Instead, I use the included functionality that lets me create separate config files per PHP version, and then issuing commands to disable the previous version's file, and enable the new one.  For example:

a2disconf php7.4-fpm
a2enconf php7.3-fpm

That requires a file of each name above to be in the confs-available directory:  /etc/apache2/confs-available/php7.3-fpm & /etc/apache2/confs-available/php7.4-fpm,

When you run the commands above, a2disconf removes the named linked file from the confs-enabled directoy, and a2enconfs creates a link to the file in confs-available.  One place to create/update the config files, and 2 commands to disable and enable the files you want active.  Now I can have sockets named for the PHP versions in each file, and only one is active at a time.

In each file listed above (php7.x-fpm), add these lines at the bottom outside of any other tags:

    <FilesMatch ".+\.ph(ar|p|tml)$">
        SetHandler "proxy:unix:/run/php/php7.3-fpm.sock|fcgi://localhost"
    </FilesMatch>

The version in the "SetHandler" line should obviously match the filename's version identifier. 

That's it!  If you are only interested in one version of PHP, then you can place these updates in one of several files and it will work.  This method adds the ability to change versions as needed without a lot of work.

And, in order to easily switch PHP versions, I created a bash script to run on ubuntu Linux: 

Filename:  php_version_select.sh

!#/bin/bash
#Get currently configured PHP default version:

currver=`php -v | grep '^PHP' | awk '{print substr($0,5,3)}'`

echo ""
echo "PHP Version Selector"
echo "--------------------"
echo "Currently selected version: $currver"
update-alternatives --config php

newver=`php -v | grep '^PHP' | awk '{print substr($0,5,3)}'`

if [[ $newver = $currver ]]
then
   echo ""
   echo "Keeping $currver"
   echo ""
else
   echo ""
   echo "Switching to $newver ..."
   echo ""
   a2dismod php$currver
   a2disconf php${currver}-fpm.conf
   a2enmod  php$newver
   a2enconf php${newver}-fpm.conf
   update-alternatives --set phar /usr/bin/phar$newver
   update-alternatives --set phar.phar /usr/bin/phar.phar$newver
   echo ""
   echo "Restarting Apache and FPM Services ..."
   systemctl restart apache2
   systemctl stop php${currver}-fpm
   systemctl start php${newver}-fpm
   echo ""
   echo "done"
fi
# Display php version output

php -v

echo ""
echo "Script complete."

If you select a different PHP version, the script sets that as well as doing all the module and configuration disable/enable requirements.  At the end, it restarts the Apache Server and FPM processes to make the changes active.

So much simpler when I see it boiled down to this list.  All the other online versions were a hodgepodge of these and many other steps, but none in enough detail to explain WHY you are following each step.

The greatest benefit of computers is there is always another way to do everything.

The greatest downside of computers is there are so many ways to do things, it's difficult to find the one that's best for your case.

 

You can also do TOR browser in a Linux environment.
All real pirates do.

Stop giving away our secrets!!

Uh ... I mean ... really?      

Thanks, I was looking through the registrations I have, and they didn't match the three types listed on the 4473 (Handgun, Long Gun, Other Firearm)

I have:

Pistol
Pistol Receiver
Rifle
Rifle Receiver
Receiver

Sometime between getting my first gun in HI (2012) and a few years ago, the ATF added "frame or receiver" to the "other" category.  The current online form at the ATF site shows a revision date of October 2016.  Adding the "marijuana use" warning was part of the 2016 revision, I know.

Prior to that, FFLs had to mark Long Gun or Handgun for receivers -- no category existed that called out "receiver".

Since the FFL only fills out one 4473 per transaction, they'll check as many boxes as appropriate for the firearms in that purchase.  So, even now, you might get the boxes "Long Gun" and "Other" checked if you buy an AR15 and a stripped AR receiver at the same time.

As I do some research:

The 2005 form only had Handgun, Long Gun and Both.   So, if the FFL checked the box next to "Rifle" -- because an AR receiver is built as a rifle in most cases -- you could not make it into a pistol.  Now -- the "Other" box is all they need to check for a receiver-only transfer.

https://www.ocshooters.com/Gen/Form-4473/ATF-Form-4473.htm

This article is about AOWs, but it details the classification issue quite well.

https://www.thefirearmblog.com/blog/2016/10/18/aow/