Jake Brinkmann jakebrinkmann

Pulse Secure Client on Ubuntu Linux

by Danny Quah, June 2020 (revised Jan 2022)

Pulse Secure Client is a VPN client that allows secure connection to a Pulse Connect Secure SSL VPN gateway. Many universities use that latter for faculty, staff, and student access to their computer systems. However, because Linux comes in many different flavors, the standard Pulse Secure Client installer does not always run to completion. (For one, [UWO.ca][] suggests "PulseSecure's understanding of Linux package managers and distributions in general seems very limited.") The user is then either forced to use a Windows machine, somehow, or fail VPN access when traveling with their Linux notebook.

This Gist describes the steps I took to install Pulse Secure Client on my Ubuntu-based Linux machines, including a Pixelbook running GalliumOS 3.1 and Dell desktops running Ubuntu 18.04 and 20.04. Other writeups elsewhere that I've looked at describe the same problems I encountered, but were either out-dated, overly localised,

Disclaimer: This gist is a bit outdated now. The client download page now redirects to a login page that the downloads are guarded behind. You'll want to do a web search for a pulse secure deb file and install that now. Try: http://webdev.web3.technion.ac.il/docs/cis/public/ssl-vpn/ps-pulse-ubuntu-debian.deb. When I installed Pulse Secure 9.1R13, I didn't need to do anything else to get it working.

9.1R13 download: https://drive.google.com/file/d/1xfXsg9aNISAtWUgfVmAWKd_8FE2I_Mbl/view

To install Pulse Secure for Ubuntu 20.04, it is a bit complicated since the support isn't great.

First, we'll want to go through the form at https://www.pulsesecure.net/trynow/client-download/. You'll get an email with download links to the latest versions of pulse secure. Download the Linux

👩‍💻 👨‍💻

Hello Friends. This is my space where I want to spread knowledge as far as I can.

Adding co-authors to Git commits

How do you share credit for a new or altered piece of code when one person commits the change in a pair programming or mob programming session? And when you have questions about a particular change, how can you see in Git who has been working on that change, besides the committer? You add co-autors to your commits. This gist contains information on how to do that, so that the Git commit message contains a list of co-authors, and all co-autors for a commit are automatically listed in GitHubs web UI.

GitHub has some info on specifying co-authors here. This is good info, pretty straightforward. The gist of it (pun intended) is to include at least one blank line and then a line for each co-author like so Co-authored-by: name <[email protected]> at the very end of your commit message.

GitHub's recipe tells you [how to find the right e-mail address to use](https:

Type	Emoji	code
feat	✨	`:sparkles:`
fix	🐛	`:bug:`
docs	📚	`:books:`
style	💎	`:gem:`
refactor	🔨	`:hammer:`
perf	🚀	`:rocket:`
test	🚨	`:rotating_light:`
build	📦	`:package:`

How to Install Homebrew on Manjaro

Steps

Install base-devel

 pacman -Syu # CAUTION: this updates the whole system
 pacman -S base-devel

Run the installer script

Using Git Commit Message Templates to Write Better Commit Messages

The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the

	---
	AWSTemplateFormatVersion: '2010-09-09'
	Description: Sample template that contains a Lambda function behind an API GW
	Resources:
	# BEGIN: Should only need this in an empty API Gateway situation
	ApiGatewayCloudWatchLogsRole:
	Type: AWS::IAM::Role
	Properties:
	AssumeRolePolicyDocument:
	Version: '2012-10-17'

	const zlib = require('zlib');

	exports.decode = async (data) => {
	const compressedPayload = Buffer.from(data, 'base64');
	const jsonPayload = zlib.gunzipSync(compressedPayload).toString('utf8');
	return JSON.parse(jsonPayload);
	}