Gregarius » BetaNews.Com » juin 13, 2015

Canaux

108375 éléments (108375 non lus) dans 10 canaux

Actualités (48730 non lus)

• 01net. Actualités (48730 non lus)

Hoax (65 non lus)

• Top dix quotidien Sophos des canulars (65 non lus)

Logiciels (39066 non lus)

• BetaNews.Com (34382 non lus)
• Presence PC - Actualité Logiciels, jeux vidéos (3551 non lus)
• LeMondeInformatique.fr : Actualités Applications (1133 non lus)

Sécurité (1668 non lus)

• Actualités Sécurité Informatique (406 non lus)
• Les Nouvelles.net : sécurité informatique. (1262 non lus)

Referencement (18846 non lus)

• Secrets2moteurs (11746 non lus)
• Referencement Google WebRankInfo (2255 non lus)
• Abondance (4845 non lus)

BetaNews.Com (3 non lus)

• 

  How to sideload apps in Windows 10

  Publié: juin 13, 2015, 7:39pm CEST par Mark Wilson

  

  The sideloading of apps is something that most people associate with smartphones and tablets. If you want to install unofficial apps on your iPhone, Android, or Windows Phone handset, there are things you can do to make this possible. The same is true with Windows 10 assuming you are using build 10122 or newer.

  If you want to be able to install apps that are not featured in the Store, all you need to do is enable Developer Mode. As the name would suggest, this is something that will be of particular interest to developers as it makes it possible for them to test out their own apps before they hit the store, but there's nothing to stop anyone from enabling the mode to take advantage of the same feature. Here's what you need to do.

  These days, there is no need to mess about the registry or Group Policy Editor -- everything can be handled from within Settings. Open Settings from the Start menu and then click Updates & Security. Move to the For Developers section and select the option labelled "Sideload apps". Windows 10 likes to hold your hand, so you'll be warned that sideloading is potentially dangerous; just click Yes to continue if you're happy to take the risk. If you prefer, you can enable Developer Mode rather than just enabling sideloading -- this unlocks a few extra options as well. If you change your mind at any time, you can easy switch back to regular mode by selecting the "Don’t use developer features" option.

  And that's pretty much all there is to it. With either of these settings selected, you'll now be able to download Windows apps from other sources and install them even though they are not featured in the Windows Store.

  Photo credit: wavebreakmedia / Shutterstock

  
• 

  Wikimedia secures connections with HTTPS encryption by default

  Publié: juin 13, 2015, 6:23pm CEST par Mark Wilson

  

  There is a movement calling for the encryption of all web traffic. The cause of this could be laid at Edward Snowden's door, but there's no getting away from the fact that in recent years there is an increased interest in security and privacy. To this end, Wikimedia has announced that it is now using HTTPS to encrypt all of its traffic -- including that to Wikipedia.

  We've already seen the US government embrace HTTPS, and companies like Google and Facebook are making it easier to control privacy settings. Apple has hit out at companies that fail to do enough to protect users' privacy, and Wiki media is taking the extra step of also implementing HSTS, just days after Microsoft announced that this would be supported by Internet Explorer 11 under Windows 7 and 8.1.

  There has long been the option of accessing the likes of Wikipedia with an HTTPS connection, but the difference now is that encryption is enabled by default. This means that for people accessing Wikimedia sites in certain parts of the world, it will now be much harder for snooping governments to monitor activity; it also makes it more difficult for ISPs to censor content.

  Writing on the Wikimedia blog, the foundation said:

  To be truly free, access to knowledge must be secure and uncensored. At the Wikimedia Foundation, we believe that you should be able to use Wikipedia and the Wikimedia sites without sacrificing privacy or safety. Today, we’re happy to announce that we are in the process of implementing HTTPS to encrypt all Wikimedia traffic. We will also use HTTP Strict Transport Security (HSTS) to protect against efforts to ‘break’ HTTPS and intercept traffic.

  The foundation says that the move has been made in response to increased concerns about government surveillance. The switch to encryption-by-default meant updating not only site code, but also server hardware. The final stages have now been reached, and should be completed within a couple of weeks.

  Photo credit: Evan Lorne / Shutterstock.com

  
• 

  Amazon publishes opaque transparency report

  Publié: juin 13, 2015, 12:54pm CEST par Mark Wilson

  

  Post-Snowden there is great interest in just what involvement the government has with technology firms. There are frequent requests from government agencies for information about users and the likes of Google, Snapchat, and even the NSA itself have all released transparency reports that reveal, in broad strokes, the number of requests for data they have received.

  Amazon is the latest company to release a transparency report -- although the term really should be used in the loosest possible sense. The report includes scant details about the number of subpoenas, search warrants, court orders, and national security requests received in the first five months of 2015. The report is so vague as to be virtually meaningless.

  As with other transparency reports, the level of detail provided is a disappointing. For each type of request we are simply told how many requests were received, and how many were complied with, partially complied with, or not responded to. There is no breakdown of which areas of Amazon's operation have been the subjects of interest -- the report makes no indication how many of the data requests relate to cloud storage service, and which to retail, for instance.

  The title of 'transparency report' remains something of a misnomer, particularly when it comes to revealing information about national security data requests. Here we are not even privy to precise numbers; we're told nothing more than the fact that between 0 and 256 requests were received. No information is provided about the responses given.

  Amazon's Stephen Schmidt said:

  Amazon does not disclose customer information unless we’re required to do so to comply with a legally valid and binding order. Unless prohibited from doing so or there is clear indication of illegal conduct in connection with the use of Amazon products or services, Amazon notifies customers before disclosing content information.

  Where we need to act publicly to protect customers, we do. Amazon never participated in the NSA’s PRISM program. We have repeatedly challenged government subpoenas for customer information that we believed were overbroad.

  For what they are worth, here are the figures Amazon has shared:

  Subpoenas received: 813
  How Amazon responded:
  Full response: 542
  Partial response: 126
  No response: 145

  Search warrants received: 25
  How Amazon responded:
  Full response: 13
  Partial response: 8
  No response: 4

  Other court orders received: 13
  How Amazon responded:
  Full response: 4
  Partial response: 5
  No response: 4

  National security requests received: 0-249

  Non-U.S. requests received: 132
  How Amazon responded:
  Full response: 108
  Partial response: 7
  No response: 17

  Removal requests received: 1
  How Amazon responded:
  Full response: 1
  Partial response: 0
  No response: 0

  The next transparency report is expected at the end of 2015 or beginning of 2016.

  Photo credit: Ken Wolter / Shutterstock