| Mute these words in your settings here: https://twitter.com/settings/muted_keywords | |
| ActivityTweet | |
| generic_activity_highlights | |
| generic_activity_momentsbreaking | |
| RankedOrganicTweet | |
| suggest_activity | |
| suggest_activity_feed | |
| suggest_activity_highlights | |
| suggest_activity_tweet |
| This is a benchmark of the BETA CUDA branch of Hashcat, designed to run with both CUDA and OpenCL devices. | |
| The Jetson Nano Dev Kit is an ARM SBC with a Jetson Nano (Maxwell 128 CUDA core) module attached. | |
| Some modes failed due to the limitations of such a lower power GPU. | |
| Access to the Jetson Nano was provided by Gridcoin(https://gridcoin.us/) Community member sodom89. | |
| hashcat (v5.1.0-1029-g523e0f71) starting in benchmark mode... |
I’m looking for any tips or tricks for making chrome headless mode less detectable. Here is what I’ve done so far:
Set my args as follows:
const run = (async () => {
const args = [
'--no-sandbox',
'--disable-setuid-sandbox',
'--disable-infobars',
| function sync() { | |
| var id="XXXXXXXXXX"; // CHANGE - id of the secondary calendar to pull events from | |
| var today=new Date(); | |
| var enddate=new Date(); | |
| enddate.setDate(today.getDate()+7); // how many days in advance to monitor and block off time | |
| var secondaryCal=CalendarApp.getCalendarById(id); | |
| var secondaryEvents=secondaryCal.getEvents(today,enddate); |
namespaces - overview of Linux namespaces http://man7.org/linux/man-pages/man7/namespaces.7.html
mount_namespaces - overview of Linux mount namespaces
2017-03-03 fm4dd
The gcc compiler can optimize code by taking advantage of CPU specific features. Especially for ARM CPU's, this can have impact on application performance. ARM CPU's, even under the same architecture, could be implemented with different versions of floating point units (FPU). Utilizing full FPU potential improves performance of heavier operating systems such as full Linux distributions.
These flags can both be used to set the CPU type. Setting one or the other is sufficient.
| *** RSA | |
| # Generate self-signed certificate with RSA 4096 key-pair | |
| openssl req -x509 -nodes -days 3650 -newkey rsa:4096 -keyout rsakey.pem -out rsacert.pem | |
| # print private and public key | |
| openssl rsa -in rsakey.pem -text -noout | |
| # print certificate | |
| openssl x509 -in rsacert.pem -text -noout |
| #!/bin/sh | |
| # Written by: Keefer Rourke <https://krourke.org> | |
| # Based on AUR package <https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=ttf-google-fonts-git> | |
| # dependancies: fonts-cantarell, ttf-ubuntu-font-family, git | |
| sudo apt-get install fonts-cantarell ttf-ubuntu-font-family git | |
| srcdir="/tmp/google-fonts" | |
| pkgdir="/usr/share/fonts/truetype/google-fonts" | |
| giturl="git://github.com/google/fonts.git" |
Putting cryptographic primitives together is a lot like putting a jigsaw puzzle together, where all the pieces are cut exactly the same way, but there is only one correct solution. Thankfully, there are some projects out there that are working hard to make sure developers are getting it right.
The following advice comes from years of research from leading security researchers, developers, and cryptographers. This Gist was [forked from Thomas Ptacek's Gist][1] to be more readable. Additions have been added from
