Kevin spideynn

These instructions have moved to https://github.com/emporia-vue-local/esphome

Log4J CVE Advisory

The Problem

Log4J has a feature called Java Naming and Directory Interface (shortened to JNDI in this document), which allows a Java program to reach out to an external source to gather data.
If you put a section of text containing ${jndi:query} into the log, the Log4J library will try to resolve the query.
This can be combined with the Lightweight Directory Access Protocol (LDAP) to connect to a remote server.

However, because JNDI is built for retrieving data, and JNDI is a Java program, if you put a JNDI query using LDAP into a log, it will connect to the given site, download a file, and then execute it.
This is called Remote Code Execution.

If you are annoyed that "Sources for Android 26" are not yet available via SDK manager, this might be for you:

Collect source files

mkdir android-sdk-source-build
cd android-sdk-source-build

mkdir -p frameworks/base

Analyze & Manage Memory on Android Like a Boss

This Blog is all about memory management in Android. It provides information about how you can analyze & reduce memory usage while developing an Android app.

Memory management is a complex field of computer science and there are many techniques being developed to make it more efficient. This guide is designed to introduce you to some of the basic memory management issues that programmers face.

Memory Management in Android

Android is a Linux based operating system. It uses native open source C libraries which power Linux machines. All the basic operating system operations like I/O, memory management and so on are handled by the Linux kernel. Like Java and .NET, Android uses its own run time and virtual machine to manage application memory. Unlike either of these frameworks, the Android run time also manages the lifetime processes. Each Android application runs in a separate process within its own Dalvik instance, relinquishing all responsibility for memo

	import SwiftUI
	import PlaygroundSupport

	struct Screen: View {
	var body: some View {
	ScrollView {
	VStack {
	Text("5:45").font(.system(size: 64, weight: .thin))
	Text("Monday, May 11").font(.system(size: 24))
	}.padding(.vertical, 32)

	package main

	import (
	"context"
	"flag"
	"fmt"
	"log"
	"net/http"
	"os"
	"os/signal"

	using System.Threading.Tasks;
	using Discord.Commands;

	public class AudioModule : ModuleBase<ICommandContext>
	{
	// Scroll down further for the AudioService.
	// Like, way down
	private readonly AudioService _service;

	// Remember to add an instance of the AudioService

	/* $ gcc cve_2016_0728.c -o cve_2016_0728 -lkeyutils -Wall */
	/* $ ./cve_2016_072 PP_KEY */

	#include <stdio.h>
	#include <stdlib.h>
	#include <string.h>
	#include <sys/types.h>
	#include <keyutils.h>
	#include <unistd.h>
	#include <time.h>

	// TODO add <meta-data android:value="GlideModule" android:name="....OkHttpProgressGlideModule" />
	// TODO add <meta-data android:value="GlideModule" tools:node="remove" android:name="com.bumptech.glide.integration.okhttp.OkHttpGlideModule" />
	// or not use 'okhttp@aar' in Gradle depdendencies
	public class OkHttpProgressGlideModule implements GlideModule {
	@Override public void applyOptions(Context context, GlideBuilder builder) { }
	@Override public void registerComponents(Context context, Glide glide) {
	OkHttpClient client = new OkHttpClient();
	client.networkInterceptors().add(createInterceptor(new DispatchingProgressListener()));
	glide.register(GlideUrl.class, InputStream.class, new OkHttpUrlLoader.Factory(client));
	}