The Term “Homegrown Violent Extremist” Needs Transparency

  • The Department of Defense has broadened surveillance to encompass a new type of potential, U.S.-based threat but it has not publicly described the criteria it uses to evaluate the threat. According todocuments revealed by Human Rights Watch through a Freedom of Information Request, the Department of Defense can now conduct surveillance of U.S. persons who some in the government refer to as :undefined:“:undefined:homegrown violent extremists.:undefined:”:undefined:

    But the absence of clear and publicly articulated guidelines about this new surveillance category raises concerns for abuse:undefined:—:undefined:concerns exacerbated by the Defense Department:undefined:’:undefined:s opaque, multi-armed surveillance regime that already allows little room for oversight.

    The Air Force Office of Special Investigations, in a revealedslide deck presentation, calls this new type of monitored person a :undefined:“:undefined:homegrown violent extremist,:undefined:”:undefined: or HVE for short. Two examples of events caused by :undefined:“:undefined:homegrown violent extremists:undefined:”:undefined: are given: the shootings in San Bernardino, Calif. in 2015, and in Orlando, Fla. the year after.

    The inclusion of so-called HVEs stems from an expansion of the type of :undefined:“:undefined:counterintelligence:undefined:”:undefined: surveillance the Department of Defense conducts, as a 2016Department of Defense manual explains. With the change, DoD is now permitted to conduct surveillance of Americans :undefined:“:undefined:reasonably believed to be acting for, or in furtherance of, the goals or objectives of an international terrorist or international terrorist organization, for purposes harmful to the national security of the United States.:undefined:”:undefined:

    Aside from the two examples given, the new interpretation:undefined:—:undefined:and the corresponding slide deck:undefined:—:undefined:offer little insight into how an individual is designated an HVE and what type of legal process the DoD uses to conduct that surveillance. Human Rights Watch pressed the Department of Defense for clarity:

    :undefined:“:undefined:As an example of :undefined:‘:undefined:homegrown violent extremists,:undefined:’:undefined: the Defense Department official who commented to Human Rights Watch pointed to individuals who :undefined:‘:undefined:may be self-radicalized via the internet, social media, etc., and then plan or execute terrorist acts in furtherance of the ideology or goals of a foreign terrorist group.:undefined:’:undefined: However, the official did not respond to a question about the criteria the executive branch uses when designating a U.S. person a :undefined:‘:undefined:homegrown violent extremist:undefined:’:undefined: for the purposes of this policy.:undefined:”:undefined:

    Human Rights Watch:undefined:’:undefined:s attempt to understand :undefined:“:undefined:homegrown violent extremists:undefined:”:undefined: classification was met with stonewalling. We need answers to these questions.

    We do not know how U.S. persons are identified as :undefined:“:undefined:homegrown violent extremists.:undefined:”:undefined: We do not know, once identified as HVEs, what type of surveillance DoD believes is permitted, or how the data it collects is used. We do not know if a journalist researching international terrorism could be monitored; or if Twitter users who unwittingly retweet propaganda could be monitored.

    We understand the safety concerns. Yes, international terrorist organizations can now create online propaganda that can influence a U.S. person into sympathy, support, and even violence. But we also need a clear understanding of how DoD makes a determination that someone is or has become an :undefined:“:undefined:HVE.:undefined:”:undefined: A policy where innocent users are swept up in DoD surveillance, simply for clicking the wrong link, or viewing or sharing the wrong content online, is unacceptable.

    Expanding this type of surveillance specifically to DoD is new, and we need to understand more. A new agency means different rules, different protocols and potentially different legal standards for approval. This morass should be cleared.

    Surveillance regimes, as the government has built them, are obscured from public view. The government:undefined:’:undefined:s unwillingness to discuss this expanded surveillance again leaves us in the dark, unable to fully understand and unequipped to question.

    We demand something simple:undefined:—:undefined:more transparency.

    To learn more about one of the government:undefined:’:undefined:s most powerful surveillance authorities, read about Section 702here. To tell your representatives that you won:undefined:’:undefined:t accept government agents going through your emails without a warrant,go here.


  • Make ISO from DVD

    In this case I had an OS install disk which was required to be on a virtual node with no optical drive, so I needed to transfer an image to the server to create a VM

    Find out which device the DVD is:



    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 464.8G 0 part ├─centos-root 253:0 0 50G 0 lvm / ├─centos-swap 253:1 0 11.8G 0 lvm [SWAP] └─centos-home 253:2 0 403G 0 lvm /home sdb 8:16 1 14.5G 0 disk /mnt sr0 11:0 1 4.1G 0 rom /run/media/rick/CCSA_X64FRE_EN-US_DV5

    Therefore /dev/sr0 is the location , or disk to be made into an ISO

    I prefer simplicity, and sometimes deal with the fallout after the fact, however Ive repeated this countless times with success.

    dd if=/dev/sr0 of=win10.iso

    Where if=Input file and of=output file

    I chill out and do something else while the image is being copied/created, and the final output:

    8555456+0 records in 8555456+0 records out 4380393472 bytes (4.4 GB) copied, 331.937 s, 13.2 MB/s


    read more
  • Recreate postrgresql database template encode to ASCII

    UPDATE pg_database SET datistemplate = FALSE WHERE datname = 'template1';

    Now we can drop it:

    DROP DATABASE template1;

    Create database from template0, with a new default encoding:

    CREATE DATABASE template1 WITH TEMPLATE = template0 ENCODING = 'UNICODE'; UPDATE pg_database SET datistemplate = TRUE WHERE datname = 'template1'; \c template1 VACUUM FREEZE;

    read more