Common Internet File System (CIFS) – Windows 10 and Windows 7 – Accessing SMB1 Using Anonymous (guest) Account

Tuesday, January 28th, 2020

Common Internet File System (CIFS) – Login Using Anonymous (Guest) Account to Network Shares & NAS Systems

Windows 7:

To map and connect to a network share that is using the SMB1 protocol in Windows, there are a few things that you need to do depending on which version of Windows you use.  In Windows 7, it should be pretty easy.  When mapping the network drive, be sure to check the "Connect using different credentials" box.  For the login, use "anonymous".  Leave the password field blank (don't provide a password).

Windows 10:

Windows 10 doesn't support the SMB1 protocol by default.  However, it can be enabled.  To enable SMB1 support, go to the Control Panel, click on "Programs and Features", and then click on the "Turn Windows features on or off" link in the left sidebar.  Under the "SMB 1.0" category, enable the "SMB 1.0/CIFS Client" by clicking the checkbox and making sure it's in a checked state.  Uncheck the "SMB 1.0/CIFS Automatic Removal" entry if it's enabled as it will cause anonymous logins to SMB1.0 shares to fail.

The next step is to configure Windows 10 to allow anonymous logins to network shares.

To enable access under the guest account from your computer, you need to use the Group Policy Editor (gpedit.msc). Go to the section: Computer Configuration -> Administrative templates -> Network -> Lanman Workstation. Find and enable the policy "Enable insecure guest logons". These policy settings determine whether the SMB client will allow the guest logon to the SMB server.

More Detailed Guide | Archived Copy

Windows 7 and 10:

If you get a message that a drive is already mapped using different credentials, simply map the connection using its IP address instead rather than its name. 

Allow Anonymous Read Only FTP via VSFTPD

Saturday, January 3rd, 2015

Anonymous VSFTPD Setup (Read Only)

Configuration:

In order to enable anonymous FTP connections to a particular directory while still supporting authentication for virtual users for their files via PAM isn't that difficult.  Install VSFTPD if you haven't done so already by running the following command:

sudo apt-get install vsftpd

Create a backup of your existing VSFTPD confiugration file (this guide assumes you have already installed vsftpd):

sudo cp /etc/vsftpd.conf /etc/vsftpd.conf.bak

Next, let's edit the file:

sudo nano /etc/vsftpd.conf

Add the following lines to your configuration file:

anonymous_enable=YES
anon_root={INSERT_PATH_TO_ANONYMOUS_DIRECTORY}
anon_mkdir_write_enable=NO
anon_upload_enable=NO

Adding these lines enables anonymous FTP to the specified directory where files can be read and downloaded only.  Anonymous users cannot write, delete, change, or modify files because of the anon_mkdir_write_enable=NO and the anon_upload_enable=NO configuration lines.  For your changes to take effect, restart vsftpd.

sudo service vsftpd restart

You're done!

The Monsanto Protection Act – “Farmer Assurance Provision, Section 735” – Promotes the Growth and Engineering of GMO Foods and Seeds Without Any Judicial Oversight or Regulation

Tuesday, April 9th, 2013

The Monsanto Protection Act & What It Means For YOU

"Free from Any Judicial Litigation" – WAIT WHAT?!?!?!

The “Farmer Assurance Provision, Section 735”, known as the Monsanto Protection Act, is a provision that was slipped into the "Continuing Resolution" spending bill.  This spending bill is designed to prevent the government shutdown and sequester.  The Continuing Resolution bill, including the Farmer Assurance Provision, passed the house and was signed by President Obama on March 29, 2013.  A sub-committee slipped the provision into the bill anonymously.  However, news has spread that Missouri Sen. Roy Blunt (R) drafted the provision in direct conjunction with Monsanto.  His reasoning for supporting such a provision: "it is only a one-year protection.”

So, What Does this Do?

In short, the Farmer Assurance Provision, Section 735 "allows agribusiness giant Monsanto to promote and plant genetically modified organisms (GMOs) and genetically engineered (GE) seeds, free from any judicial litigation that might decide the crops are unsafe".

It stipulates that the U.S. Department of Agriculture (USDA) “ignore any court ruling that would otherwise halt the planting of new genetically-engineered crops.”  Typically, the USDA approves GMO products and seeds as long as they pass certain filing regulations and conditions.  Unfortunately, the USDA does not conduct thorough reviews or tests of the many submitted food products it receives.  To speed up the process, the USDA typically approves products without performing tests that study long term effects.

Tests of these controversial products are usually performed much later by independent groups.  Some are sponsored by Monsanto and conclude that these products are safe.  Others are sanctioned by independent groups funded by "the people" who are protecting their health interests.  Typically, results from studies not financed by Monsanto show that GMO products can increase the risk of cancer and cause adverse health issues.

GE and GMOs can damage the environment and introduce additional pesticides into the food supply endangering the health of all consumers.  The unfortunate truth is that 80% of the food supply is already contaminated by GMOs.  The effects to our health are unknown.  

Do you really want to be a guinea pig?

What can we do?

Fight this by mandating the labeling of GMO products on food labels:

http://justlabelit.org/

Spread the news on Facebook.  

Read these articles to find out why GMOs and GE seeds are bad for you, your neighbors, and the environment.

http://www.100daysofrealfood.com/2013/04/02/gmos-monsanto-protection-act/
http://www.safe-food.org/-issue/dangers.html
http://www.organicconsumers.org/ge/ge_vs_organic.cfm
http://www.organicauthority.com/foodie-buzz/eight-reasons-gmos-are-bad-for-you.html
http://www.badseed.info/
http://dailybail.com/home/jon-stewart-exposes-the-monsanto-protection-act.html

Main Sources:

http://www.workers.org/2013/04/07/monsanto-protection-act-chemical-monopoly-writes-its-own-law/
http://dailybail.com/home/jon-stewart-exposes-the-monsanto-protection-act.html