Install apt-fast on Debian-based Linux

Configure apt-fast

• Debian: http://www.debian.org/mirror/list
• Ubuntu: https://launchpad.net/ubuntu/+archivemirrors

MIRRORS=('http://ftp.us.debian.org/debian/,http://carroll.aset.psu.edu/pub/linux/distributions/debian/,http://debian.gtisc.gatech.edu/debian/,http://debian.lcs.mit.edu/debian/,http://mirror.cc.columbia.edu/debian/')

MIRRORS=('http://us.archive.ubuntu.com/ubuntu,http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/,http://mirror.cc.vt.edu/pub2/ubuntu/,http://mirror.umd.edu/ubuntu/,http://mirrors.mit.edu/ubuntu/')

Install a Package with apt-fast

apt-fast [apt-get options and arguments]
apt-fast [aptitude options and arguments]
apt-fast { { install | upgrade | dist-upgrade | build-dep | download  | source  } [ -y | --yes | --assume-yes | --assume-no ]   ... | clean }

How Fast is apt-fast?

Install Scrot on Linux

Take Screenshots with Scrot

1. Take a screenshot of the entire desktop

2. Take a screenshot of a particular window or a rectangular region

3. Take a delayed screenshot

4. Adjust quality of a screenshot

5. Adjust the size of a screenshot

6. Pipeline a captured screenshot to another command

Apple has squashed a significant security bug in its SSL engine for iOS and OS X as part of a slew of patches for iThings and Macs.

The so-called "triple handshake" flaw quietly emerged yesterday amid panic over OpenSSL's Heartbleed vulnerability, and soon after the embarrassing "goto fail" blunder in iOS and OS X.

Apple's "triple handshake" bug [CVE-2014-1295, advisory] is unrelated to Heartbleed, and nothing like as serious, according to security experts. For one thing, Heartbleed is a problem in OpenSSL versions 1.0.1 to 1.0.1f, whereas Apple uses its own implementation of SSL/TLS, called Secure Transport, and provides an older OpenSSL library just in case.

"Apple ships with OpenSSL 0.9.8, a version that is not affected by Heartbleed," confirmed Wolfgang Kandek, CTO at cloud security firm Qualys, in a blog post.

Matthew Green, a professor of computer science who teaches cryptography at Johns Hopkins University in Maryland, US, commented: "The SSL patch in the new Apple update fixes a subtle issue with client authentication. Not too terrifying."

What is a triple-handshake vulnerability?
In Apple's words, the bug can be exploited thus:

In a 'triple handshake' attack, it was possible for an attacker to establish two connections which had the same encryption keys and handshake, insert the attacker's data in one connection, and renegotiate so that the connections may be forwarded to each other.
To prevent attacks based on this scenario, Secure Transport was changed so that, by default, a renegotiation must present the same server certificate as was presented in the original connection.

This vulnerability was assigned CVE-2014-1295 on 8 January, 2014, and is linked to the triple handshake design flaws in the SSL/TLS protocol that were publicly documented in early March by Karthikeyan Bhargavan, Antoine Delignat-Lavaud, Cedric Fournet, Alfredo Pironti and Pierre-Yves Strub (see Register passim).

Apple was privately warned of the vulnerabilities by the aforementioned researchers on 10 January, we're told. Yesterday's security update for Secure Transport "fixes renegotiation and header truncation issues", according to the triple-handshake team; the iPhone maker duly credited the Paris-based researchers in its advisory this week.

"To summarize the attacks briefly, if a TLS client connects to a malicious server and presents a client credential, the server can then impersonate the client at any other server that accepts the same credential," the team wrote on its website about the problem back in March.

In the case of the buggy Secure Transport, a miscreant with access to a router or dodgy Wi-Fi point can sit between, say, a web browser and a HTTPS web server, and potentially read web pages that should otherwise be fully encrypted between the pair, or inject malicious JavaScript into the pages. HTTPS relies on SSL/TLS to protect data in transit from eavesdroppers and tamperers.

(It's worth noting that the developers behind Chrome, Opera, Android, Firefox, and Internet Explorer were also notified of triple-handshake flaws in their software – some as early as October – and have patched, or are patching, accordingly. OpenSSL is "not directly affected", said the researchers.)

OS X update roundup
Apple published updates for Mac OS X 10.7 (Lion), 10.8 (Mountain Lion) and 10.9 (Mavericks) on Tuesday: these tackle a JPEG handling flaw in Mavericks that poses a code injection risk, and a format string issue in the URL handling that poses an identical type of remote-code exception threat in Mac OS X 10.9. Another patch tackles a PDF font parsing vulnerability that can be exploited by hackers to run malware on Mac OS X 10.8 machines.

Lastly, on the desktop front, there're patches for a lesser sandbox escape vulnerability in 10.8 (Mountain Lion) and 10.9 (Mavericks).

Apple also published a new version of iOS, namely version 7.1.1, that addresses some of the same issues. These various updates to Apple's computer and smartphone software, which include performance tweaks, are covered in greater depth.



source

Verdict

I experienced issues connecting my smartphone to my Windows 7 PC ever since I replaced my Samsung Galaxy Note II with the Motorola Moto G.

Nothing happened whenever I plugged the USB cable in and connect the phone to it. The workaround that I came up with was to open Devices and Printers, right-click on the device, select troubleshoot, and wait until Windows would install the required drivers on the system.

The strange thing was that I had to do so each time and not only once. When I checked the phone's properties with a right-click, it would list "Windows cannot initialize the device driver for this hardware. (Code 37)" as the device status.

A search on the Internet reveals hundreds if not thousands of pages with workarounds and fixes for the solution, and users who can't get these fixes to work on their system.

Common suggestions include uninstalling drivers, deleting UpperFilters and LowerFilters Registry values, using System Restore, or uninstalling all USB devices.

If you are unlucky, you land on a page that is trying to sell you a software to fix those errors on your system.

While I cannot claim that the following method works for all devices the error is displayed for, it worked for my situation. It fixed the issue that I was experiencing and resulted that the phone was detected properly whenever I connected it to the PC.

Solution

All I did was install the device driver offered by Motorola for the Moto G. There is a downside to that but more about that later. Once installed, the Moto G was detected properly by the PC so that I was able to transfer files or back up data on it.

Now, the downside is that Motorola's Device Manager needs to run in the background for that to work which is not ideal.

There is another solution, one that is not that obvious as it can be overlooked easily. Here is what you need to do:

1. Open the Devices and Printers module of the Control Panel. Tap on the Windows-key, type devices and printers, and select the result from the listing.

2. Right-click on the device that is not detected properly and select the troubleshoot option.

3. Windows attempts to find a solution for the issue and displays it afterwards. In this case, it displays an option to reinstall the device driver. Select apply this fix from the available options.

4. The next page is the important one. If you just click next on "allow driver updates to be installed", you will only fix the issue for the current session but not permanently.

You need to click on view and change settings to fix it once and for all.

5. On the next page, switch from "never install driver software from Windows Update" to "Yes, do this automatically (recommended)".

6. Save the changes and click next on the page. Windows will then display the troubleshooting results. If everything went well, all issues displayed should be listed as fixed.

Closing Words

If you are experiencing error code 37 issues in Windows when connecting devices via USB, you may want to try the troubleshooting option first as it offers the best result when it works.

If that does not work, download and install the latest drivers for the device from the manufacturer website.

Summary

Article Name

How to fix "Windows cannot initialize the device driver for this hardware. (Code 37)"

Author

Martin Brinkmann

Description

The guide provides you with two options to fix error code 37 messages in Windows. The error code is used by the operating system if devices connected via USB are not functioning correctly.

Two hackers claim to have discovered a way to bypass Apple's "Activation Lock," an iCloud security feature that locks ill-intentioned individuals out of lost or stolen iOS devices.

On Wednesday, Dutch newspaper De Telegraaf first broke the news about the Activation Lock bypass, which was accomplished by two individuals who go by the handles “AquaXetine” and “MerrukTechnolog” on Twitter.

AquaXetine confirmed that, via a man-in-the-middle (MitM) attack, the duo was able to unlock an iPhone 4 by getting the device to communicate with their server, as opposed to Apple's servers. From there, the two claimed to have replicated the bypass on thousands more Apple devices.

Throughout the week, Apple users took to Twitter to post about their own successful attempts at unlocking devices using the technique.

According to an Apple support page, Activation Lock is a relatively new feature included in “Find My iPhone,” which requires users to login with their Apple ID and password before allowing them to erase and reactivate the device, sign out of iCloud on the device, or disable “Find my iPhone.”

AquaXetine later told that the Activation Lock bypass could open users to a myriad of data security concerns, if an intruder was able to get into a device that hadn't yet been wiped.

“If the device is not wiped, and someone has physical access to it, they can do more than [bypass the lock],” AquaXetine wrote. “[They] can take your [Apple] ID, very important information, and make purchases with your [stored] credit card information. All your data would will be in the wrong hands.”

The two hackers reached out to Apple in late March about the security issue, but received no response from the company.



source