In Perl
, we can turn on special security check when deailing with external data.
Here is an example (taint-check.pl)
where we get the file path from user as command line input.
#!/usr/bin/perl
use v5.38;
my $file = $ARGV[0];
In Perl
, we can turn on special security check when deailing with external data.
Here is an example (taint-check.pl)
where we get the file path from user as command line input.
#!/usr/bin/perl
use v5.38;
my $file = $ARGV[0];
$ cd /tmp/
$ curl -O https://web.archive.org/web/20190512112704/https://download.microsoft.com/download/3/0/8/3080C52C-2517-43DE-BDB4-B7EAFD88F084/wmp11-windowsxp-x64-enu.exe
$ cabextract wmp11-windowsxp-x64-enu.exe -d wmp11
$ cd $HOME/.local/share/Steam/steamapps/compatdata/287290
$ WINEPREFIX=$PWD/pfx wine winecfg
#! /bin/bash | |
# | |
# build-xnu-4903.241.1.sh | |
# Brandon Azad | |
# | |
# A script showing how to build XNU version 4903.241.1 (which corresponds to | |
# macOS 10.14.3) on macOS High Sierra 10.14.6 with Xcode 9.4.1. | |
# | |
# Note: This process will OVERWRITE files in Xcode's MacOSX10.13.sdk. Make a | |
# backup of this directory first! |
This work is released under a Creative Commons Attribution-NoDerivatives 4.0 International License.
"OpenPGP" refers to the OpenPGP protocol, in much the same way that HTML refers to the protocol that specifies how to write a web page. "GnuPG", "SequoiaPGP", "OpenPGP.js", and others are implementations of the OpenPGP protocol in the same way that Mozilla Firefox, Google Chromium, and Microsoft Edge refer to software packages that process HTML data.
#!/bin/bash | |
# Build Swift on Arch Linux | |
# Original post I followed https://akrabat.com/compiling-swift-on-linux/. | |
# [1] Checking out repo | |
mkdir swift-dev | |
cd swift-dev/ | |
git clone [email protected]:apple/swift.git |
package main | |
import ( | |
"bytes" | |
"fmt" | |
"io" | |
"os" | |
"strings" | |
) |
I am trying to determine if it is possible to build a Swift dynamic library which is itself composed of one of more private modules, without needing to expose to that fact to outside users. My hope was that I could build the private module as a static library, which would be linked into the primary (dynamic) library. The dylib
could then be deployed together with its swiftmodule
and swiftdoc
and be imported, with the private module and its symbols not being exposed at all.
Unfortunately, what I'm currently observing seems to indicate that the private module's swiftmodule
also has to be available for the primary library to be successfully imported.
This can be reproduced as follows. I have the following directory structure:
./Greeter/Logger/Logger.swift
:
public func log(_ message: String) {
[ | |
{ | |
owner: 'bcoe', | |
repo: 'top-npm-users', | |
description: ':star: Generate a list of top npm users by based on monthly downloads.', | |
language: 'JavaScript', | |
isFork: false, | |
stargazers: 27, | |
watchers: 27 | |
} |
# Maintainer: Kristian Klausen <[email protected]> | |
# Contributor: Egon Ashrafinia <[email protected]> | |
# Contributor: Tavian Barnes <[email protected]> | |
# Contributor: Jan de Groot <[email protected]> | |
# Contributor: Andreas Radke <[email protected]> | |
# Contributor: Thomas Dziedzic < gostrc at gmail > | |
# Contributor: Antti "Tera" Oja <[email protected]> | |
# Contributor: Diego Jose <[email protected]> | |
# Credits to maintainers of mesa in extra! |
load 'config/deploy' | |
desc "FTP Sync" | |
namespace :deploy do | |
desc "Sync and compile to remote by default" | |
task :default do | |
#assets.sprite | |
#assets.compile | |
remote.default |