Debian -- Details of package bitcoin-qt in sid

Whonix lead developer wants to maintain a debian repository for the Monero GUI for two years. Comment on the proposal!

Whonix lead developer wants to maintain a debian repository for the Monero GUI for two years. Comment on the proposal! submitted by Rehrar to Monero [link] [comments]

Delightful Privacy

Delightful Privacy delightful

This is a collection of software, operating systems, and other miscellaneous tools to help the average user fight for their privacy and security online.

Operating Systems

Fedora

Fedora uses Security-Enhanced Linux by default, which implements a variety of security policies, including mandatory access controls, which Fedora adopted early on. Fedora provides a hardening wrapper, and does hardening for all of its packages by using compiler features such as position-independent executable (PIE). Wikipedia

Pop!_OS

Pop!_OS provides full out-of-the-box support for both AMD and Nvidia GPUs. It is regarded as an easy distribution to set-up for gaming, mainly due to its built-in GPU support. Pop!_OS provides default disk encryption, streamlined window and workspace management, keyboard shortcuts for navigation as well as built in power management profiles. The latest releases also have packages that allow for easy setup for TensorFlow and CUDA. Wikipedia

Debian

Debian is one of the oldest operating systems based on the Linux kernel. The project is coordinated over the Internet by a team of volunteers guided by the Debian Project Leader and three foundational documents: the Debian Social Contract, the Debian Constitution, and the Debian Free Software Guidelines. New distributions are updated continually, and the next candidate is released after a time-based freeze. Wikipedia

openSUSE Tumbleweed - Rolling Release!

Any user who wishes to have the newest packages that include, but are not limited to, the Linux Kernel, SAMBA, git, desktops, office applications and many other packages, will want Tumbleweed. openSUSE

For enhanced security

Qubes OS

Qubes OS is a security-focused desktop operating system that aims to provide security through isolation. Virtualization is performed by Xen, and user environments can be based on Fedora, Debian, Whonix, and Microsoft Windows, among other operating systems. Wikipedia

Tails

Tails, or The Amnesic Incognito Live System, is a security-focused Debian-based Linux distribution aimed at preserving privacy and anonymity. All its incoming and outgoing connections are forced to go through Tor, and any non-anonymous connections are blocked. Wikipedia).*

Whonix

Whonix is a Debian GNU/Linux–based security-focused Linux distribution. It aims to provide privacy, security and anonymity on the internet. The operating system consists of two virtual machines, a "Workstation" and a Tor "Gateway", running Debian GNU/Linux. All communications are forced through the Tor network to accomplish this. Wikipedia

Web Browsers

For Desktop

Firefox Needs manual tweaking to be more secure! Use ghacks

Firefox, is a free and open-source web browser developed by the Mozilla Foundation and its subsidiary, the Mozilla Corporation. Wikipedia Recommended addons: uBlock Origin | Https Everywhere | Privacy Badger | Privacy Possum | Decentraleyes | NoScript | CanvasBlocker

Tor

Tor is free and open-source software for enabling anonymous communication. The name derived from the acronym for the original software project name "The Onion Router". Tor directs Internet traffic through a free, worldwide, volunteer overlay network consisting of more than seven thousand relays to conceal a user's location and usage from anyone conducting network surveillance or traffic analysis. Using Tor makes it more difficult to trace Internet activity to the user. Wikipedia

UnGoogled-Chromium

Without signing in to a Google Account, Chromium does pretty well in terms of security and privacy. However, Chromium still has some dependency on Google web services and binaries. In addition, Google designed Chromium to be easy and intuitive for users, which means they compromise on transparency and control of internal operations.
ungoogled-chromium addresses these issues in the following ways:

For mobile

Bromite Android Only

Bromite is a Chromium fork with ad blocking and privacy enhancements; take back your browser! Bromite

Firefox Focus Android - iOS

Firefox Focus is a free and open-source privacy-focused browser from Mozilla, available for Android and iOS. Wikipedia

Tor Browser for mobile Android - iOS

Tor protects your privacy on the internet by hiding the connection between your Internet address and the services you use. We believe Tor is reasonably secure, but please ensure you read the instructions and configure it properly. GitHub

Email

Tutanota

Tutanota is an end-to-end encrypted email software and freemium hosted secure email service. Wikipedia

Mailbox

There are many ears listening on the Internet, which is why all our services require mandatory SSL/TLS-encrypted data transmission. For additional security, we also use enhanced (green) security certificates ("EV") by the independent SwissSign trust service provider from Switzerland (Check the padlock symbol in your web browser's URL field). But this is just the beginning – there is so much more that we do. Mailbox

Disroot

Disroot is a decentralized cloud-based service that allows you to store your files and communicate with one another. Established by a privacy-focused organization of volunteers, if we look at Disroot as an email provider specifically, it stands out thanks to its emphasis on security with a completly free open-source approach. ProPrivacy

ProtonMail

ProtonMail is an end-to-end encrypted email service founded in 2013 in Geneva, Switzerland by scientists who met at the CERN research facility. ProtonMail uses client-side encryption to protect email content and user data before they are sent to ProtonMail servers, unlike other common email providers such as Gmail and Outlook.com. The service can be accessed through a webmail client, the Tor network, or dedicated iOS and Android apps. Wikipedia

Search Engine

Searx

searx is a free metasearch engine, available under the GNU Affero General Public License version 3, with the aim of protecting the privacy of its users. To this end, searx does not share users' IP addresses or search history with the search engines from which it gathers results. Tracking cookies served by the search engines are blocked, preventing user-profiling-based results modification. By default, searx queries are submitted via HTTP POST, to prevent users' query keywords from appearing in webserver logs. Wikipedia - Find public instances of searx here searx.space

Startpage

Startpage is a web search engine that highlights privacy as its distinguishing feature. Previously, it was known as the metasearch engine Ixquick, At that time, Startpage was a variant service. Both sites were merged in 2016. Wikipedia

YaCy

YaCy is a free distributed search engine, built on principles of peer-to-peer (P2P) networks. Its core is a computer program written in Java distributed on several hundred computers, as of September 2006, so-called YaCy-peers. Each YaCy-peer independently crawls through the Internet, analyzes and indexes found web pages, and stores indexing results in a common database (so called index) which is shared with other YaCy-peers using principles of P2P networks. It is a free search engine that everyone can use to build a search portal for their intranet and to help search the public internet clearly. Wikipedia

VPN

If you need anonymity and privacy online use Tor instead, if you are looking to bypass a geo-restriction, don't trust public WiFi, or are looking to Torrent, a VPN will help you.

Mullvad

Mullvad is an open-source commercial virtual private network (VPN) service based in Sweden. Launched in March 2009, Mullvad operates using the WireGuard and OpenVPN protocols. Mullvad accepts Bitcoin and Bitcoin Cash for subscriptions in addition to conventional payment methods.
No email address or other identifying information is requested during Mullvad's registration process. Rather, a unique 16-digit account number is anonymously generated for each new user. This account number is henceforth used to log in to the Mullvad service.
The TechRadar review notes that "The end result of all this is you don't have to worry about how Mullvad handles court requests to access your usage data, because, well, there isn't any." Wikipedia

ProtonVPN

ProtonVPN utilizes OpenVPN (UDP/TCP) and the IKEv2 protocol, with AES-256 encryption. The company has a strict no-logging policy for user connection data, and also prevents DNS and Web-RTC leaks from exposing users' true IP addresses. ProtonVPN also includes Tor access support and a kill switch to shut off Internet access in the event of a lost VPN connection.
In January 2020, ProtonVPN became the first VPN provider to release its source code on all platforms and conduct an independent security audit. ProtonVPN is the only VPN to do so, even though experts say this is a crucial factor in deciding whether to trust a VPN service. Wikipedia

For information about alternatives to software and services.

If you are looking for alternatives to proprietary services like Discord and Facebook, or an open-source alternative to Photoshop, check out our list about Awesome-Alternatives

Mirrors are kept up to date, this post may lag behind as we add stuff in.

submitted by CipherOps to LinuxCafe [link] [comments]

⟳ 870 apps added, 78 updated at f-droid.org

Notice: this update is spurious, and the issue is being looked at.
⟳ f-droid.org from Wed, 26 Feb 2020 20:21:50 GMT updated on Sun, 01 Mar 2020 05:23:29 GMT contains 2962 apps.
Added (870)
Updated (78)
2020-03-01T05:53:18Z
submitted by BrainstormBot to FDroidUpdates [link] [comments]

[Help] For some reason, my homescreen is very slow whenever I tried to swipe to the next page.

Here is my tweak list: 7-zip (POSIX): 16.02-1 A-Font: 1.5.2 Accelerated Home Button: 1.6 Activator Theme Fix: 1.0 Activator: 1.9.13~beta5 AdBlock for YouTube: 1.0.7 AllowTouchesOnPageDots: 1.0.1-1+debug AnimationsBeFast: 1.4.7 AppList: 1.5.15~beta1 Apps Manager: 1.5.0-12 AppStore++: 0.9.6-1 APT (apt-key): 1.4.9-2 APT 0.7 Transitional: 1:0-2 APT 1.4 Strict (libapt-pkg): 1.4.9-1 APT Command Line: 1:0-2 APT Strict (lib): 1.4.9-2 APT Strict: 1.4.9-1 Archero Cheats: 1.1.5+iOSGods.com Assuan: 2.5.1-1 Asteroid: 3.0.4 AutoTouch Cracked: 5.1.2-1k Barmoji: 1.9 Base Structure: 1-5 BatteryLife: 1.7.0 BegoneCIA (iOS 11 and 12): 0.2.1-2 Berkeley DB: 6.2.32-1 BetterCCIconsPro: 1.7.5k BetterCCXI (Weather Addon): 1.0.1 BetterCCXI: 1.4.8 betternet: 0.0.1 BetterSettings: 0.1.3 BigBoss Icon Set: 1.0 BinaryNumpad: 1.1 Bitcoin Billionaire Cheats: 4.8.1 Bourne-Again SHell: 5.0.3-1 bzip2: 1.0.6-1 CA Certs: 0.0.2 CamControls X: 1.0.2 Cappd: 1.0.3 CCLinker: 1.2.1 CCModules: 1.4-3 CCRinger: 2.1.0 CCSupport: 1.2-3 Cephei: 1.13.1-2 CircleSettings: 1.0.1 CocoaTop: 2.0.2 ColorBadges: 1.3.2-1 ColorFlow 4 (iOS 11 – 12): 1.3.0 Compactions CC: 1.1 CoolCC: 1:3.1 Core Utilities (/bin): 8.30-3 Core Utilities: 8.30-2 Cowbell: 1.2.1 CrashReporter: 1.16.0-1 Cuboid: 2.0.1 cURL: 7.65.0-1 Cydia Installer: 1.1.32~b16 Cydia Substrate: 0.9.7033 Cydia Translations: 1.1.32~b1 Cylinder: 1.0.6 CylinderFix: 0.0.2 DaDa-statusbar-1: 1.0 Darwin Tools: 1-6 Debian Packager: 1.18.25-11 Debian Utilities: 4.8.6-1 DeleteForever: 0.0.1-57 DetailedBatteryUsage: 1.1.1 Diff Utilities: 3.6-1 Disconnected: 1.0 diskdev-cmds: 593.221.1-1 DismissProgress: 1.0.4 DLGMemor Injected: 1.2.1 DoubleCut: 0.5 Dune: 1.2.1 DzMoha Icons: 9.8 Eclipse Dark Mode (iOS 12): 6.1.2 Episode - Choose Your Story Cheats: 10.40 Essential: 0-1 ExactTimePhone: 1.0-1+debug EZSwipe: 1.1 Fallout Shelter Cheats: 1.13.21 FastDel: 0.5 FDots: 1.0.1 file: 5.35-2 Filza File Manager 64-bit: 3.7.0-18 Find Utilities: 4.6.0-2 Fiona: 0.1 Flame: 1.3 Flat UI Theme: 1.2.4 FlipConvert: 0.0~beta5 Flipswitch: 1.0.16~beta5 FloatyDock: 1.5 FolderColor: 1.0-4 Free IAP: 0.0.1-7+debug gettext: 0.19.8-1 GNU Cryptography: 1.8.3-1 GNU Multiple Precision Arithmetic Library: 6.1.2-1 GnuPG Errors: 1.32-1 GnuPG: 2.2.11-2 GnuTLS: 3.5.19-1 grep: 3.1-1 Groovify: 1.2.1 Gushi Statusbar: 1.3 gzip: 1.9-1 HideDockLabels10: 0.0.1-7+debug HomeGesture: 2.1.4 Host AdBlocker: 1.6-3 hotspotvip: 4.7.0-1+debug HYI Repo Icons: 8.0.4 iCleaner Pro: 7.7.5 IconSupport: 1.11.1 Immortal: 1.2.1-1 IOKit Tools: 76-1 iOS Firmware: 12.2 iOSGods iAP Cracker: 1.0-2 iPhone Firmware (/sbin): 0-1 iThemer: 1.FuckYes Jailbreak Resources: 1.0~b23 Jumper: 1.5.0 KBPreferences: 0.0.7 Kiiimo Repo Icons: 12.5 KillX: 0.1.2 KSBA: 1.3.5-1 LeadMeHome: 1.0.1 LeaveMeAlone: 2.3.1 LetMeBlock: 0.0.6.8 LetMeKnow: 1.4.1 libbulletin: 0.1-145 libcolorpicker: 1.6.3-1 libcrashreport: 1.1.0-1 libCSColorPicker: 1.0.3 libCSPreferences: 1.2.0 Liberty Lite (Beta): 0.2.12 libfoxfortutils: 1.0.8 libidn2: 6.1.2-1 libimagepicker: 1.0.3 libnepeta: 0.1.1 libnghttp2-14: 1.38.0-1 libpackageinfo (cokepokes): 1.1.0.1-3 libpackageinfo: 1.1.0.1-1 libplist: 2.0.0-2 libSparkAppList: 1.0.3 libssh2: 1.8.0-2 libSubstitrate: 0.0.1-3 libswift (stable): 5.0 libswift4: 4.2.1-2 libsymbolicate: 1.9.0-1 libtasn1: 4.13-1 libunistring: 0.9.10-1 LightsOn: 1.0.0 Line StatusBar: 1.21 Lineal CC Theme: 1.0 Lineal Music Controls: 1.0 Lineal UI Theme: 1.2 Link Identity Editor: 2:2.1.1+elucubratus2 Locale Profiles in UTF-8: 1.0-1 LocalIAPStore: 1.4-2 Lotus Dark: 1.0.7 Lotus: 1.0 LowPowerMode: 1.0-3 LSPullToDismiss [Public]: 0.0.1-1 LZ4: 1.7.5-1 LZMA Utils: 2:4.32.7-2 Mega UHB IPv4+6 - iOS 9/10/11/12 - MUHB IPv4+6 (Mega Untrusted Hosts Blocker IPv4 and IPv6): 2.1.1 MessageColors: 1.5 MessageTypingIndicators: 1.0-1 Moonshine: 1.3 Moveable12: 1.0.0~beta29-32 Mune - Neon Edition: 1.1 Muze 4: 1.0 Muzik: 2.0 NCNoTitle: 1.0.1 Nettle: 3.4.1-1 New Curses: 5.9-1 New Curses: 6.1-1 New GNU Portable Threads: 1.6-1 NoCCGrabber12: 1.1 NoLowPowerAutoLock [Public]: 0.0.3 NoLSPadLock: 0.1 NoLSScreenshot: 0.0.1 NoSub (PalBreak w/ options): 1.3 Notchification Cracked: 1.4.2k Notifica: 0.3.0-4 NudeKeys (iOS 12): 1.0.0~b8 OpenSSL 1.0 Libraries: 1.0.2s-1 p11-kit: 0.23.12-1 PasscodeText: 0.1 Pebbli Status Bar for Xeon: 1.0 PencilChargingIndicator: 1.2~b6 PhotoManager (iOS 12): 1.0.7-1+debug pincrush: 0.9.2-1 PM, really?: 1.2 Portrait Lock: 1.8.4 PreferenceLoader: 2.2.4~beta1 PrefixUI: 1.2.2 Profile Directory: 0-1 readline: 8.0-1 RealCC: 1.0.2 Reddit No Ads: 0.0.2 ReProvision: 0.4.2 ReturnDismiss: 0.0.1-4 RocketBootstrap: 1.0.7~beta3 rsync: 3.1.3-2 Sareth: 1.0.3-1 sed: 4.5-1 Shadow Fight 2 Cheats: 1.9.38 shell-cmds: 118-8 shuffle: 1.0.4 Shy Labels: 1.1.1 Signing Certificate: 0.0.1 SilentScreenshot: 1.2 SmallVolumeStep: 1.1.0-2 SmartLight: 1.0.4 SmoothCursor: 1.1.3 SnowBoard Labels Extension: 1.0.0~Beta1 SnowBoard Settings Icons Extension: 1.0.4~Beta1 SnowBoard StatusBar Extension: 1.0.1~Beta1 SnowBoard: 1.2.14~Beta1 Soba: 1.2 Soda StatusBar(Gray灰色版): 1.3 Soul Knight Cheats: 2.2.1 Spotlightless11: 1.1.1 SSG3 Cheats: 1.0.0-4 StatusSwitcher: 1.1.1 Substitute Dummy for unc0ver: 1.0 Substrate Safe Mode: 0.9.6001.1 SugarCane: 1.0.0 System Memory Reset Fix: 1.0 system-cmds: 790.30.1-2 Tape Archive: 1.30-2 TapTapFlip: 1.5 TapVideoConfig: 0.0.4.1 TechSupport Framework (cokepokes): 1.5.0.1-2 TranslucentCydia: 0.9.0-1 Trust Cache Injector: 0.4~b5 Tweak Count 2: 1.0.1 tweakCompatible: 0.1.5 TypeReceipt: 0.0.2 UHB - iOS 9/10/11/12 (Untrusted Hosts Blocker): 1.7.1 UIKit Tools: 1.1.13-18 Ultrasound: 1.2.9 unrar: 5.6.4-1 unzip: 6.0+deb9u1-1 Viola: 1.5 Waze ++: 4.53 Whoops: 1.0.2 WiFi Passwords: 3.0.1 Xen HTML: 0.5.4 XenInfo: 2.2.6 XZ Utils: 5.2.4-4 zip: 2.32-1
Thanks in advance.
submitted by Benetzit to jailbreak [link] [comments]

Armory is Now in the Official Debian Unstable (Sid) Repositories (and Ubuntu Vivid)

Armory is Now in the Official Debian Unstable (Sid) Repositories (and Ubuntu Vivid) submitted by josephbisch to Bitcoin [link] [comments]

Ethereum on ARM. Geth and Parity clients update. Status.im, IPFS and Swarm packages. Raiden Network and Trinity client installers.

EthArmbian [1] is a custom Linux image for the NanoPC-T4 ARM SoC [2] that runs Geth or Parity Ethereum clients as a boot service and automatically turns the device into a full Ethereum node.
Once powered up, the image takes care of all steps, from setting up the environment to running the Ethereum client and synchronizing the blockchain.
Edit: Images links are now Ready for Constantinople and Petersburg Hardforks. You can update Geth to 1.8.22 and Parity to 2.2.9 from these images by running:
update-ethereum
This is a new release of the EthArmbian image for the NanoPC-T4 ARM board. Ethereum is evolving quickly so it is time to include some other interesting pieces of the ecosystem. Changelog:

Download links

Armbian_5.74_Nanopct4_Ubuntu_bionic_default_4.4.172-1-geth.img.zip
Armbian_5.74_Nanopct4_Ubuntu_bionic_default_4.4.172-1-parity.img.zip
Note: The only difference between both images is the default client that runs at boot time. You can switch between Geth or Parity at anytime.
For further info regarding installation and usage please visit Github README [1]

Status.im, IPFS and Swarm

Status [5] is a decentralized messaging & browsing app (using the Whisper protocol). And as any P2P system, it needs… peers. So if you want to support it, status is now included as a systemd service, configured in whisper and mailserver mode.
You need to start it manually as it doesn’t run by default:
sudo systemctl start status.im
And, if you want it to get started on boot you need:
sudo systemctl enable status.im
Configuration options are located in /etc/ethereum/status.im.json.
Why run a Status node? (from their FAQ):
Currently, we don’t provide any incentives for running Status Nodes. We are working hard to solve this problem. Our intent is to increase the size of the Whisper network, thereby improving how “decentralized” and safe our platform is.
Another reason is privacy. In the current setup, nodes that are running as Mail Servers are trusted. This means that such a node can communicate directly with the Status app using a p2p connection and some metadata might leak. If one wants to avoid that, the best option is to run a Mail Server on your own and configure it in the Status app.
Another important piece of the so called web 3 is decentralized storage. The most mature option available is IPFS [6] which is now included as a systemd service as well. You need to start it manually as it doesn’t run for default:
sudo systemctl start ipfs
If you want IPFS to get started on boot you need to enable it by running:
sudo systemctl enable ipfs
You can tweak config options in /home/ethereum/.ipfs/config file (particularly, you may want to adjust the StorageMax parameter).
Swarm [7] (Ethereum decentralized storage solution) is available as a binary. You may want to take a look at the official docs to start testing it.
You can run these clients along with Geth or Parity client with no performance issues.

Raiden and Trinity

As you may know, Raiden Network [8] is a Layer 2 scalability solution (similar to Bitcoin's Lightning Network). Trinity [9] is a new Ethereum client developed entirely in Python (and already working on the beacon chain).
You can install both clients by running its corresponding bash script. Take into account that both are in alpha stage so expect some trouble and give back feedback to developers, if possible. They are not properly packaged yet so the script installs them directly from Github (it takes a while).
Installation: Type (as ethereum user):
install-trinity
install-raiden
You can now run "trinity" or "raiden" commands.
Note on Trinity: If you experience this issue: “trinity: error: Timed out waiting for database start”, try to increase wait_for_ipc() “timeout” value in /uslocal/lib/python3.6/dist-packages/trinity/utils/ipc.py [10]

Ethereum nodes FUD

We’ve been seeing lately a lot of misinformation about Ethereum blockchain size and other kind of FUD.
Stick to the facts. With Parity, it just takes several hours to get a full node up and running and you need about 140 GB of SSD disk size (2-3 days with Geth and 150GB of disk size). So, you could run a full node for several months even with a 256GB SSD unit. Don’t listen to this kind of nonsense. Plain and simple: they are wrong.
This "guy" knows [11]

References

[1] https://github.com/diglos/userpatches
[2] https://www.friendlyarm.com/index.php?route=product/product&product_id=225
[3] https://github.com/ethereum/go-ethereum/releases/tag/v1.8.21
[4] https://github.com/paritytech/parity-ethereum/releases/tag/v2.2.7
[5] https://status.im/
[6] https://ipfs.io/
[7] https://swarm-guide.readthedocs.io/en/latest/introduction.html
[8] https://raiden.network/
[9] https://trinity.ethereum.org/
[10] https://github.com/ethereum/trinity/issues/182
https://github.com/ethereum/trinity/pull/192/commits/e19326689cbb08fd81c1827a7a3ab41200bbbeff
[11] https://twitter.com/ethnodesize
submitted by diglos76 to ethereum [link] [comments]

Homelab collective ressources post!

Hey guys!
I'm fairly new to this sub and to having a home lab in general and I found this community to be so kind and helping, I wanted to give back what I've learned. I'm seeing a lot of questions asked around on improvements and on what to do with x extra hardware so I thought it would be nice to have a thread to regroup that.
 
I'll put here some stuff I gathered and the most common questions I've seen, feel free to contribute and i'll update the post along.
 
Latest Additions
 
Homelab Dashboard
Posts about dashboards have been growing lately and here are some of the best that were kind enough to provide us with their sources.
User Screenshot Source
yours truly http://imgur.com/a/GhCNH https://github.com/Gabisonfire/dashboard-q
lastditchefrt http://i.imgur.com/5zQdao4.png https://github.com/d4rk22/Network-Status-Page
_SleepingBag_ http://i.imgur.com/Ql9ZM4W.png https://github.com/jsank/homelabdash
NiknakSi https://niknak.org/extras/sysinfo TBA
DainBramaged http://imgur.com/jYNlUEQ https://github.com/gordonturneBigBoard
michaelh4u https://i.imgur.com/XkZwMKj.png https://github.com/michaelh4u/homelabfrontpage
spigotx http://imgur.com/a/1zMht https://github.com/spigotx/HomeLab2
SirMaster https://nicko88.com/ https://github.com/dashbad/plex-server-status
yourofl10 http://imgur.com/a/AyROa TBA
TheBobWiley http://imgur.com/a/oU6d3 https://github.com/TheBobWiley/ManageThis-LandingPages
0110010001100010 http://i.imgur.com/iwtQcsL.jpg https://github.com/danodemano/monitoring-scripts
mescon & SyNiK4L https://i.imgur.com/gqdVM6p.jpg https://github.com/mescon/Muximux
ak_rex http://i.imgur.com/a/RJkrT https://github.com/ak-rex/homelab-dashboard
 
Or build yours from scratch: PRTG API, ELK, Grafana, freeboard, JumpSquares
 
Some other resources: Custom Monitoring Scripts by 0110010001100010
 
Credits to apt64 for his original post
= Pi specific =
 
= Download Automation =
 
= Virtualization =
 
= Monitoring =
 
= Media Center =
 
= Remote access =
 
= VOIP =
 
= Networking =
 
= File Servers/Storage/RAID =
 
= Cameras =
 
= Documentation =
 
= Dynamic DNS =
 
= Backup =
 
= Creating network diagrams =
 
= Guides =
 
= Misc =
 
That's all I could come up with on top of my head + some research, passing over to you guys so we can get a nice complete list!
 
Let's try and stick with free(or mostly) softwares, let me know if you guys feel otherwise.
submitted by Gabisonfire to homelab [link] [comments]

Dogecoin on Linux - The Complete Beginner's Guide

I'm writing this because I couldn't find a single condensed guide on compiling the wallet and running mining software on linux, specficially Ubuntu/Linux Mint. I combed Bitcoin and Litecoin forums for similar problems I was running into and eventually got everything nailed down, so here it is in one place, for new Shibes.
If you want to make a Dogecoin directory in your downloads folder to keep things organized, you will need to modify these commands to refelct the change. So instead of going to ~/Downloads/ you will need to go to ~/Downloads/Dogecoin and be sure to put the zipped files there when you download them, but the commands will be the same otherwise.
cwayne18 put in the work to make a PPA for the QT client here.
Ubunutu/Mint/Debian users should be able to install the client with the following commands:
sudo add-apt-repository ppa:cwayne18/doge sudo apt-get update && sudo apt-get install dogecoin-qt 
To update using this method, run
sudo apt-get update && sudo apt-get upgrade dogecoin-qt 
Compiling the Wallet Manually
I suggest using the PPA above, but if you want to compile manually, here you go.
1)Download the newest source from here. If you want to check out the Github page, click here
2)Unzip the package with the native client OR, navigate to your downloads and unzip
cd ~/Downloads unzip dogecoin-master.zip 
3)Now it's time to compile. You will need to install the dependencies, just copy and paste the following code. It will be a fairly large download and could take some time. It is always important to update before installing any new software, so we'll do that first and then install the dependencies.
sudo apt-get update sudo apt-get upgrade sudo apt-get install libssl-dev libdb-dev libdb++-dev libqrencode-dev qt4-qmake libqtgui4 libqt4-dev sudo apt-get install libminiupnpc-dev libminiupnpc8 libboost-all-dev build-essential git libboost1.53-all-dev 
4)Once that is done, go to the doge-coin master directory and compile:
cd ~/Downloads/dogecoin-maste sed -i 's/-mgw46-mt-sd-1_53//g' dogecoin-qt.pro qmake USE_UPNP=- USE_QRCODE=0 USE_IPV6=0 make -j3 
After running the qmake command you will likely see some text similar to
Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target language has less forms. If this sounds wrong, possibly the target language is not set or recognized. 
It's perfectly normal, so don't worry about that.
Your Dogewallet is ready to go! The executable is in ~/Downloads/dogecoin-maste and called dogecoin-qt. Your wallet information is in ~/.dogecoin. You can run the wallet at any time by opening terminal and typing
cd ~/Downloads/dogecoin-maste ./dogecoin-qt 
Future upgrades to dogewallet are easy. Back up your wallet.dat, and simply follow the same directions above, but you'll be unzipping and building the newer version. You will likely need to rename the old dogecoin-master directory in ~/Downloads before unzipping the newest version and building. Also, it is likely that you will not need to install the dependencies again.
Alternate Method For Installing Dogecoin Wallet from Nicebreakfast
After installing the dependencies listed in step 3, open terminal, then navigate to where you want Dogecoin Wallet stored and run:
git clone https://github.com/dogecoin/dogecoin ./autogen.sh ./configure make 
then when the wallet is updated just run
git pull 
from the dogecoin directory.
GPU Mining
GPU mining requires CGminer. My suggestion is to get the executable already built. The creator of cgminer has removed the built file from his website, but I've uploaded it here
sudo apt-get install pkg-config opencl-dev libcurl4-openssl-dev autoconf libtool automake m4 ncurses-dev cd ~/Downloads tar -xvf cgminer-3.7.2-x86_64-built.tar.bz2 
Don't use anything newer than 3.7.2. The newer versions of CGMiner don't support GPU mining.
That's it! You have cgminer ready to go! You will run cgminer with the following syntax
cd ~/Downloads/cgminer-3.7.2-x86_64-built/ ./cgminer --scrypt -o stratum+tcp://SERVERNAME:PORT -u WORKER.ID -p PASS 
A good guide for fine tuning cgminer can be found here; follow the litecoin example.
EDIT
I had trouble getting cgminer running with a single line command, but running it via an executable .sh file works. This is covered in the cgminer setup guide I posted above but I'll put it here too. In the same directory that has the cgminer executable, you need to make a file called cgminer.sh and make it executable. It should contain the follwing:
export GPU_USE_SYNC_OBJECTS=1 export GPU_MAX_ALLOC_PERCENT=100 export DISPLAY=:0 find *.bin -delete sleep 5 ./cgminer 
Then you can call cgminer in terminal by doing ./cgminer.sh You will need a cgminer.conf file containing all your options. All of this is covered in the guide that is linked above.
A quick note about AMD drivers: They used to be a huge PITA to install and get working, but the newest Catalyst drivers are great. There's a GUI installer, everything works out of the box, and there is a lot of documentation. You can download them here: AMD Catalyst 14.6 Beta Linux
CPU Mining
For CPU mining I use minerd because it doesn't require any work to get running, simply download it and get to work. Download the built file for your machine 32-bit or 64-bit, and then unzip it and you're ready to go!
cd ~/Downloads tar -xvf pooler-cpuminer-2.3.2-linux-x86.tar.gz 
The executable is called minerd and it will be in ~/Downloads but you can move it to wherever you like. To run it, pull up terminal and do
cd ~/Downloads minerd --url=stratum+tcp://SERVER:PORT --userpass=USERNAME.WORKERNAME:WORKERPASSWORD 
You're done! Happy mining!
Common Issues
I ran into this and I've seen others with this problem as well. Everything installs fine but there is a shared library file that isn't where it should be. In fact, it isn't there at all.
 libudev.so.1: cannot open shared object file: No such file or directory 
In terminal, do
sudo updatedb locate libudev.so.0.13.0 
And it will probably return a path /lib/x86_64-linux-gnu. Inside that directory there's a library file called libudev.so.0.13.0. You'll need to make a symlink (aka shortcut) that links libudev.so.1 to libudev.so.0.13.0 So, assuming you're working with libudev.so.0.13.0 do this
cd /lib/x86_64-linux-gnu sudo ln -s libudev.so.0.13.0 libudev.so.1 
Now if you do
ln -l 
You should see
libudev.so.1 -> ./libudev.so.0.13.0 
Meaning you've made the symlink. Also, the text for libudev.so.1 will be blue.
submitted by Boozybrain to dogecoin [link] [comments]

Mega FAQ (Or: Please come here for your questions first)

Qbundle Guide (Step by step setup & Bootstrap) https://burstwiki.org/wiki/QBundle
1( I want to mine or activate My account. Where do find the multiple coins?
You only need 1, an outgoing transaction or reward reassignment will set the public key. Get them from:
https://www.reddit.com/burstcoinmining/comments/7q8zve/initial_burstcoin_requests/
Or (Faucet list)
https://faucet.burstpay.net/ (if this is empty, come back later)
http://faucet.burst-coin.es
Or
https://forums.getburst.net/c/new-members-introductions/getting-started-initial-burstcoin-requests
2( I bought coins on Bittrex and want to move to my new wallet, but can't. Why?
Bittrex will only send to accounts with a public key (not a Burst requirement) so see number 1 and either set the name on the account (IF you will not mine) or set the reward recipient to the pool. Either action will enable the account and allow for transfers from Bittrex.
3( I sent coins from Poloniex/anywhere to Bittrex and they don’t show up after a considerable time. Why?
You need to set an unencrypted message on the transaction, informing Bittrex which account to send the funds to (this is in the directions on Bittrex). Did you do this? Contact Bittrex support with all the details and eventually you will get your funds.
4( How much can I make on Burst?
https://explore.burst.cryptoguru.org/tool/calculate
Gives you an average over time assuming a few things like: Average luck/100% uptime/no overlapping/fees on pool/good plot scan time (<20 seconds) if you do not have all of these, you may not see that number.
5( If I use SSD’s would I make more money?
No, it’s 95% capacity and 5% scan time that determine success. More plot area = better deadlines = better chance of forging a block, or better rates from a pool.
6( What is ‘solo’ and ‘pool’ (wasn’t his name Chewbacca?)
Solo is where you attempt to ‘forge’ (mine) a block by yourself; you get 100% of the block reward and fees. But you only receive funds if you forge, no burst for coming in second place.
Pools allow a group of miners to ‘pool’ together their resources and when a miner wins, they give the pool the winnings (this is done by the reward assignment you completed earlier), it is then divided according to different percentages and methods and burst is sent out according to pool rules (minimum pay-out, time, etc.)
7( I have been mining for 2 days and my wallet doesn’t show any Burst WHY?
Mining solo: it is win-or-lose, nothing in between, and wining is luck and plot size. Pool mining: because it costs 1 burst to send burst, the pools have either a time requirement (every X days) or a minimum amount (100 burst +) so you need to research your pool. Some pools allow for you to set the limit (cryptoGuru and similar) to be met before sending
8( How do I see what I have pending?
On CryptoGuru, based pools, it’s the ‘Pending (burst)’ column, other pools, look for the numbers next to your burst ID. One is Paid and the other pending.
9( I’m part of a pool and I forged a block, but I didn’t recieve the total value of the block, why?
A pool has 2 basic numbers that denote the pay-out method, in the format ‘XX-XX’ (i.e. 50-50) The first number is the % paid to the block forger (miner) and the second is the retained value, which is paid to historic ‘shares’ (or, past blocks that the pool didn’t win, but had a miner that was ‘close’ to winning with a good submitted deadline)
Examples of pools:
0-100 (good for <40TB)
20-80 (30-80TB)
50-50 (60-200TB)
80-20 (150-250)
100-0 (solo mine, 150+ TB)
Please note that there is an overlap as this is personal preference and just guidance; a higher historical share value means a smoother pay-out regime, which some people prefer. If fees are not factored in, or are the same on different pools, the pay-out value will be the same over a long enough period.
10( Is XXX model of hard drive good? Which one do you recommend?
CHEAP is best. If you have 2 new hard drives, both covered by warranty, get the one with the lowest cost per TB (expressed as $/TB , calculated by dividing the cost by the number of terabytes) because plot size is KING,
11( How many drives can I have on my machine?
For best performance, you can have up to 2 drives per thread (3 on a new fast AVX2 CPU). So that quad-core core-2-quad can have up to 8 drives, but a more modern i7 with 4 cores + hyper threading can squeeze 8 * 3 or 24 drives. (Performance while scanning will suffer)
12( Can I game while I mine?
Some people have done so, but you cannot have the ‘maximum’ number of drives and play games generally.
13( Can I mine Burst and GPU mine other coins?
Yes, if you CPU Mine Burst.
14( I’m GPU plotting Burst and GPU mining another coin, my plots are being corrupted, why?
My advice is dedicating a GPU to either mining or plotting, don’t try to do both.
15( What is a ‘plot’?
A plot is a file that contains Hashes, these hashes are used to mine burst. A plot is tied to an account, but they can be created (with the same account ID) on other machines and connected back to your miner(s).
16( Where can I trade/buy/sell Burst?
A list of exchanges is maintained on https://www.reddit.com/burstcoin/ (on the right, ‘Exchanges’ tab) the biggest at the moment are Bittrex and Poloniex, some offer direct Fiat-to-Burst purchase (https://indacoin.com for example)
17( Do I have to store my Burst off the exchange?
No, but it’s safer from hackers who target exchanges, if you cannot guarantee the safety or security of your home computer from Trojans etc, then it might be best to leave on an exchange (but enable 2FA security on your account PLEASE!)
18( What security measures can I take to keep my coin safe?
When you create an account, sign out and back in to your wallet (to make sure you have copied the pass phrase correctly) and keep multiple copies of the key (at least one physically printed or written down and in a safe place, better in 2 places) do not disclose the passphrase to anyone. Finally use either a local wallet or a trusted web wallet (please research before using any web wallet)
19( How can I help Burst?
Run a wallet, which will act as a node (or if you’re a programmer, contact the Dev team Bring attention to burst (without ‘shilling’ or trying to get people to buy) And help translate into your local language
Be a productive member of the community and contribute experience and knowledge if you can, or help others get into Burst.
20( Will I get coins on the fork(s) and where will they be?
There will be no new coin, and no new coins to be given/air dropped etc, the forks are upgrades to burst and there will not be a ‘classic’ or ‘new’ burst.
21( Will I need to move my Burst off of the exchange for the fork?
No, your transactions are on the block chain, which will be used on the fork, they will be visible after the move; nothing will need to be done on your side.
22( Where can I read about the progress of Burst and news in general on the community?
There is no finer place than https://www.burstcoin.ist/
23( What are the communities for Burst and the central website?
Main website: https://www.burst-coin.org/
Reddit: https://www.reddit.com/burstcoin and https://www.reddit.com/burstcoinmining/
Burstforum.net: https://www.burstforum.net/
Getburst forum: https://forums.getburst.net/
Official Facebook channel: https://m.facebook.com/groups/398967360565392
(these are the forums that are known to be supporting the current Dev Team)
Other ways to talk to the community:
Discord: https://discordapp.com/invite/RPhpjVv
Telegram (General): https://t.me/burstcoin
Telegram (Mining): https://t.me/BurstCoinMining
24( When will Burst partner up with a company?
Burst is a currency, the USD does not ‘partner up’ with a company, the DEV team will not partner up and give over to special interests.
25( Why is the DEV team anonymous?
They prefer anonymity, as it allows them to work without constant scrutiny and questions unless they wish to engage, plus the aim is for Burst to become a major contender, and this brings issues with security. They will work and produce results, they owe you nothing and if you cannot see the vision they provide then please do not ‘invest’ for short term gain.
26( When moon/Lambo/$100/make me rich?
My crystal ball is still broken, come back to the FAQ later for answer (seriously, this is a coin to hold, if you want to day-trade, good luck to you)
27( How can I better educate myself and learn about Dymaxion?
Read about the Dymaxion here: https://www.reddit.com/burstcoin/wiki/dymaxion
28( My reads are slow, why?
There are many reasons for this, if your computer has a decent spec it’s likely due to USB3 hub issues, or plugging into a USB2 hub, but other reasons can be multiple plots in the same folder, but it’s best to visit the mining subreddit. They can help more than an simple FAQ https://www.reddit.com/burstcoinmining/
29( I have a great idea for Burst (not proof of stake related)?
Awesome! Please discuss with the DEV team on discord https://discordapp.com/invite/RPhpjVv
(Please be aware that this is a public forum, you need to find who to ask/tell)
30( I have a great idea for Burst (Proof of stake related)?
No. if you want a POS, find a POS coin. On the tangle which is being implemented a POS/POW/POC coin can be created, but BURST will always be POC mined. You are welcome to implement a proof of stake coin on this!
31( Will the Dev team burn any coins?
Burst is not an ICO, so any coins will need to be bought to be burnt. You are welcome to donate, but the DEV team have no intention of burning any coins, or increasing the coin cap.
32( When will there be an IOS wallet?
IOS wallet is completed; we are waiting for it to go on the app store. Apple is the delaying factor.
33( Why do overlapping plots matter?
Plots are like collections of lottery tickets (and if only one ticket could win). Having 2 copies is not useful, and it means that you have less coverage of ‘all’ the possible numbers. It’s not good, avoid.
34( My local wallet used to run, I synchronised it before and now it says ‘stopped’. when I start it, it stops after a few seconds, what should I do?
I suggest that you change the database type to portable MariaDB (on Qbundle, at the top, ‘Database’ select, ‘change database’) and then re-import the database from scratch (see 35)
35( Synchronising the block chain is slow and I have the patience of a goldfish. What can I do?
On Qbundle , ‘Database’ select ‘Bootstrap chain’ and make sure the CryptoGuru repository is selected, then ‘start Import’ this will download and quickly stuff the local database (I suggest Portable MariaDB, see 34) (lol, loop)
36( What will the block reward be next month/will the block rewards run out in 6 months?
https://www.ecomine.earth/burstblockreward/ Rewards will carry on into 2026, but transaction fees will be a bigger % by then, and so profitable mining will continue.
37( How can I get started with Burst (wallet/mining/everything) and I need it in a video
https://www.youtube.com/watch?v=LJLhw37Lh_8 Watch and be enlightened.
38( Can I mine on multiple machines with the same account?
Yes, if you want to pool mine this can be done (but be prepared for small issues like reported size being incorrect. Just be sure to keep question 33 in mind.)
39( Why do some of my drives take forever to plot?
Most likely they are SMR drives, it’s best to plot onto another SSD and then move the finished plot/part of a plot across to the SMR drive as this is much quicker. SMR drives are fine on the read, just random writes that are terrible.
So plot an SMR drive quickly, plot to a non SMR or better still SSD drive, in as big a chunk as possible (fewer files better) and move. a version of Xplotter, called Splotter, can do this easily.
https://github.com/NoParamedic/SPlotter
40( I have a great idea; why not get listed on more exchanges!!
Exchanges list coins because of 2 reasons:
  1. Clients email and REQUESTING Burst and provide details like:
    i. https://www.burst-coin.org/information-for-exchanges
  2. The coin pays (often A LOT, seriously we’ve been asked for 50 BTC)
I suggest you speak with your exchange and ask ‘when will they offer Burst?’
41( Do you have a roadmap?
https://www.burst-coin.org/roadmap
42( Why is the price of Burst going up/down/sideways/looping through time?
The price of burst is still quite dependent upon Bitcoin, meaning that if Bitcoin gains, the value of Burst gains, if Bitcoin drops then Burst also drops. If there is news for Burst then we will see something independent of Bitcoin moving. Variations can be because of people buying in bulk or selling in bulk. There are also ‘pump and dump’ schemes that we detest, that can cause spikes in price that have nothing to do with news or Bitcoin, just sad people taking advantage of others.
43( Where is the best place to go with my mining questions?
https://www.reddit.com/burstcoinmining/
or https://t.me/BurstCoinMining
44( What hardware do you advise me to buy, is this computer good?
See question 43 for specific questions on hardware, it depends on so many variables. The ‘best’ in my opinion is a 36 bay Supermicro storage server, usually they have dual 6-core CPU’s and space for 36 drives. No USB cables, plotting and mining monster, anything else, DYOR.
45( Where do you buy your hard drives?
I have bought most from EBay in job lots, and some refurbished drives with short warranties. Everything else I have bought, from Amazon.
46( Can I mine on my Google drive/cloud based storage?
In short: no. If you want to try, and get to maybe 1 TB and then find that your local connection isn’t fast enough, or that shortly after, your account is blocked for various reasons. Please be my guest.
47( Can I mine on my NAS?
Some you can mine with the NAS (if it can run the miner, it can scan locally) but generally they’re not very fast. good for maybe 16 TB? Having a plot on a NAS and mining from another computer depends on the network speed between the NAS and scanning computer. I believe you can scan about 8 TB (maybe a bit more) and keep the scan times to within acceptable, but YMMV.
48( How can I set up a node?
No need to set up a node, just set up a wallet (version 2.0.4) or Qbundle (2.2) and it will do the rest
49( Are the passphrases secured?
I’ll leave the effort to a few people to show how secure a 12-word passphrase is: https://burstforum.net/topic/4766/the-canary-burst-early-warning-system Key point: brute forcing it will be around 13,537,856,339,904,134,474,012,675,034 years.
50( I logged into my account (maybe with a different burst ID) and see no balance!!
I have dealt with this very issue multiple times, and there are only 3 options:
  1. You have typed in the password incorrectly
  2. You have copy-pasted the password incorrectly
  3. You are trying to log into a ‘local wallet’ which the block chain has not finished updating
The last one generally leaves the burst ID the same, but old balances will show. No, this is not a security problem, and yes, windows loves to add spaces after the phrase you enter when copied, and that space is important in getting to your account.
51( Are there channels for my language?
Telegram:
Spanish: https://t.me/burstcoin_es
German: https://t.me/Burstcoinde
Italian: https://t.me/BurstCoinItalia
Forum:
Spanish: https://burst-coin.es/index.php/forum/index
Discord:
Spanish: https://discordapp.com/invite/RaaGna9
Bulgarian: https://discord.gg/r4uzTd
(there are others, please contact me to put up)
52( I am mining in a pool, and it says that my effective capacity is lower than I actually have, why?
  1. If you've not been mining for >48 hours, or just added additional capacity, it will take time.
  2. The value fluctuates (normally, +-5% but can be up to 10% at times)
  3. Read on the ‘Quick info’ tab about adjusting your deadline to compensate for changes i. revisit once a month for best results
  4. If you have overlapping plots it will also be lower so be aware of this (see question 33)
53( What pool should I join?
First of all, read question 9, after you have understood that it depends on the size (and how patient you are) select from the following list: https://www.ecomine.earth/burstpools/
54( What miner to use?
I use Blago’s miner, there are many out there but Blago’s works for me on CPU mining, it can be found in Qbundle.
55( What Wallet to use (I use windows)?
Qbundle: https://github.com/PoC-Consortium/Qbundle/releases/ guide: https://burstwiki.org/wiki/QBundle
56( What Wallet to use (Linux)?
https://package.cryptoguru.org/ for Debian and Ubuntu, for Mac. read:
https://www.ecomine.earth/macoswalletinstallguide/
57( Will i need to 'replot' after POC2 (second fork) happens?
No, there will be a tool which will optimise, but it is not CPU intensive (it basically re-shuffles your plot) and is just IO intensive. You do not need to replot.
TurboPlotter and https://github.com/PoC-Consortium/Utilities/tree/mastepoc1to2.pl are tools that will/can be used to actuate optimization, but PLEASE wait with optimization until after the hard fork.
58( Will the transaction fee always be 1 burst?
No, dynamic fees are coming in the next fork.
submitted by dan_dares to burstcoin [link] [comments]

Let's build an army of Ethereum nodes!

Hi everyone!
I ran into Ethereum several months ago while reading about bitcoin and the blockchain and was quite impressed by some videos explaining the project (most of them by Vitalik himself). During this time I've tried to educate myself on this breakthrough technology. And at this point, I'd like to get a little more involved. I think that one easy way to contribute to this fascinating project is by running a full Ethereum node, so let me share some stuff of my experience of setting up an Ethereum node on Raspberry Pi 3.
While doing some research about the best Ethereum client for my raspberry Pi 3 I realized that pretty much there are no ARM nodes on the network (according to ethernodes.org). Shouldn't be precisely the opposite? ARM devices such as Raspberry Pi have a good performance, are cheap and power-efficient.
I looked into "EthEmbedded" [1] (great project, by the way) but it is mainly focused on Geth and Eth clients and you need to run the Ethereum clients manually. It's built on top of Ubuntu mate (and we need to keep things light). Besides, I was looking something more Flash & Play :-).
So, I compiled Parity from source on my raspberry Pi 3 (which is the most efficient Ethereum client out there [2]) and gave it a try. I was really surprised with the overall performance and thought that it would be great to get an Ethereum node up and running easiest way possible.
So, I built a custom Raspbian image which runs Parity as a boot up service and starts syncing the blockchain with no user interaction. This is what I got so far:
A custom [3] Raspbian [4] image with Ethcore Parity 1.3 [5] integrated. The image is generated using pi-gen [6] (plus a couple of files for Parity installation)
Some remarks:
Final thoughts:
I think there are several reasons to try to increase Ethereum ARM nodes in the coming months:
You can download the Custom Raspbian Image here:
http://www.ethraspbian.com/downloads/2016-09-09-ethraspbian.img.zip
For further installation instructions please visit:
https://github.com/diglos/pi-gen
Let me know your comments.
Let's do this. Mine is up and running :-)
TL;DR: If you want to contribute to the Ethereum network, get a Raspberry pi 3, install the OS image into your microSD card, connect the ethernet cable and power on your device. This is it, flash and play :-), you are already running an Ethereum node!
submitted by diglos76 to ethereum [link] [comments]

Anatomy of crypto data destruction and RNG

Ever since the post-credits scene in season 2, I've been thinking about how the stage 1 "payload" that encrypted all of the E-Corp systems might have been built, and how it might be flawed enough to permit data recovery. No sci-fi time-travel magic required for this theory.
We never get a direct look at the malware, but we do get a smattering of references to what it is throughout the episodes so far. Not enough to get a totally clear picture, but it's somewhere to start with educated guesses.
In S01E01, Mr. Robot is explicit about the aims:
If we hit their data center just right, we could systematically format all the servers, including backup. It would be impossible to enforce outdated paper records. It would all be gone.
Okay. They want to irreversibly delete the data on all of E-Corp's servers and backups.
In S01E02, when tasking Elliot with blowing up the Comet electric natural gas plant to take out the tape backups at Steel Mountain, Mr. Robot elaborates:
Once we blow up the pipeline, Darlene's worm will kick into high gear at the US datacenter, which you helped us to install. Thank you very much. The redundant backups at their eastern datacenter in China? The dark army is covering us on that.
Okay, we've learned the way they'll do it is with a worm, which Darlene wrote. A worm is malware that is designed to replicate itself and carry a payload.
In S01E08, after successfully entering the work order to remove the honeypot around CS30, Elliot states:
In 43 hours, exactly, our server will no longer be a honeypot, and that rootkit you wrote will take down Evil Corp. We did it Darlene. It's going to happen.
Despite what Lloyd might have said, rootkits are not serial rapists with very big dicks. They're malicious code designed to hide the presence of an attacker (inc. processes they might be running, alterations to system login and authentication modes to accept a backdoor credential) and their tools on a system once it has been compromised. Unqualified, the term "rootkit" commonly refers to kernel-mode rootkits, which operate directly within the context of the operating system, and frequently loaded through the same facilities provided for installing new device drivers. They can hide files/directories, running processes, network connections, and themselves (e.g. in the list of loaded drivers) from scanning entities on the same system. One way to detect a rootkit is to look for discrepancies between what tools on the system report (e.g. in terms of active network connections) versus what is observed externally (e.g. on a network monitoring device).
That makes the discussion of "honeypots" a little bit strange. A honeypot usually refers to a target on a network that's designed to be enticing to attackers, so that they try to hack it, but isn't "real" in the sense that it processes real data. It might be instrumented such that probing and reconnaissance activities targeting the honeypot are tied to network hacking alerts.
I can think of one of three interpretations of what turning server cs30 into a honeypot might mean:
  1. They've installed additional monitoring software on cs30.
  2. They've replaced cs30 with a totally different system that looks like cs30 to an outsider.
  3. They've installed additional network monitoring around cs30.
But none of these interpretations really make sense. If it's #1, if the rootkit was written properly, it's likely that additional monitoring would be fruitless, and the attack could be carried out without the whole Whiterose meeting riddles.
If it's #2, then the rootkit would probably not have been copied over to the clone, and fscociety would have noticed their server misbehaving. Unless, of course, E-Corp discovers the rootkit on cs30 as part of this process, in which case, they could have just cleaned it up, and closed off fsociety access to the internal server.
If it's #3, then the periodic use of the backdoored access to cs30 by fsociety should have been noticed by looking at that network monitoring data, likewise leading to a server cleanup and removal of the backdoor.
I'll chalk this up to somewhat cavalier and imprecise use of technical terminology by a TV show, and press on.
What have we learned so far?
In S01E09, after Tyrell coerces Elliot into showing him the fsociety arcade:
Tyrell: What is it that you're doing exactly?
Elliot: Encrypting all the files. All of Evil-Corp's financial records will be impossible to access. The encryption key will self-delete after the process completes.
Wait a second? Encryption? Encryption key? I thought we were after data deletion.
Of course, there's a perfectly plausible explanation: deleting data takes time. If you go around rm -rf'ing servers, there's a good chance that recoverable data will be scattered around those hosts. By performing bulk encryption, you overwrite all data on the target systems once, can still permit access to everything on the system while the encryption is occurring, and then destroy the key once the encryption process is completed. This lowers the length of the window in which someone can realize that something has gone terribly wrong. The key is small (tens of bytes, not to gigabytes or hundreds of gigabytes), and can be deleted almost instantaneously.
Several full disk encryption systems, including FileVault in macOS, and the now-defunct TrueCrypt have the ability to do this: you start encrypting the drive, but can continue working while the data is read, encrypted, and overwritten unnoticed in the background.
Some ransomware strains also follow this practice, so it's not an unreasonable approach. However, cryptography is a loaded foot cannon for the unwary, and it's surprisingly easy to make a small mistake that unravels the whole thing.
In S01E10, as Elliot looks for Tyrell at the E-Corp building, in voice-over he says:
A simple program: a worm that can make data unreadable. Malware that took Darlene maybe 2 hours to code. Is that all it takes to kill the world?
And follows with:
I wonder what stage they're at. Denial? Muttering to themselves "no, this can be fixed." Maybe bargaining? Forcing their techs to work overtime to try to decrypt our data. Or have they come to the realization yet that Darlene encrypted everything with 256-bit AES, and it would take an incomprehensible amount of time to crack? That all of their data is actually gone, for good.
AES is a symmetric encryption algorithm in wide use. It's stood the test of time since its standardization in 2000, and lots of people trying to find weaknesses in the last 2 decades. At a 256-bit key length, it would take many multiples of lifetimes of the universe to break, at least so long as computers are still made out of atoms. A quantum computer would not meaningfully assist in this kind of attack, as Grover's algorithm would still require 2128 quantum operations, and this is still going to take many multiplies of lifetimes of the universe to break.
But it does raise questions about cryptographic hygiene. Mechanically: what mode of operation is AES being used in to encrypt files? Let's assume Darlene has heard of the ECB penguin and has picked something better like CBC with per-file random initialization vectors.
More importantly: where is that key coming from? The right answer is to read it from a operating system provided cryptographically secure random number generator like /dev/urandom on UNIX-like systems, or the equivalent on Microsoft Windows CryptGenRandom. Ideally, perform this random key generation process individually (resulting in unique keys) on every single target system. There have been cases where CryptGenRandom has produced sub-par quality randomness on earlier versions of Windows, but not since Windows XP SP2 or older.
My theory is that this is where the fsociety worm went wrong.
In S02E01, we see the night of the hack for the first time, and in the terminal we see:
[email protected]:~# ssh -l root bkuw300ps345672-cs30.serverfarm.evil-corp-usa.com [email protected] password: The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usshare/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Thu May 8 16:26:57 2015 from cs30.serverfarm.evil-corp-usa.com [email protected]:~# cd /opt/2/task/2/fd1nfo/fsociety/hscripts/ [email protected]:/opt/2/task/2/fd1nfo/fsociety/hscripts# ls fuxsocy.py loadmod.py rootkitctrl sniff-out.pcap kernel_modules nuke.py sn1ff worm.py [email protected]:/opt/2/task/2/fd1nfo/fsociety/hscripts# ./fuxsocy.py 
And then:
Executing FuxSocy Loading Source of Entropy ####################### COMPLETE Generating Keys ####################### COMPLETE Locating target files. beginning crypto operations Encrypting /bin Encrypting /boot Encrypting /dev Encrypting /etc 
"Loading Source of Entropy" you say? That sounds awfully like a userspace random number generator. If the entropy pool is too small, or if the random number generation process is otherwise flawed, the key fed into the AES encryption process might be much more predictable than the 256-bit key length would suggest.
There was a major incident of this type discovered in 2006, where the Debian GNU/Linux package maintainers for OpenSSL (a popular, and widely used, though terrible) cryptography library commented out some lines that were generating code safety warnings when packaging it for the Debian distribution. Turns out these lines were essential to introducing any kind of real randomness for uses by the library, and this includes key generation and certain signing operations.
The fallout was that the affected versions of OpenSSL on Debian GNU/Linux would only generate 32,768 or 214 distinct keys. This also affected things like ECDSA signing, which was mirrored in 2013 when a similar vulnerability in Android led to the theft of about 56 Bitcoins.
You would have to know how the flawed key generation was implemented, and it would not necessarily be obvious looking at the keys from the outside, but if there was a flaw of this magnitude, you could break that "256-bit" key almost instantly with e.g. 14-bits of effort.
The use of Debian on the E-Corp servers might be a suggestive hint to this historical fiasco too.
The screen output also suggests that there might have been a single key generated at the start of the process that was copied as part of the data destruction payload to all of the E-Corp servers. Not ideal from a cryptographic hygiene standpoint.
In the post-credits scene of S02E12, Trenton and Mobley discuss:
Trenton: Have you given any more thought to what I said?
Mobley: I don't want to discuss this.
Trenton: Mobley...
Mobley: Fredrick.
Trenton: Seriously, Fredrick, what if we could? This might work.
Mobley: And also, it might not. I've taken enough risks for one lifetime, I don't want to discuss it anymore.
Trenton: But what if we could generate the keys...
Mobley: Tanya... will you just please shut up?
Trenton: What? This is important. We need to talk about it.
...
Trenton: Please, just look at it.
Mobley: Okay, so what? Say I did. Then what?
Trenton: If what I discovered is real, do you know what that means?
Mobley: Yeah, I know exactly what it means.
Trenton: Yeah, it means we could potentially undo this whole thing. Put everything back the way it was.
Mobley: I know. I know.
Trenton: Please. Just look at what I found.
I bet they've looked over the fsociety data destruction payload code and discovered a way to reproduce the key, precisely because there's this kind of flaw in it.
Finally, during Tyrell's AMA, a.k.a. S03E03, we get another shot of stage 1 running:
Thread #7 - 233 hosts online, initiating SCP transfer Waiting on thread updates ... Thread #2 - SCP complete. launched encryption tasks Thread #6 - SCP complete. launched encryption tasks Waiting on thread updates Thread #2 - Encryption tasks completed & verified Updating process log Thread #2 - Obtaining next hosts ... read 256 addresses Waiting on thread updates Thread #6 - SCP complete. launched encryption tasks Waiting on thread updates Thread #2 - Starting tasks on 10.0.0.29/24 
I interpret this as cs30 copying (via SCP) the data destruction payload to every server on the E-Corp network. The 10.0.0.0/8 IP addresses are designated internal network addresses, and are common for large internal business networks. It's odd that E-Corp would have a totally flat network, and also odd that cs30 itself seems to be copying the payload everywhere (not very worm-like), but perhaps this is just artistic license from the VFX guys.
Given how little we see of this screen, and how it was effective at wiping out E-Corp, I think it's safe to assume that the payload being transferred over SCP is both a propagator (i.e. the worm) and a data destruction payload, which would also address it spreading over the entire E-Corp network, even if it isn't flat. It is still suggestive of the single-key possibility though.
So, did Darlene fuck up the crypto? I think so. There's a few more suggestive quotes.
In S01E06, after dropping USB flash drives in the police parking lot for Elliot, the malware is blocked by antivirus.
Elliot: Did you write that exploit yourself?
Darlene: I had an hour.
Elliot: So what? You just pulled code from Rapid9 or some shit? Since when did you become a script kiddie?
Darlene: I repeat: I had an hour.
We learn that Darlene can be sloppy when doing things quickly, and re-iterating Elliot's voice-over in S01E10:
Malware that took Darlene maybe 2 hours to code.
And another off-hand remark in S01E08:
Elliot: How'd it go with the climate control hack?
Darlene: Handled. I happen to be really smart and good at things. Not like you give a shit.
There's a lot of ways that subtle faults in a cryptographic implementation can lead to the entire system coming tumbling down. Darlene might be an expert malware coder, but that's not a universal skill that necessarily translates over to other aspects of information security.
If you're curious about not falling into "bad noob practices" with crypto, there's a great set of cryptography building and breaking challenges that don't require much more than basic algebra, statistics, and coding skills.
Wildly speculating now:
submitted by DrElectolight to MrRobot [link] [comments]

Why is does it take so long to shut down an node used only as a JSON-RPC server?

I'm trying to sync a full node that will only be used as a JSON-RPC server (no mining). I tried to modify the config file and added a service unit, so that the node can run in a low-end VPS with minimum RAM and CPU capabilities. The problem is that the server takes too long to stop, and it's terminated by the system, so it always start rewinding blocks that have been already downloaded.
Here is my configuration file:
server=1 daemon=1 #debug=mempool debug=rpc # If run on the test network instead of the real bitcoin network # testnet=1 # You must set rpcuser and rpcpassword to secure the JSON-RPC api # Please make rpcpassword to something secure, `5gKAgrJv8CQr2CGUhjVbBFLSj29HnE6YGXvfykHJzS3k` for example. # Listen for JSON-RPC connections on  (default: 8332 or testnet: 18332) rpcuser=myuser rpcpassword=pypassword rpcport=8332 # Enable blocks pruning #prune=550 # Limit dbcache=50 maxconnections=4 rpcthreads=2 
And the service unit:
# It is not recommended to modify this file in-place, because it will # be overwritten during package upgrades. If you want to add further # options or overwrite existing ones then use # $ systemctl edit bitcoind.service # See "man systemd.service" for details. # Note that almost all daemon options could be specified in # /etc/bitcoin/bitcoin.conf [Unit] Description=Bitcoin daemon After=network.target [Service] ExecStart=/usbin/bitcoind -daemon=0 -datadir=/home/jsonrpc/bitcoin -conf=/home/jsonrpc/bitcoin/settings.conf ExecStop=/usbin/bitcoin-cli -datadir=/home/jsonrpc/bitcoin -conf=/home/jsonrpc/bitcoin/settings.conf stop # Creates /run/bitcoind owned by bitcoin #RuntimeDirectory=/home/jsonrpc/bitcoin WorkingDirectory=/home/jsonrpc/bitcoin User=jsonrpc Group=jsonrpc TimeoutStopSec=15m #CPUQuota=4% #MemoryLimit=128M #IOReadIOPSMax=10 #IOWriteIOPSMax=10 Type=simple #Restart=on-failure # Hardening measures #################### # Provide a private /tmp and /vatmp. PrivateTmp=true # Mount /usr, /boot/ and /etc read-only for the process. ProtectSystem=full # Disallow the process and all of its children to gain # new privileges through execve(). NoNewPrivileges=true # Use a new /dev namespace only populated with API pseudo devices # such as /dev/null, /dev/zero and /dev/random. PrivateDevices=true # Deny the creation of writable and executable memory mappings. # Commented out as it's not supported on Debian 8 or Ubuntu 16.04 LTS #MemoryDenyWriteExecute=true [Install] WantedBy=multi-user.target 
submitted by rraallvv to Bitcoin [link] [comments]

Headlines for week 06 of 2019

Listen to the Headlines for week 06

​Show notes for Security Endeavors Headlines for Week 5 of 2019
InfoSec Week 6, 2019 (link to original Malgregator.com posting)
The Zurich American Insurance Company says to Mondelez, a maker of consumer packaged goods, that the NotPetya ransomware attack was considered an act of cyber war and therefore not covered by their policy. According to Mondelez, its cyber insurance policy with Zurich specifically covered “all risks of physical loss or damage” and “all risk of physical loss or damage to electronic data, programs or software” due to “the malicious introduction of a machine code or instruction.” One would think that the language in the cyber insurance policy was specifically designed to be broad enough to protect Mondelez in the event of any kind of cyber attack or hack. And NotPetya would seem to fit the definition included in the cyber insurance policy – it was a bit of malicious code that effectively prevented Mondelez from getting its systems back up and running unless it paid out a hefty Bitcoin ransom to hackers. Originally, Zurich indicated that it might pay $10 million, or about 10 percent of the overall claim. But then Zurich stated that it wouldn't pay any of the claim by invoking a special “cyber war” clause. According to Zurich, it is not responsible for any payment of the claim if NotPetya was actually “a hostile or warlike action in time of peace or war.” According to Zurich, the NotPetya cyber attack originated with Russian hackers working directly with the Russian government to destabilize the Ukraine. This is what Zurich believes constitutes "cyber war." https://ridethelightning.senseient.com/2019/01/insurance-company-says-notpetya-is-an-act-of-war-refuses-to-pay.html
Reuters reports that hackers working on behalf of Chinese intelligence breached the network of Norwegian software firm Visma to steal secrets from its clients. According to investigators at cyber security firm Recorded Future, the attack was part of what Western countries said in December is a global hacking campaign by China’s Ministry of State Security to steal intellectual property and corporate secrets. Visma took the decision to talk publicly about the breach to raise industry awareness about the hacking campaign, which is known as Cloudhopper and targets technology service and software providers in order reach their clients.
https://www.reuters.com/article/us-china-cyber-norway-visma/china-hacked-norways-visma-to-steal-client-secrets-investigators-idUSKCN1PV141
A new vulnerability has been discovered in the upcoming 5G cellular mobile communications protocol. Researchers have described this new flaw as more severe than any of the previous vulnerabilities that affected the 3G and 4G standards. Further, besides 5G, this new vulnerability also impacts the older 3G and 4G protocols, providing surveillance tech vendors with a new flaw they can abuse to create next-gen IMSI-catchers that work across all modern telephony protocols.
This new vulnerability has been detailed in a research paper named "New Privacy Threat on 3G, 4G, and Upcoming5G AKA Protocols," published last year.
According to researchers, the vulnerability impacts AKA, which stands for Authentication and Key Agreement, a protocol that provides authentication between a user's phone and the cellular networks.The AKA protocol works by negotiating and establishing keys for encrypting the communications between a phone and the cellular network. Current IMSI-catcher devices target vulnerabilities in this protocol to downgrade AKA to a weaker state that allows the device to intercept mobile phone traffic metadata and track the location of mobile phones. The AKA version designed for the 5G protocol --also known as 5G-AKA-- was specifically designed to thwart IMSI-catchers, featuring a stronger authentication negotiation system But the vulnerability discovered last year allows surveillance tech vendors to create new models of IMSI-catchers hardware that, instead of intercepting mobile traffic metadata, will use this new vulnerability to reveal details about a user's mobile activity. This could include the number of sent and received texts and calls, allowing IMSI-catcher operators to create distinct profiles for each smartphone holder. https://www.zdnet.com/article/new-security-flaw-impacts-5g-4g-and-3g-telephony-protocols/
The Debian Project is recommending the upgrade of golang-1.8 packages after a vulnerability was discovered in the implementation of the P-521 and P-384 elliptic curves, which could result in denial of service and in some cases key recovery. In addition this update fixes two vulnerabilities in the “go get” command, which could result in the execution of arbitrary shell commands. https://www.debian.org/security/2019/dsa-4380
It is possible to trick user’s of the Evolution email application into trusting a phished mail via adding a forged UID to a OpenPGP key that has a previously trusted UID. It's because Evolution extrapolates the trust of one of OpenPGP key UIDs into the key itself. The attack is based on using the deficiency of Evolution UI when handling new identifiers on previously trusted keys to convince the user to trust a phishing attempt. More details about how the flaw works, along with examples are included in the article, which is linked in the show notes. Let’s take a minute to cover a bit of background on Trust Models and how validating identities work in OpenPGP and GnuPG:
The commonly used OpenPGP trust models are UID-oriented. That is, they are based on establishing validity of individual UIDs associated with a particular key rather than the key as a whole. For example, in the Web-of-Trust model individuals certify the validity of UIDs they explicitly verified.
Any new UID added to the key is appropriately initially untrusted. This is understandable since the key holder is capable of adding arbitrary UIDs to the key, and there is no guarantee that new UID will not actually be an attempt at forging somebody else's identity. OpenPGP signatures do not provide any connection between the signature and the UID of the sender. While technically the signature packet permits specifying UID, it is used only to facilitate finding the key, and is not guaranteed to be meaningful. Instead, only the signing key can be derived from the signature in cryptographically proven way.
GnuPG (as of version 2.2.12) does not provide any method of associating the apparent UID against the signature. In other words, from e-mail's From header. Instead, only the signature itself is passed to GnuPG and its apparent trust is extrapolated from validity of different UIDs on the key. Another way to say this is that the signature is considered to be made with a trusted key if at least one of the UIDs has been verified. https://dev.gentoo.org/~mgorny/articles/evolution-uid-trust-extrapolation.html
If you’re up for some heavy reading about manipulation and deceit being perpetrated by cyber criminals, it may be worth checking out a piece from buzzfeednews. It tells a woeful and dark tale that does not have a happy ending. A small excerpt reads: “As the tools of online identity curation proliferate and grow more sophisticated, so do the avenues for deception. Everyone’s familiar with the little lies — a touch-up on Instagram or a stolen idea on Twitter. But what about the big ones? Whom could you defraud, trick, ruin, by presenting false information, or information falsely gained? An infinite number of individual claims to truth presents itself. How can you ever know, really know, that any piece of information you see on a screen is true? Some will find this disorienting, terrifying, paralyzing. Others will feel at home in it. Islam and Woody existed purely in this new world of lies and manufactured reality, where nothing is as it seems.” https://www.buzzfeednews.com/article/josephbernstein/tomi-masters-down-the-rabbit-hole-i-go
Security researchers were assaulted by a casino technology vendor Atrient after responsibly disclosed critical vulnerabilities to them. Following a serious vulnerability disclosure affecting casinos globally, an executive of one casino technology vendor Atrient has allegedly assaulted the security researcher who disclosed the vulnerability at the ICE conference in London. The article covers the story of a vulnerability disclosure gone bad, one involving the FBI, a vendor with a global customer base of casinos and a severe security vulnerability which has gone unresolved for four months without being properly addressed. https://www.secjuice.com/security-researcher-assaulted-ice-atrient/
Article 13, the new European Union copyright law is back and it got worse, not better. In the Franco-German deal, Article 13 would apply to all for-profit platforms. Upload filters must be installed by everyone except those services which fit all three of the following extremely narrow criteria:
Available to the public for less than 3 years Annual turnover below €10 million Fewer than 5 million unique monthly visitors Countless apps and sites that do not meet all these criteria would need to install upload filters, burdening their users and operators, even when copyright infringement is not at all currently a problem for them. https://juliareda.eu/2019/02/article-13-worse/
Researchers from Google Project Zero evaluated Apple's implementation of Pointer Authentication on the A12 SoC used in the iPhone XS. There are bypasses possible, but the conclusion says it is still a worthwhile exploitation mitigation technique. Among the most exciting security features introduced with ARMv8.3-A is Pointer Authentication, a feature where the upper bits of a pointer are used to store a Pointer Authentication Code (PAC), which is essentially a cryptographic signature on the pointer value and some additional context. Special instructions have been introduced to add an authentication code to a pointer and to verify an authenticated pointer's PAC and restore the original pointer value. This gives the system a way to make cryptographically strong guarantees about the likelihood that certain pointers have been tampered with by attackers, which offers the possibility of greatly improving application security. There’s a Qualcomm white paper which explains how ARMv8.3 Pointer Authentication was designed to provide some protection even against attackers with arbitrary memory read or arbitrary memory write capabilities. It's important to understand the limitations of the design under the attack model the author describes: a kernel attacker who already has read/write and is looking to execute arbitrary code by forging PACs on kernel pointers.
Looking at the specification, the author identifies three potential weaknesses in the design when protecting against kernel attackers with read/write access: reading the PAC keys from memory, signing kernel pointers in userspace, and signing A-key pointers using the B-key (or vice versa). The full article discusses each in turn. https://googleprojectzero.blogspot.com/2019/02/examining-pointer-authentication-on.html
There is a dangerous, remote code execution flaw in the LibreOffice and OpenOffice software. While in the past there have been well documented instances where opening a document would result in the executing of malicious code in paid office suites. This time LibreOffice and Apache’s OpenOffice are the susceptible suites. The attack relies on exploiting a directory traversal flaw, identified as CVE-2018-16858, to automatically execute a specific python library bundled within the software using a hidden onmouseover event. To exploit this vulnerability, the researcher created an ODT file with a white-colored hyperlink (so it can't be seen) that has an "onmouseover" event to trick victims into executing a locally available python file on their system when placing their mouse anywhere on the invisible hyperlink. According to the researcher, the python file, named "pydoc.py," that comes included with the LibreOffice's own Python interpreter accepts arbitrary commands in one of its parameters and execute them through the system's command line or console. https://thehackernews.com/2019/02/hacking-libreoffice-openoffice.html
Nadim Kobeissi is discontinuing his secure online chat Cryptocat. The service began in 2011 as an experiment in making secure messaging more accessible. In the eight ensuing years, Cryptocat served hundreds of thousands of users and developed a great story to tell. The former maintainer explains on the project’s website that other life events have come up and there’s no longer available time to maintain things. The coder says that Cryptocat users deserve a maintained secure messenger, recommends Wire.
The Cryptocat source code is still published on GitHub under the GPL version 3 license and has put the crypto.cat domain name up for sale, and thanks the users for the support during Cryptocat's lifetime. https://twitter.com/i/web/status/1092712064634753024
Malware For Humans is a conversation-led, independent documentary about fake news, big data, electoral interference, and hybrid warfare. Presented by James Patrick, a retired police officer, intelligence analyst, and writer, Malware For Humans covers the Brexit and Trump votes, the Cambridge Analytica scandal, Russian hybrid warfare, and disinformation or fake news campaigns.
Malware For Humans explains a complex assault on democracies in plain language, from hacking computers to hacking the human mind, and highlights the hypocrisy of the structure of intelligence agencies, warfare contractors, and the media in doing so. Based on two years of extensive research on and offline, Malware For Humans brings the world of electoral interference into the light and shows that we are going to be vulnerable for the long term in a borderless, online frontier. A complete audio companion is available as a separate podcast, which can be found on iTunes and Spotify as part of The Fall series and is available for free, without advertisements. https://www.byline.com/column/67/article/2412
Security Endeavors Headlines is produced by SciaticNerd & Security Endeavors with the hope that it provides value to the wider security community. Some sources adapted for on-air readability.
Special thanks to our friends at malgregator dot com, who allow us to use their compiled headlines to contribute to show’s content. Visit them at Malgregator.com.
Additional supporting sources are also be included in our show notes
More information about the podcast is available at SecurityEndeavors.com/SEHL
Thanks for listening and we'll see you next week!
submitted by SecurityEndeavors to SEHL [link] [comments]

Electrum will be in the next Ubuntu release in ~1 month. Please help test it now.

Hello, I am magicfab posting from the Bitcoin Embassy account.
Yesterday I shared here why I thought it was excellent news that Electrum was recently made available to all Debian GNU/Linux users and its derivatives and how it was so recent that it had missed the time window to be included automatically in one of its derivatives, Ubuntu.
I filed a bug report to make an exception and include electrum in Ubuntu now instead of waiting another 6 months, and it was quickly accepted. The package is already available for testing. Don't download it directly! If you're using Ubuntu 13.10 already you can search for electrum with your package manager or just sudo apt-get install electrum.
This is the ideal time to install Ubuntu 13.10 and test its functionality and this includes Electrum. Ubuntu "Saucy Salamander" is still in beta, and beta freeze is today. For all intents and purposes, the beta version is very close to what will be released in ~1 month, stable enough to use daily, and specially to test and file important bugs reports. If you find a bug in Ubuntu for Electrum or Debian, this is an excellent time to report it.
As the Chief Ambassador here at the Bitcoin Embassy, this is one of the more technical aspects in my role of Bitcoin advocacy that I believe is important to help with. If anyone files a bug report, has similar ideas or other technical requests regarding use of Bitcoin with free open source software / operating systems, PM me at magicfab or Bitcoin_Embassy.
tl;dr: Electrum will be in the final Ubuntu 13.10 release :) PM me if you have technical suggestions/requests related to Bitcoin + free software.
submitted by Bitcoin_Embassy to Bitcoin [link] [comments]

[Reupload][Tutorial] Install Armory Wallet 0.96.4 on Fedora Workstation 29

note: I had to reupload this because reddit is banning my original account for no reason. I appealed but I thought maybe someone wanted to have this content online.
Armory is a very cool open source bitcoin wallet for the power user. You can do neat things with it, read here: https://www.bitcoinarmory.com/
Disclaimer: follow these steps at your own risk. I am not responsible for any damage / loss of funds you might face for following or not following correctly my instructions here. I may have made a typo somewhere or be wrong so do your own research and learn for yourself what I am doing at each step, and what consequences may have for you, at your own risk. These instructions may be wrong somewhere. It worked for me, it doesn't mean it has to work for you.
Requirements for this tutorial:
We are going to build the code from source.
Install dependencies.
I followed these instructions to find the equivalent Fedora packages:
Open the terminal app and run this command:
sudo dnf install git nano qt qt-devel python-devel libtool pyqt4 pyqt4-devel lmdb swig 
And more python packages that I had to install:
sudo pip install twisted qt4reactor psutil 
Importing the signing key to verify the software
Install KGPG to easily manage keys.
sudo dnf install kgpg 
Go to
https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x8C5211764922589A
and copy paste the code below the title from
-----BEGIN PGP PUBLIC KEY BLOCK-----
to
-----END PGP PUBLIC KEY BLOCK-----
both included. Then open KGPG from terminal with
kgpg -k 
and click 'Import Key...' > Clipboard > Ok . You should see a confirmation message. Double check the info and close the dialog.
Repeat the process with this other key:
https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xA4FC919E85C595BA
You can verify both keys are mentioned at the Armory webpage.
Clone and compile the code plus some edits
Before, we installed some dependencies that are named differently than the equivalent Ubuntu/Debian package specified at the Armory documentation. The build process fails for Fedora as the name for the dependency during checks won't match the Fedora version. There's this pull request addressing that, but the code is not part of any release yet.
So the fastest workaround (maybe a bit dirty) was to edit the build config file and correct the name for my Fedora install. Let's begin.
Clone the Armory repository
git clone https://github.com/goatpig/BitcoinArmory.git 
Enter the BitcoinArmory dir
cd BitcoinArmory 
Switch to release code
git checkout 'v0.96.4' 
Verify commit signature
git tag -v 'v0.96.4' 
you should see the following message:
> object fee1f91a3137ef1056e15cc606a186b0e508f84c > type commit > tag v0.96.4 > tagger goatpig  1522530739 +0200 > > v0.96.4 > gpg: Signature made Sat 31 Mar 2018 11:12:19 PM CEST > gpg: using RSA key 8C5211764922589A > gpg: Good signature from "goatpig (Offline signing key for Armory releases) " > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the owner. > Primary key fingerprint: 745D 707F BA53 968B DF63 AA8D 8C52 1176 4922 589A 
if it looks the same, everything is ok.
Edit the file 'Makefile' file with
gedit Makefile 
And click the three dot menu > Find and Replace...
Configure the options as follows:
https://i.imgur.com/hpS01Kd.png
Click Replace All and close.
Go back to the terminal and run the following commands in order from inside the BitcoinArmory dir. Wait for the previous one to finish before running the next one:
./autogen.sh 
...
./configure 
...
make 
if everything finishes without error you are all done! Run this to start Armory:
python ./ArmoryQt.py 
you are all set. Please let me know if I missed something.
submitted by RedditShadowbangedMe to Bitcoin [link] [comments]

bitcoin daemon service gets stuck in the command-line

I modified bitcoin.service like follows
# It is not recommended to modify this file in-place, because it will # be overwritten during package upgrades. If you want to add further # options or overwrite existing ones then use # $ systemctl edit bitcoind.service # See "man systemd.service" for details. # Note that almost all daemon options could be specified in # /etc/bitcoin/bitcoin.conf [Unit] Description=Bitcoin daemon After=network.target [Service] ExecStart=/usbin/bitcoind -daemon -datadir=/home/deploy/.bitcoin -conf=/home/deploy/.bitcoin/bitcoin.conf -pid=/run/bitcoind.pid # Creates /run/bitcoind owned by bitcoin RuntimeDirectory=bitcoind User=deploy Group=deploy Type=forking PIDFile=/run/bitcoind.pid Restart=on-failure # Hardening measures #################### # Provide a private /tmp and /vatmp. PrivateTmp=true # Mount /usr, /boot/ and /etc read-only for the process. ProtectSystem=full # Disallow the process and all of its children to gain # new privileges through execve(). NoNewPrivileges=true # Use a new /dev namespace only populated with API pseudo devices # such as /dev/null, /dev/zero and /dev/random. PrivateDevices=true # Deny the creation of writable and executable memory mappings. # Commented out as it's not supported on Debian 8 or Ubuntu 16.04 LTS #MemoryDenyWriteExecute=true [Install] WantedBy=multi-user.target 
so that the settings and data are kept under the user deploy's home directory, the only problem is that when I run the command to start the service, it gets stuck as if it wasn't running in daemon mode. Then I have to enter CTR-C to get the command prompt again.
$ sudo systemctl start bitcoind ^C $ sudo systemctl status bitcoind ● bitcoind.service - Bitcoin daemon Loaded: loaded (/lib/systemd/system/bitcoind.service; disabled; vendor preset: enabled) Active: activating (start) since Thu 2018-10-04 01:45:26 CEST; 25s ago Process: 51145 ExecStart=/usbin/bitcoind -daemon -datadir=/home/deploy/.bitcoin -conf=/home/deploy/.bitcoin/bitcoin.conf -pid=/run/bitcoind.pid (code=exited, status=0/SUCCESS) Tasks: 12 Memory: 578.0M CPU: 14.100s CGroup: /system.slice/bitcoind.service └─51147 /usbin/bitcoind -daemon -datadir=/home/deploy/.bitcoin -conf=/home/deploy/.bitcoin/bitcoin.conf -pid=/run/bitcoind.pid Oct 04 01:45:26 host systemd[1]: Starting Bitcoin daemon... Oct 04 01:45:26 host systemd[1]: bitcoind.service: PID file /run/bitcoind.pid not readable (yet?) after start: No such file or directory 
submitted by rraallvv to Bitcoin [link] [comments]

[Tutorial] Install Armory Wallet 0.96.4 on Fedora Workstation 29

Armory is a very cool open source bitcoin wallet for the power user. You can do neat things with it, read here: https://www.bitcoinarmory.com/
Disclaimer: follow these steps at your own risk. I am not responsible for any damage / loss of funds you might face for following or not following correctly my instructions here. I may have made a typo somewhere or be wrong so do your own research and learn for yourself what I am doing at each step, and what consequences may have for you, at your own risk. These instructions may be wrong somewhere. It worked for me, it doesn't mean it has to work for you.
Requirements for this tutorial:
We are going to build the code from source.
Install dependencies.
I followed these instructions to find the equivalent Fedora packages:
Open the terminal app and run this command:
sudo dnf install git nano qt qt-devel python-devel libtool pyqt4 pyqt4-devel lmdb swig 
And more python packages that I had to install:
sudo pip install twisted qt4reactor psutil 
Importing the signing key to verify the software
Install KGPG to easily manage keys.
sudo dnf install kgpg 
Go to
https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x8C5211764922589A
and copy paste the code below the title from
-----BEGIN PGP PUBLIC KEY BLOCK-----
to
-----END PGP PUBLIC KEY BLOCK-----
both included. Then open KGPG from terminal with
kgpg -k 
and click 'Import Key...' > Clipboard > Ok . You should see a confirmation message. Double check the info and close the dialog.
Repeat the process with this other key:
https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xA4FC919E85C595BA
You can verify both keys are mentioned at the Armory webpage.
Clone and compile the code plus some edits
Before, we installed some dependencies that are named differently than the equivalent Ubuntu/Debian package specified at the Armory documentation. The build process fails for Fedora as the name for the dependency during checks won't match the Fedora version. There's this pull request addressing that, but the code is not part of any release yet.
So the fastest workaround (maybe a bit dirty) was to edit the build config file and correct the name for my Fedora install. Let's begin.
Clone the Armory repository
git clone https://github.com/goatpig/BitcoinArmory.git 
Enter the BitcoinArmory dir
cd BitcoinArmory 
Switch to release code
git checkout 'v0.96.4' 
Verify commit signature
git tag -v 'v0.96.4' 
you should see the following message:
> object fee1f91a3137ef1056e15cc606a186b0e508f84c > type commit > tag v0.96.4 > tagger goatpig  1522530739 +0200 > > v0.96.4 > gpg: Signature made Sat 31 Mar 2018 11:12:19 PM CEST > gpg: using RSA key 8C5211764922589A > gpg: Good signature from "goatpig (Offline signing key for Armory releases) " > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the owner. > Primary key fingerprint: 745D 707F BA53 968B DF63 AA8D 8C52 1176 4922 589A 
if it looks the same, everything is ok.
Edit the file 'Makefile' file with
gedit Makefile 
And click the three dot menu > Find and Replace...
Configure the options as follows:
https://i.imgur.com/hpS01Kd.png
Click Replace All and close.
Go back to the terminal and run the following commands in order from inside the BitcoinArmory dir. Wait for the previous one to finish before running the next one:
./autogen.sh 
...
./configure 
...
make 
if everything finishes without error you are all done! Run this to start Armory:
python ./ArmoryQt.py 
you are all set. Please let me know if I missed something.
edit: cd git dir.
submitted by AmbitiousSpeed0 to Bitcoin [link] [comments]

Unix & Linux: Debian package's files authentication - YouTube Debian Package of the Day S02E15 - #35 - dateutils Debian: What are these files in /sys/devices/pci0000:00 ... Idiomatic location for file based sockets on Debian ... BITTRAIN  How To Buy Packages  Investing  Part 2

Older debian systems that are missing the dh-systemd package, will fail to build the packages, yes. I believe the (supported) Debian/Ubuntu versions that are affected by this, are Debian 7 (LTS version is EOL at the end of May 2018) and Ubuntu 14.04 LTS (EOL in April 2019). Package: bitcoin. 0.18.1~dfsg-1.2 (main) [sid] ; Browse by prefix: 0 2 3 4 6 7 8 9 a b c d e f g h i j k l lib-lib3 liba libb libc libd libe libf libg libh libi libj ... This package provides Bitcoin Core tool Bitcoin-Qt, a graphical user interface for Bitcoin. Bitcoin (₿) is the world's first cryptocurrency, a form of electronic cash sent peer-to-peer without the need for a financial intermediary. Bitcoin Core is the reference implementation of Bitcoin. Beware that unless pruning is enabled, full global transaction history is stored locally at each client ... Litecoin source tree. Contribute to litecoin-project/litecoin development by creating an account on GitHub. vcswatch reports that the current version of the package is not in its VCS. Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be ...

[index] [50478] [23560] [35027] [30472] [40849] [50109] [19099] [16209] [34643] [23372]

Unix & Linux: Debian package's files authentication - YouTube

Package Management on Ubuntu/Debian/Linux Mint - Duration: 50 ... THE BITCOIN BULLISH DIVERGENCE THAT NO ONE IS TALKING ABOUT!!! - Duration: 14:01. The Moon Recommended for you. New; 14:01 ... This company deals in BITCOIN exchanges and Cryptocurrency exchanges as well as FOREX trading and REAL ESTATE investments And in this video i am showing you how to buy packages in Bittrain To make ... Unix & Linux: Debian package's files authentication Helpful? Please support me on Patreon: https://www.patreon.com/roelvandepaar With thanks & praise to God,... Welcome to Debian Package of the Day, where we take a look at a package from the Debian archives. In today's edition we take a look at dateutils, a set of tools that can make life much easier when ... Unix & Linux: How to find out which (not installed) Debian package a file belongs to? Helpful? Please support me on Patreon: https://www.patreon.com/roelvand...

#