'Master' & 'Slave' Words to be Removed From Python

These service words will be removed from one of the most popular programming languages for political correctness
13 September 2018   729

The creator of the Python programming language, Guido van Rossum, announced that Python 3.8 will remove designs with the words "master" and "slave" for reasons of political correctness. This proposal was made by a Red Hat employee and one of the key developers of Python Victor Stinner. He believes that words are associated with slavery and inequality.

The proposal caused discussion in the circles of developers. In the opinion of opponents of change, Stinner mixes politics and programming, and "master" and "slave" are just terms whose meaning has nothing to do with the approval of slavery. In addition, their replacement can lead to violation of backward compatibility, community members are sure.

Guido van Rossum accepted four out of five commits. Among them:

  • master process is replaced by the parent process;
  • master option mappings replaced by main option mappings;
  • master pattern object replaced by main pattern object;
  • in the ssl module, the word master is replaced by server;
  • in pty.spawn () the parameter master_read is replaced with parent_read;
  • the pty.slave_open () method is renamed to pty.child_open (), but thepty.slave_open call is still left for backward compatibility;
  • in os.openpty () and os.forkpty (), the parameters of master_fd / slave_fd are renamed to parent_fd / child_fd;
  • internal variables master_fd, slave_fd and slave_name are renamed to parent_fd, child_fd and child_name respectively;
  • the --slaveargs option is replaced by --worker-args;
  • the function run_tests_slave () is renamed to run_tests_worker ()

The creator of the Redis database, Salvatore Sanfilippo, also suggested to get rid of it from the terms "master" and "slave". Participants want to rename SLAVEOF operations to REPLICAOF and slaveof settings in replicaof. At the same time, SLAVEOF support will remain as an option for maintaining compatibility. For the same purpose, the slave feature in the INFO and ROLE commands remains. In the future, community members want to come up with an alternative to INFO and replace the slave with a replica in the ROLE.

Ethereum VM May Have Vulnerability

The vulnerability is reported by NettaLab Twitter account
12 November 2018   146

On November 9, a statement appeared in Netta Lab’s Twitter account that the organization discovered a vulnerability in the Ethereum virtual machine that allows to execute smart contracts endlessly without paying for gas online. The researchers also allegedly turned to the operator of the American database of vulnerabilities, where they registered the corresponding discovery.

Netta Labs discovered an Ethereum EVM vulnerability, which could be exploited by hackers. The vulnerability can cause smart contracts can be executed indefinitely without gas being paied.

Netta Lab's Twitter

At Netta Lab's request, Google demonstrates the site of the netto.io project, which specializes in auditing smart contracts under the Netta Lab brand, but the Twitter accounts of the projects do not match. Note that the profile that reported the vulnerability was registered in November.

Many users expressed doubts about the authenticity of the information that appeared, but then the creator of the NEO project Da Hongwei said that he spoke with the CEO of Netta Labs and asked the researchers to audit the NEO virtual machine.

Nevertheless, Vitalik Buterin wrote on Reddit that this is a vulnerability in the Python-implementation of the virtual machine, which was first reported on GitHub 9 days ago. This means that the main clients (go-ethereum; parity and cpp-ethereum) are not affected.