netscapes

youtube

Applicat Spectra「インスピレーション」 (by asketch)

This is one of the new songs from Applicat Spectra!! I am very very very grateful that they finally release something new!! (>o<)/~~~ because I miss them soooo much!! <3

PS.
There’s still no announcement that this is their new single/album. It’s just a new song. (^ ^“)

vimeo

NETSCAPES

Netscapes, by Garrett Lynch, is an automated application that uses live feeds from networked webcams to create combined and imagined landscape compositions: networked landscapes. The application does this by employing a technique called web scraping where data is retrieved from websites and presented elsewhere. Unlike standard web scraping, however, Netscapes does not retrieve textual data. Instead it retrieves imagery and considers the network as an augmented lens, an extension of our vision as a means to see distant places. Have a look at all the netscapes here.

vimeo

Netscapes, 2011
Artist: Garrett Lynch
Description: software

Exhibition: Notes on a New Nature

youtube

Applicat Spectra「アップル」 (by asketch)

The second new song from Applicat Spectra.

Facebook Director Feels Indians Were Better Off Under British Rule

Marc Andreessen has since deleted his tweet following Indian Twitter’s backlash.

Marc Andreessen, the co-founder of Netscape and currently among the board of directors for Facebook, was fair game today for Indian Twitter after his shocking comment about colonialism in India.

“Anti-colonialism has been economically catastrophic for the Indian people for decades. Why stop now,” he said this morning in a tweet that has now been deleted.

Andreessen had earlier tweeted that India’s opposition to Free Basics is “morally wrong”.

Andreessen, who has a penchant for blocking those who object to his bizarre tweets, made his comment in a conversation about Facebook’s Free Basics being banned in India.

Andreessen’s comments follow Facebook CEO Mark Zuckerberg’s throwing of toys from his pram, asserting that his company would not rest till India and other developing countries accept Free Basics. 

“While we’re disappointed with today’s decision, I want to personally communicate that we are committed to keep working to break down barriers to connectivity in India and around the world,” Zuckerberg wrote in a Facebook post soon after TRAI, India’s telecom regulatory authority, blocked differential pricing by telecom operators.

The comment justifies strongly-held fears of net neutrality activists who believe Free Basics to be a form of internet casteism that only means to serve Facebook’s interest in finding its next billion users.

Andreessen later tweeted he is opposed to colonialism.

“I hereby withdraw from all future discussions of Indian economics or politics. :D Carry on…”

“And for the record, I am opposed to colonialism, in any country.”

Not surprisingly, people on social media – and not just Indians –  didn’t take kindly to Andreessen’s idiotic assertion, and let him have it. 

I fuckin remember trying and waiting forever to get dial up to connect bc we lived in the middle of fuckin nowhere, and when it finally did I remember trying to look shit up on Netscape to help me beat this stupid educational game that just happened to star sonic??? Like I don’t even think it was official, it was some third party bullshit, but holy shit aside from Oregon trail it was all that computer had for me so boy howdy did I play it

Netscape : 5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36 is not supported!
Only Internet Explorer 6, Internet Explorer 7 and Internet Explorer 8 are supported.

HP, 2016. odakuldtek.

Mega64 Podcast #381 Link Dump

Video | Audio | Blog

Question of the Week: What did you think of the movie Nightcrawler? – E-mail at Podcast@Mega64.com

Hosts: Derrick Acosta [ t ], Garrett Hunter [ t ], Rocco Botte [ t ], Shawn Chatfield [ t ] Crew: Eric Baudour [ t ]

I’m starting to realize all the 1990s blogs are run by people about 4-5 years younger than me.

Because all the stuff in them from the late 90s are the kinds of things that would have been of interest to middle-Jr High schoolers at the time.

Man, I was in HS from 1996-2000. WHERE’S MY DARIA. GIMMIE MY DARIA. (Note: I desperately wish they’d remake Daria with her life now as a 30-something year old.) (Also, Pop-Up Video. STAR TREK: VOYAGER. Bill Nye would have been acceptable too, because even though his content was technically a bit young for me, I enjoyed the show anyway.)

And how about movies and video games? TOY STORY. EARTHBOUND.

And what about the Internet? Remember LYCOS? DOGPILE? WEB RINGS? GUESTBOOKS? NETSCAPE? The Y2K bug?

Also, fashion: chokers & jumpers & those plastic fake tattoo chokers/bracelets. And WWJD? bracelets were all the rage amongst the Christian teens. And I don’t know if you remember this, but the 1970s were back in the 1990s. I had some KILLER bell bottoms & platform sandals back then. I had this all white outfit, except the jeans had full color orange and red poppies coming up from the bottom. (I still have the sandals somewhere.) I had a lightweight scarf with matching colors that I would wear with it.

And what about “It’s the 90s!” Oh, god, how many times I said that to my mom trying to convince her to let me do something.

Transport Layer Security TLS - History and development

Secure Network Programming API
The first research efforts towards the safety of the transport layer included application programming interface (API, for its acronym in English) Secure Network Programming (SNP), which in 1993 explored the possibility of having an API layer similar to safely transport Berkeley sockets, to facilitate the retrofitting of existing network applications with measures seguridad.5
  • SSL 3.0

The SSL protocol was originally developed by Netscape.6 Version 1.0 was never publicly presented; Version 2.0 was introduced in February 1995 but “contained a number of security flaws that ultimately led to the design of SSL version 3.0” .7 This version, presented in 1996, was a complete redesign of the protocol produced by Paul Kocher, who he worked with Netscape engineers Karlton Phil and Alan Freier. The newest versions of SSL / TLS are based on SSL 3.0. The draft 1996 SSL 3.0 was published by the IETF as RFC 6101. In the historic October 2014, a new vulnerability on the SSL protocol version 3.0, Vulnerability Poodle was generated.

  • TLS 1.0

TLS 1.0 was defined in RFC 2246 in January 1999 and is an update of SSL version 3.0. As the RFC says, “the differences between this protocol and SSL 3.0 are not dramatic, but they are significant in preventing interoperability between TLS 1.0 and SSL 3.0”. TLS 1.0 includes a form in which the implementation can connect in SSL 3.0, weakening security.

  • TLS 1.1

TLS 1.1 was defined in RFC 4346 in April 2006.8 It is an update to TLS 1.0. The most significant differences include:

  1. Added protection against CBC attacks.
  2. The initialization vector (IV) embedded was replaced by an explicit IV.
  3. Change in handling errors filling.
  4. Support for recording parameters IANA.
  • TLS 1.2 

TLS 1.2 was defined in RFC 5246 in August 2008. It is based on a later TLS 1.1 specification. The major differences are:

  1. MD5-SHA-1 combination in the pseudo-random function (PRF) was replaced by SHA-256, with the option of using PRFs specified in the cipher-suite.
  2. MD5-SHA-1 combination in the finished message was replaced by SHA-256, without the option of using hash algorithms specific to the cipher-suite. However, the size of the hash in the finished message is truncated to 96 bits.
  3. MD5-SHA-1 combination in the digitally signed item was replaced by a simple hash negotiated during the handshake, which by default is SHA-1.
  4. Improvements in the ability of clients and servers to specify which hashing algorithms and signature will accept.
  5. Support expansion figures authenticated encryption, mostly used for Galois / Counter (GCM) CCM mode and encryption mode with Advanced Encryption Standard (or Advanced Encryption Standard) (AES).
  6. Extensions defining Ciphersuites TLS and AES were added.

TLS 1.2 was later redefined in RFC 6176 March 2011 drawing up its backward compatibility with SSL and TLS to negotiate those sessions ever using SSL version 2.0.

TLS 1.3 (draft)
Until May 2015, TLS 1.3 is a draft, and details have not been set yet, is based on the above specification TLS 1.1 and 1.2. The main differences with TLS 1.2 include:

  1. Retirement GMT.
  2. Merges support RFC 4492 ECC without explicit curves.
  3. Remove the unnecessary length field entry to figures AEAD AD.
  4. Rename {Client, Server KeyExchange} to {Client, Server} KeyShare
  5. Adds an explicit HelloRetryRequest to reject the customer
  6. Handshake revised to provide mode 1-RTT.
  7. Withdrawal of DHE custom groups.
  8. Removed support for compression.
  9. Removed support for static RSA key exchange and DH.
  10. Removed support for ciphers not AEAD.

Operation
The SSL protocol exchanges records; optionally, each record can be compressed, encrypted and packaged with a message authentication code (MAC). Each record has a field that specifies the content_type higher level protocol being used.

When the connection starts, the record level encapsulates another protocol, the handshake protocol (or MoU), which has the content_type 22.

The client sends and receives several handshake structures:

  1. ClientHello sends a message specifying a set list encrypted, compression methods and the highest version of SSL protocol allowed. It also sends random bytes which will be used later (called Challenge of Customer or Dare). It may also include the session identifier.
  2. Then you get a ServerHello record, in which the server chooses the connection parameters from the choices offered by the client earlier.
  3. When the connection parameters are known, client and server exchange certificates (depending on the selected public key encryption). These certificates are currently X.509, but there is also a draft specifying the use of certificates based on OpenPGP.
  4. Client and server negotiate a common secret key (symmetric) called master secret, possibly using the result of a Diffie-Hellman exchange, or simply encrypting a secret key with a public key is decrypted with the private key of each. All other key data are derived from the master secret (and the generated random values ​​in the client and server), which are passed through a carefully chosen pseudorandom function.

TLS / SSL have a variety of security measures:

  1. Numbering all the records and using the sequence number in the MAC.
  2. Using a summary of enhanced with a key message (so that one with that key can check the MAC). This is specified in RFC 2104).
  3. Protection against several known attacks (including man-in-the-middle attacks), such as those involving a gradient protocol to previous versions (and therefore less safe), or weaker cipher suites.
  4. The message that ends the handshake protocol (Finished) sends a hash of all data exchanged and viewed by both parties.
  5. The pseudo random function divides input data into two halves and processed with different hash algorithms (SHA and MD5), then performs an XOR operation on them. Thus you protect yourself from the possibility that any of these algorithms are revealed himself vulnerable in the future.

Key Exchange

Before a client and server can start exchanging information protected by TLS must securely exchange or agree on an encryption key and a key for use when the data (see Encryption) is encrypted. The methods used to exchange / key agreement are: public and private keys generated with RSA (denoted TLS_RSA in the protocol handshake TLS), Diffie-Hellman (named TLS_DH), Diffie-Hellman Ephemeral (denoted TLS_DHE), Diffie Hellman Elliptic Curve (denoted TLS_ECDH), Diffie-Hellman Ephemeral Elliptic Curve (TLS_ECDHE), Diffie-Hellman anonymous (TLS_DH_anon), 2 and PSK (TLS_PSK) .

The method according TLS_DH_anon key does not authenticate the server or the user and therefore rarely used since it is vulnerable to a phishing attack. Only TLS_ECDHE TLS_DHE and provide secret-perfect-to-forward.

The public key certificates used in the exchange / also vary according to the size of the keys of public / private encryption used for the exchange and therefore the strength of the security provided. In July 2013, Google announced it would stop using 1024-bit public key and change to 2048 bits keys to increase security of the TLS encryption provides its usuarios.

Data integrity
Message authentication code (MAC Message Authentication Code in English) is used for data integrity. HMAC is used for CBC mode block cipher encryption and streams. SFDA is used for authenticated encryption as CCM and GCM modes.

It’s true, however, that HTML originally lacked a way to present images. It took Marc Andreesen (yes, that Marc Andreesen) introducing the img tag in Netscape Navigator for the first images to appear on the web. Video came eons later in internet years. JavaScript has been around for a while, but it’s only recently (and probably mistakenly) become a kind of necessity. Olds can remember a brief dark period where the web was mostly something called Flash; those days are best forgotten.
— 

Hypertext for all | A Working Library

I remember all of this…