Russ Allbery: Review: Moose Madness
| Publisher: | Kalikoi |
| Copyright: | May 2021 |
| ASIN: | B094HGT1ZB |
| Format: | Kindle |
| Pages: | 68 |
| Publisher: | Kalikoi |
| Copyright: | May 2021 |
| ASIN: | B094HGT1ZB |
| Format: | Kindle |
| Pages: | 68 |
Another minor maintenance release for the RcppBDT
package is now on CRAN.
The RcppBDT
package is an early adopter of Rcpp
and was one of the first packages utilizing Boost and its Date_Time
library. The now more widely-used package anytime is a
direct descentant of RcppBDT.
This release follows the recent updates of other package updating
their C++ compilation standard along with other standard package
updates. No feature or interface changes.
The NEWS entry follows:
Courtesy of my CRANberries, there is also a diffstat report for this release. For questions, suggestions, or issues please use the issue tracker at the GitHub repo.Changes in version 0.2.7 (2025-01-25)
- The package no longer sets a C++ compilation standard
- Package infrastructure, documentation and continuous integration support have been updated
- Several manual pages now have package anchors for the code link
- A
demo/file has been move toinst/examples/
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. If you like this or other open-source work I do, you can now sponsor me at GitHub.
The fourteenth release of the qlcal package
arrivied at CRAN today,
following the QuantLib 1.37
release two days ago.
qlcal
delivers the calendaring parts of QuantLib. It is provided (for the R
package) as a set of included files, so the package is self-contained
and does not depend on an external QuantLib library (which can be
demanding to build). qlcal covers
over sixty country / market calendars and can compute holiday lists, its
complement (i.e. business day lists) and much more. Examples
are in the README at the repository, the package page,
and course at the CRAN package
page.
This releases synchronizes qlcal with
the QuantLib release 1.37 (made
this week), and moves a demo/ file to
examples/.
This update includes the inclusion of the January 9, 2025, holiday for the memorial of President Carter that was observed at the NYSE and shown by theChanges in version 0.0.14 (2025-01-23)
- Synchronized with QuantLib 1.37 released two days ago
- Calendar updates for United States and New Zealand
- The
demo/file is now ininst/examples/
allUScalendars.R example:
edd@rob:~/git/qlcal-r/inst/examples(master)$ Rscript allUScalendars.R
LiborImpact NYSE GovernmentBond NERC FederalReserve SOFR
2025-01-01 TRUE TRUE TRUE TRUE TRUE TRUE
2025-01-09 NA TRUE NA NA NA NA
2025-01-20 TRUE TRUE TRUE NA TRUE TRUE
2025-02-17 TRUE TRUE TRUE NA TRUE TRUE
2025-04-18 NA TRUE TRUE NA NA TRUE
2025-05-26 TRUE TRUE TRUE TRUE TRUE TRUE
2025-06-19 TRUE TRUE TRUE NA TRUE TRUE
2025-07-04 TRUE TRUE TRUE TRUE TRUE TRUE
2025-09-01 TRUE TRUE TRUE TRUE TRUE TRUE
2025-10-13 TRUE NA TRUE NA TRUE TRUE
2025-11-11 TRUE NA TRUE NA TRUE TRUE
2025-11-27 TRUE TRUE TRUE TRUE TRUE TRUE
2025-12-25 TRUE TRUE TRUE TRUE TRUE TRUE
edd@rob:~/git/qlcal-r/inst/examples(master)$ This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
A new minor release of our ttdo package arrived
on CRAN a few days ago. The ttdo package extends
the excellent (and very minimal / zero depends) unit testing package tinytest by Mark van der Loo with the very
clever and well-done diffobj package by
Brodie Gaslam to give us test
results with visual diffs (as shown in the screenshot below) which
seemingly is so compelling an idea that it eventually got copied by
another package which shall remain unnamed And as of this release, we
also support visual diffs as provided by tinysnapshot
by Vincent Arel-Bundock.
This release chiefly adds support for visual diff plots. As we extend
tinytest for
use in the R autograder we
maintain and deploy within the lovely PrairieLearn framework, we need
to encode the diffplot that has been produced by the autograder
(commonly in a separate Docker process) to communicate it back to the
controlling (Docker also) instance of PrairieLearn. We also did the
usual bits of package maintenance keeping badges, URLs, continuous
integration and minor R coding standards current.
As usual, the NEWS entry follows.
Courtesy of my CRANberries, there is also a diffstat report for this release. For questions, suggestions, or issues please use the issue tracker at the GitHub repo.Changes in ttdo version 0.0.10 (2025-01-21)
- Regular packaging updates to badges and continuous integration setup
- Add support for a 'visual difference' taking advantage of a tinysnapshot feature returning a
ttvd-typed result- Added (versioned) dependency on tinysnapshot (to also get the plot 'style' enhancement in the most recent version) and base64enc
- Return
ttdo-typed result if diffobj-printed result is returned- Ensure all package-documentation links in manual page have anchors to the package
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. If you like this or other open-source work I do, you can now sponsor me at GitHub.
Another maintenance release of RcppMsgPack
got onto CRAN today. MessagePack itself is an efficient
binary serialization format. It lets you exchange data among multiple
languages like JSON. But it is faster and smaller. Small integers are
encoded into a single byte, and typical short strings require only one
extra byte in addition to the strings themselves. RcppMsgPack
brings both the C++ headers of MessagePack as well as clever code (in
both R and C++) Travers wrote to access MsgPack-encoded objects directly
from R.
This is the first release in over six years, and contains mostly
maintenance. One somewhat embarassing aspect is that Travers and I
forgot about a PR that had been ready all this since the last release,
it has now been integrated. Details follow from the NEWS file.
Courtesy of my CRANberries, there is also a diffstat report for this release. For questions, suggestions, or issues please use the [issue tracker][issue tickets] at the GitHub repo.Changes in version 0.2.4 (2025-01-19)
- Use
Rcpp::RawVectorinstead ofstd::vector<unsigned char>saving extra copy (Travers in #16)- Several updates to README.md with R Journal paper, add badges, add Authors@R, add CITATION file, add repo info to DESCRIPTION
- Update continuous integration via r-ci
- Update to no longer require compilation standard
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. If you like this or other open-source work I do, you can now sponsor me at GitHub.
What is HMAC?
HMAC stands for Hash-Based Message Authentication Code. It s a specific way to use a cryptographic hash function (like SHA-1, SHA-256, etc.) along with a secret key to produce a unique fingerprint of some data. This fingerprint allows someone else with the same key to verify that the data hasn t been tampered with.
How HMAC Works
Keyed Hashing: The core idea is to incorporate the secret key into the hashing process. This is done in a specific way to prevent clever attacks that might try to bypass the security.#!/bin/bash
# remove mac specification from sshd configuration
sed -i -e 's/^macs.*$//' /etc/ssh/sshd_config
# place a new mac specification at the end of the service configuration
ssh -Q mac perl -e \
'@mac=grep chomp; ! /sha1/ ; print("macs ", join(",",@mac), $/)' >> /etc/ssh/sshd_config
# reload the new ssh service configuration
systemctl reload ssh.service
If this code is hosted on GCS, you can refer to it with
--initialization-actions=CLOUD_STORAGE_URI,[...]or
--metadata startup-script-url=CLOUD_STORAGE_URI,[...]
A new minor release of RcppFastFloat
just arrived on CRAN. The
package wraps fast_float, another
nice library by Daniel Lemire. For
details, see the arXiv
preprint or published
paper showing that one can convert character representations of
numbers into floating point at rates at or exceeding one gigabyte per
second.
This release updates the underlying fast_float library
version to the current version 7.0.0, and updates a few packaging
aspects.
Courtesy of my CRANberries, there is also a diffstat report for this release. For questions, suggestions, or issues please use the [issue tracker][issue tickets] at the GitHub repo.Changes in version 0.0.5 (2025-01-15)
- No longer set a compilation standard
- Updates to continuous integration, badges, URLs, DESCRIPTION
- Update to fast_float 7.0.0
- Per CRAN Policy comment-out compiler 'diagnostic ignore' instances
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. If you like this or other open-source work I do, you can now sponsor me at GitHub.
A new maintenance release 0.4.23 of RProtoBuf
arrived on CRAN earlier today,
about one year after the previous
update. RProtoBuf
provides R with bindings for the
Google Protocol Buffers
( ProtoBuf ) data encoding and serialization library used and
released by Google, and deployed very widely in numerous projects as a
language and operating-system agnostic protocol.
This release brings a number of contributed PRs which are truly
appreciate. As the package dates back fifteen+ years, some code corners
can be crufty which was addressed in several PRs, as were two updates
for ongoing changes / new releases of ProtoBuf itself. I also
made the usual changes one does to continuous integrations, README
badges and URL as well as correcting one issue the
checkbashism script complained about.
The following section from the NEWS.Rd file has full details.
Thanks to my CRANberries, there is a diff to the previous release. The RProtoBuf page has copies of the (older) package vignette, the quick overview vignette, and the pre-print of our JSS paper. Questions, comments etc should go to the GitHub issue tracker off the GitHub repo.Changes in RProtoBuf version 0.4.23 (2022-12-13)
- More robust tests using
toTextFormat()(Xufei Tan in #99 addressing #98)- Various standard packaging updates to CI and badges (Dirk)
- Improvements to string construction in error messages (Michael Chirico in #102 and #103)
- Accommodate ProtoBuf 26.x and later (Matteo Gianella in #104)
- Accommodate ProtoBuf 6.30.9 and later (Lev Kandel in #106)
- Correct
bashismissues inconfigure.ac(Dirk)
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. If you like this or other open-source work I do, you can sponsor me at GitHub.
The Rcpp Core Team is once again thrilled, pleased, and chuffed (am I
doing this right for LinkedIn?) to announce a new release (now at
1.0.14) of the Rcpp package. It
arrived on CRAN earlier today,
and has since been uploaded to Debian. Windows and macOS builds
should appear at CRAN in the next few days, as will builds in different
Linux distribution and of course r2u should catch up
tomorrow too. The release was only uploaded yesterday, and as always get
flagged because of the grandfathered .Call(symbol) as well
as for the url to the Rcpp book (which
has remained unchanged for years) failing . My email reply was promptly
dealt with under European morning hours and by the time I got up the
submission was in state waiting over a single reverse-dependency
failure which is also spurious, appears on some systems and not
others, and also not new. Imagine that: nearly 3000 reverse dependencies
and only one (spurious) change to worse. Solid testing seems to help. My
thanks as always to the CRAN
for responding promptly.
This release continues with the six-months January-July cycle started
with release
1.0.5 in July 2020. This time we also need a one-off hotfix
release 1.0.13-1: we had (accidentally) conditioned an upcoming R
change on 4.5.0, but it already came with 4.4.2 so we needed to adjust
our code. As a reminder, we do of course make interim snapshot dev or
rc releases available via the Rcpp drat repo as well as
the r-universe page and
repo and strongly encourage their use and testing I run my systems
with these versions which tend to work just as well, and are also fully
tested against all reverse-dependencies.
Rcpp has long established itself
as the most popular way of enhancing R with C or C++ code. Right now,
2977 packages on CRAN depend on
Rcpp for making analytical code go
faster and further. On CRAN, 13.6% of all packages depend (directly) on
Rcpp, and 60.8% of all compiled
packages do. From the cloud mirror of CRAN (which is but a subset of all
CRAN downloads), Rcpp has been
downloaded 93.7 million times. The two published papers (also included
in the package as preprint vignettes) have, respectively, 1947 (JSS, 2011) and 354 (TAS, 2018)
citations, while the the book (Springer useR!,
2013) has another 676.
This release is primarily incremental as usual, generally preserving
existing capabilities faithfully while smoothing our corners and / or
extending slightly, sometimes in response to changing and tightened
demands from CRAN or R standards. The move towards a
more standardized approach for the C API of R once again to a few
changes; Kevin did once again did most of these PRs. Other contributed
PRs include G bor permitting builds on yet another BSD variant, Simon
Guest correcting sourceCpp() to work on read-only files,
Marco Colombo correcting a (surprisingly large) number of vignette
typos, I aki rebuilding some documentation files that tickled (false)
alerts, and I took care of a number of other maintenance items along the
way.
The full list below details all changes, their respective PRs and, if
applicable, issue tickets. Big thanks from all of us to all
contributors!
Thanks to my CRANberries, you can also look at a diff to the previous release Questions, comments etc should go to the rcpp-devel mailing list off the R-Forge page. Bugs reports are welcome at the GitHub issue tracker as well (where one can also search among open or closed issues).Changes in Rcpp release version 1.0.14 (2025-01-11)
- Changes in Rcpp API:
- Support for user-defined databases has been removed (Kevin in #1314 fixing #1313)
- The
SET_TYPEOFfunction and macro is no longer used (Kevin in #1315 fixing #1312)- An errorneous cast to
intaffecting large return object has been removed (Dirk in #1335 fixing #1334)- Compilation on DragonFlyBSD is now supported (G bor Cs rdi in #1338)
- Use read-only
VECTOR_PTRandSTRING_PTRonly with with R 4.5.0 or later (Kevin in #1342 fixing #1341)- Changes in Rcpp Attributes:
- Changes in Rcpp Deployment:
- One unit tests for arm64 macOS has been adjusted; a macOS continuous integration runner was added (Dirk in #1324)
- Authors@R is now used in DESCRIPTION as mandated by CRAN, the
Rcpp.package.skeleton()function also creates it (Dirk in #1325 and #1327)- A single datetime format test has been adjusted to match a change in R-devel (Dirk in #1348 fixing #1347)
- Changes in Rcpp Documentation:
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. If you like this or other open-source work I do, you can sponsor me at GitHub.
Another minor update 0.3.11 for our nanotime
package is now on CRAN. nanotime
relies on the RcppCCTZ
package (as well as the RcppDate
package for additional C++ operations) and offers efficient high(er)
resolution time parsing and formatting up to nanosecond resolution,
using the bit64
package for the actual integer64 arithmetic. Initially
implemented using the S3 system, it has benefitted greatly from a
rigorous refactoring by Leonardo who not only rejigged
nanotime internals in S4 but also added new S4 types for
periods, intervals and durations.
This release covers two corner case. Michael sent in a PR
avoiding a clang warning on complex types. We fixed an
issue that surfaced in a downstream package under sanitizier checks: R
extends coverage of NA to types such as integer or character which need
special treatment in non-R library code as they do not know . We
flagged (character) formatted values after we had called the
corresponding CCTZ function but that leaves potentiall undefined
values (from R s NA values for int, say, cast to
double) so now we flag them, set a transient safe value for
the call and inject the (character) representation "NA"
after the call in those spots. End result is the same, but without a
possibly slap on the wrist from sanitizer checks.
The NEWS snippet below has the full details.
Thanks to my CRANberries, there is a diffstat report for this release. More details and examples are at the nanotime page; code, issue tickets etc at the GitHub repository and all documentation is provided at the nanotime documentation site.Changes in version 0.3.11 (2025-01-10)
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. If you like this or other open-source work I do, you can now sponsor me at GitHub.
A fresh minor release of the inline package got
to CRAN today, following on the
November
release which had marked the first release in three and half years.
inline
facilitates writing code in-line in simple string expressions
or short files. The package was used quite extensively by Rcpp in the very early days before Rcpp
Attributes arrived on the scene providing an even better alternative
for its use cases. inline is still
used by rstan and
a number of other packages.
In the November
release we accommodated upcoming R-devel changes on setting
R_NO_REMAP by conditioning on the release version. It turns
that this does not get when the #define independently so
this needed a small refinement which this version brings. No other
changes were made.
The NEWS extract follows and details the changes some
more.
Thanks to my CRANberries, you can also look at a diff to the previous release. Questions, comments etc should go to the rcpp-devel mailing list off the R-Forge page. Bugs reports are welcome at the GitHub issue tracker as well (where one can also search among open or closed issues).Changes in inline version 0.3.21 (2025-01-08)
- Refine use of
Rf_warningincfunctionsetting-DR_NO_REMAPourselves to get R version independent state
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. If you like this or other open-source work I do, you can now sponsor me at GitHub.
Welcome to the December 2024 report from the Reproducible Builds project!
Our monthly reports outline what we ve been up to over the past month and highlight items of news from elsewhere in the world of software supply-chain security when relevant. As ever, however, if you are interested in contributing to the Reproducible Builds project, please visit our Contribute page on our website.
Table of contents:
Last month saw the introduction of reproduce.debian.net. Announced at the recent Debian MiniDebConf in Toulouse, reproduce.debian.net is an instance of rebuilderd operated by the Reproducible Builds project. rebuilderd is our server designed monitor the official package repositories of Linux distributions and attempts to reproduce the observed results there.
This month, however, we are pleased to announce that not only does the service now produce graphs, the reproduce.debian.net homepage itself has become a start page of sorts, and the amd64.reproduce.debian.net and i386.reproduce.debian.net pages have emerged. The first of these rebuilds the amd64 architecture, naturally, but it also is building Debian packages that are marked with the no architecture label, all. The second builder is, however, only rebuilding the i386 architecture.
Both of these services were also switched to reproduce the Debian trixie distribution instead of unstable, which started with 43% of the archive rebuild with 79.3% reproduced successfully. This is very much a work in progress, and we ll start reproducing Debian unstable soon.
Our i386 hosts are very kindly sponsored by Infomaniak whilst the amd64 node is sponsored by OSUOSL thank you! Indeed, we are looking for more workers for more Debian architectures; please contact us if you are able to help.
Reproducible builds developer kpcyrd has published a client program for reproduce.debian.net (see above) that queries the status of the locally installed packages and rates the system with a percentage score. This tool works analogously to arch-repro-status for the Arch Linux Reproducible Builds setup.
The tool was packaged for Debian and is currently available in Debian trixie: it can be installed with apt install debian-repro-status.
glibc within openSUSE.
kpcyrd followed-up to a post from September 2024 which mentioned their desire for someone to implement a hashset of allowed module hashes that is generated during the kernel build and then embedded in the kernel image , thus enabling a deterministic and reproducible build. However, they are now reporting that somebody implemented the hash-based allow list feature and submitted it to the Linux kernel mailing list . Like kpcyrd, we hope it gets merged.
Mehdi Keshani of the Delft University of Technology in the Netherlands has published their thesis on Enhancing the Security of Software Supply Chains: Methods and Practices . Their introductory summary first begins with an outline of software supply chains and the importance of the Maven ecosystem before outlining the issues that it faces that threaten its security and effectiveness . To address these:
First, we propose an automated approach for library reproducibility to enhance library security during the deployment phase. We then develop a scalable call graph generation technique to support various use cases, such as method-level vulnerability analysis and change impact analysis, which help mitigate security challenges within the ecosystem. Utilizing the generated call graphs, we explore the impact of libraries on their users. Finally, through empirical research and mining techniques, we investigate the current state of the Maven ecosystem, identify harmful practices, and propose recommendations to address them.A PDF of Mehdi s entire thesis is available to download.
diffoscope is our in-depth and content-aware diff utility that can locate and diagnose reproducibility issues. This month, Chris Lamb made the following changes, including preparing and uploading versions 283 and 284 to Debian:
tests_quines.py::test_ differences,differences_deb to simply use assert_diff and not mangle the test fixture. [ ]
A significant supply-chain attack impacted Solana, an ecosystem for decentralised applications running on a blockchain.
Hackers targeted the @solana/web3.js JavaScript library and embedded malicious code that extracted private keys and drained funds from cryptocurrency wallets. According to some reports, about $160,000 worth of assets were stolen, not including SOL tokens and other crypto assets.
Similar to last month, there was a large number of changes made to our website this month, including:
There were a significant number of reproducibility-related changes within Debian this month, including:
0.11+nmu4 of the dh-buildinfo package. In this release, the dh_buildinfo becomes a no-op ie. it no longer does anything beyond warning the developer that the dh-buildinfo package is now obsolete. In his upload, Santiago wrote that We still want packages to drop their [dependency] on dh-buildinfo, but now they will immediately benefit from this change after a simple rebuild.
dpkg.
debian-devel development mailing list on the topic of Supporting alternative zlib implementations . In particular, Fay wrote about her results experimenting whether zlib-ng produces identical results or not.
rust-rebuilderd-worker, rust-derp, rust-in-toto and debian-repro-status to Debian, which passed successfully through the so-called NEW queue.
debrebuild component/script of the devscripts package, including:
dh-r package to report that the Recommends and Suggests fields are missing from rebuilt R packages. At the time of writing, this bug has no patch and needs some help to make over 350 binary packages reproducible.
-fobject-determinism, which enables deterministic object code generation .
tests.reproducible-builds.org/archlinux now redirect to reproducible.archlinux.org instead. In fact, everything Arch-related has now been removed from the jenkins.debian.net.git repository, as those continuous integration tests have been disabled for some time.
0.7.29 was uploaded to Debian unstable by Vagrant Cascadian. It included contributions already covered in previous months as well as new ones from Rebecca N. Palmer, such as:
cargo-packaging/rusty_v8, cockpit, collectd, deepin-daemon, deepin-file-manager, esbuild, grpc, hyperkitty, icedtea-web, java-atk-wrapper, kdenetwork-filesharing, kicad, kompare, librespeed-cli, lincity-ng, mraa, ollama, opa-fmgui, opencryptoki, opencryptoki, openmpi4:gnu-hpc, openwsman, patterns-microos, portmidi, presage, procps, sad, scons/nst, sendmail, static-initrd, suse-hpc, swtpm, tiny, vtk, xdg-desktop-portal and yast.
pyorbital.python-pbcore.dictionaries-common.
The Reproducible Builds project operates a comprehensive testing framework running primarily at tests.reproducible-builds.org in order to check packages and other artifacts for reproducibility. In November, a number of changes were made by Holger Levsen, including:
i386.reproduce.debian.net rebuilder. [ ][ ][ ][ ][ ][ ]i386.reproduce.debian.net run on a public port to allow external workers. [ ]/api/v0/pkgs/list endpoint. [ ]arch:any and arch:all on the amd64 architecture, but only arch:any on i386. [ ]dstat on Jenkins nodes anymore as its been removed from Debian trixie. [ ]infom08-i386 node to become another rebuilder. [ ]reproducible_pool_buildinfos.sh script. [ ]installation-birthday everywhere. [ ]Recommends by default on Jenkins nodes. [ ]rebuilder_stats.py to rebuilderd_stats.py. [ ]/etc/cron.d/ with the correct permissions. [ ].buildinfo on buildinfos.debian.net files. [ ][ ][ ]rebuilder_stats.py scripts. [ ]dpkg.selections file [ ], Roland Clobus updated the Jenkins log parser to parse warnings from diffoscope [ ] and Mattia Rizzolo banned a number of bots and crawlers from the service [ ][ ].
#reproducible-builds on irc.oftc.net.
rb-general@lists.reproducible-builds.org
A minor package update, the first in over six years, for the RcppGetconf
package for reading system configuration not unlike
getconf from the libc library is now on CRAN
The changes are all minor package maintenance items of keeping URLs,
continuous integration, and best practices current. We had two helper
scripts use bash in their shebangs, and we just got dinged
in one of them. Tedious as this can at times seem, it ensures CRAN packages do in fact compile
just about anywhere which is a Good Thing (TM) so we obliged and updated
the package with that change and all the others that had accumulated
over six years. No interface or behaviour changes, just maintenance as
one does at times.
The short list of changes in this release follows:
Courtesy of my CRANberries, there is also a diffstat report of changes relative to the previous release. More about the package is at the local RcppGetconf page and the GitHub repo.Changes in inline version 0.0.4 (2025-01-07)
- Dynamically linked compiled code is now registered in
NAMESPACE- The continuous integration setup was update several times
- The
READMEwas updated with current badges and URLs- The
DESCRIPTIONfile now usesAuthors@R- The
configureandcleanupscripts use/bin/sh
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. If you like this or other open-source work I do, you can now sponsor me at GitHub.
As part of their "Defective by Design" anti-DRM campaign, the FSF recently made the following claim:Today, most of the major streaming media platforms utilize the TPM to decrypt media streams, forcefully placing the decryption out of the user's control(from here).
ssh-keygen tool from OpenSSH to perform signing and verification. To refresh your memory, let s study the commands that Git uses under the hood for Ed25519. First generate a Ed25519 private key:
jas@kaka:~$ ssh-keygen -t ed25519 -f my_ed25519_key -P ""
Generating public/private ed25519 key pair.
Your identification has been saved in my_ed25519_key
Your public key has been saved in my_ed25519_key.pub
The key fingerprint is:
SHA256:fDa5+jmC2+/aiLhWeWA3IV8Wj6yMNTSuRzqUZlIGlXQ jas@kaka
The key's randomart image is:
+--[ED25519 256]--+
.+=.E ..
oo=.ooo
. =o=+o .
=oO+o .
.=+S.=
oo.o o
. o .
...o.+..
.o.o.=**.
+----[SHA256]-----+
jas@kaka:~$ cat my_ed25519_key
-----BEGIN OPENSSH PRIVATE KEY-----
b3BlbnNzaC1rZXktdjEAAAAABG5vbmUAAAAEbm9uZQAAAAAAAAABAAAAMwAAAAtzc2gtZW
QyNTUxOQAAACAWP/aZ8hzN0WNRMSpjzbgW1tJXNd2v6/dnbKaQt7iIBQAAAJCeDotOng6L
TgAAAAtzc2gtZWQyNTUxOQAAACAWP/aZ8hzN0WNRMSpjzbgW1tJXNd2v6/dnbKaQt7iIBQ
AAAEBFRvzgcD3YItl9AMmVK4xDKj8NTg4h2Sluj0/x7aSPlhY/9pnyHM3RY1ExKmPNuBbW
0lc13a/r92dsppC3uIgFAAAACGphc0BrYWthAQIDBAU=
-----END OPENSSH PRIVATE KEY-----
jas@kaka:~$ cat my_ed25519_key.pub
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBY/9pnyHM3RY1ExKmPNuBbW0lc13a/r92dsppC3uIgF jas@kaka
jas@kaka:~$
Then let s sign something with this key:
jas@kaka:~$ echo "Hello world!" > msg
jas@kaka:~$ ssh-keygen -Y sign -f my_ed25519_key -n my-namespace msg
Signing file msg
Write signature to msg.sig
jas@kaka:~$ cat msg.sig
-----BEGIN SSH SIGNATURE-----
U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgFj/2mfIczdFjUTEqY824FtbSVz
Xdr+v3Z2ymkLe4iAUAAAAMbXktbmFtZXNwYWNlAAAAAAAAAAZzaGE1MTIAAABTAAAAC3Nz
aC1lZDI1NTE5AAAAQLmWsq05tqOOZIJqjxy5ZP/YRFoaX30lfIllmfyoeM5lpVnxJ3ZxU8
SF0KodDr8Rtukg2N3Xo80NGvZOzbG/9Aw=
-----END SSH SIGNATURE-----
jas@kaka:~$
Now let s create a list of trusted public-keys and associated identities:
jas@kaka:~$ echo 'my.name@example.org ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBY/9pnyHM3RY1ExKmPNuBbW0lc13a/r92dsppC3uIgF' > allowed-signers
jas@kaka:~$
Then let s verify the message we just signed:
jas@kaka:~$ cat msg ssh-keygen -Y verify -f allowed-signers -I my.name@example.org -n my-namespace -s msg.sig
Good "my-namespace" signature for my.name@example.org with ED25519 key SHA256:fDa5+jmC2+/aiLhWeWA3IV8Wj6yMNTSuRzqUZlIGlXQ
jas@kaka:~$
I have implemented support for SPHINCS+ in OpenSSH. This is early work, but I wanted to announce it to get discussion of some of the details going and to make people aware of it.
What would a better way to demonstrate SPHINCS+ support in OpenSSH than by validating the Git commit that implements it using itself?
Here is how to proceed, first get a suitable development environment up and running. I m using a Debian container launched in a protected environment using podman.
jas@kaka:~$ podman run -it --rm debian:stable
Then install the necessary build dependencies for OpenSSH.
# apt-get update
# apt-get install git build-essential autoconf libz-dev libssl-dev
Now clone my OpenSSH branch with the SPHINCS+ implentation and build it. You may browse the commit on GitHub first if you are curious.
# cd
# git clone https://github.com/jas4711/openssh-portable.git -b sphincsp
# cd openssh-portable
# autoreconf -fvi
# ./configure
# make
Configure a Git allowed signers list with my SPHINCS+ public key (make sure to keep the public key on one line with the whitespace being one ASCII SPC character):
# mkdir -pv ~/.ssh
# echo 'simon@josefsson.org ssh-sphincsplus@openssh.com AAAAG3NzaC1zcGhpbmNzcGx1c0BvcGVuc3NoLmNvbQAAAECI6eacTxjB36xcPtP0ZyxJNIGCN350GluLD5h0KjKDsZLNmNaPSFH2ynWyKZKOF5eRPIMMKSCIV75y+KP9d6w3' > ~/.ssh/allowed_signers
# git config gpg.ssh.allowedSignersFile ~/.ssh/allowed_signers
Then verify the commit using the newly built ssh-keygen binary:
# PATH=$PWD:$PATH
# git log -1 --show-signature
commit ce0b590071e2dc845373734655192241a4ace94b (HEAD -> sphincsp, origin/sphincsp)
Good "git" signature for simon@josefsson.org with SPHINCSPLUS key SHA256:rkAa0fX0lQf/7V7QmuJHSI44L/PAPPsdWpis4nML7EQ
Author: Simon Josefsson <simon@josefsson.org>
Date: Tue Dec 3 18:44:25 2024 +0100
Add SPHINCS+.
# git verify-commit ce0b590071e2dc845373734655192241a4ace94b
Good "git" signature for simon@josefsson.org with SPHINCSPLUS key SHA256:rkAa0fX0lQf/7V7QmuJHSI44L/PAPPsdWpis4nML7EQ
#
Yay!
So what are some considerations?
SPHINCS+ comes in many different variants. First it comes with three security levels approximately matching 128/192/256 bit symmetric key strengths. Second choice is between the SHA2-256, SHAKE256 (SHA-3) and Haraka hash algorithms. Final choice is between a robust and a simple variant with different security and performance characteristics. To get going, I picked the sphincss256sha256robust SPHINCS+ implementation from SUPERCOP 20241022. There is a good size comparison table in the sphincsplus implementation, if you want to consider alternative variants.
SPHINCS+ public-keys are really small, as you can see in the allowed signers file. This is really good because they are handled by humans and often by cut n paste.
What about private keys? They are slightly longer than Ed25519 private keys but shorter than typical RSA private keys.
# ssh-keygen -t sphincsplus -f my_sphincsplus_key -P ""
Generating public/private sphincsplus key pair.
Your identification has been saved in my_sphincsplus_key
Your public key has been saved in my_sphincsplus_key.pub
The key fingerprint is:
SHA256:4rNfXdmLo/ySQiWYzsBhZIvgLu9sQQz7upG8clKziBg root@ad600ff56253
The key's randomart image is:
+[SPHINCSPLUS 256-+
. .o
o . oo.
= .o.. o
o o o o . . o
.+ = S o o .
Eo= . + . . .. .
=*.+ o . . oo .
B+= o o.o. .
o*o ... .oo.
+----[SHA256]-----+
# cat my_sphincsplus_key.pub
ssh-sphincsplus@openssh.com AAAAG3NzaC1zcGhpbmNzcGx1c0BvcGVuc3NoLmNvbQAAAEAltAX1VhZ8pdW9FgC+NdM6QfLxVXVaf1v2yW4v+tk2Oj5lxmVgZftfT37GOMOlK9iBm9SQHZZVYZddkEJ9F1D7 root@ad600ff56253
# cat my_sphincsplus_key
-----BEGIN OPENSSH PRIVATE KEY-----
b3BlbnNzaC1rZXktdjEAAAAABG5vbmUAAAAEbm9uZQAAAAAAAAABAAAAYwAAABtzc2gtc3
BoaW5jc3BsdXNAb3BlbnNzaC5jb20AAABAJbQF9VYWfKXVvRYAvjXTOkHy8VV1Wn9b9slu
L/rZNjo+ZcZlYGX7X09+xjjDpSvYgZvUkB2WVWGXXZBCfRdQ+wAAAQidiIwanYiMGgAAAB
tzc2gtc3BoaW5jc3BsdXNAb3BlbnNzaC5jb20AAABAJbQF9VYWfKXVvRYAvjXTOkHy8VV1
Wn9b9sluL/rZNjo+ZcZlYGX7X09+xjjDpSvYgZvUkB2WVWGXXZBCfRdQ+wAAAIAbwBxEhA
NYzITN6VeCMqUyvw/59JM+WOLXBlRbu3R8qS7ljc4qFVWUtmhy8B3t9e4jrhdO6w0n5I4l
mnLnBi2hJbQF9VYWfKXVvRYAvjXTOkHy8VV1Wn9b9sluL/rZNjo+ZcZlYGX7X09+xjjDpS
vYgZvUkB2WVWGXXZBCfRdQ+wAAABFyb290QGFkNjAwZmY1NjI1MwECAwQ=
-----END OPENSSH PRIVATE KEY-----
#
Signature size? Now here is the challenge, for this variant the size is around 29kb or close to 600 lines of base64 data:
# git cat-file -p ce0b590071e2dc845373734655192241a4ace94b head -10
tree ede42093e7d5acd37fde02065a4a19ac1f418703
parent 826483d51a9fee60703298bbf839d9ce37943474
author Simon Josefsson <simon@josefsson.org> 1733247865 +0100
committer Simon Josefsson <simon@josefsson.org> 1734907869 +0100
gpgsig -----BEGIN SSH SIGNATURE-----
U1NIU0lHAAAAAQAAAGMAAAAbc3NoLXNwaGluY3NwbHVzQG9wZW5zc2guY29tAAAAQIjp5p
xPGMHfrFw+0/RnLEk0gYI3fnQaW4sPmHQqMoOxks2Y1o9IUfbKdbIpko4Xl5E8gwwpIIhX
vnL4o/13rDcAAAADZ2l0AAAAAAAAAAZzaGE1MTIAAHSDAAAAG3NzaC1zcGhpbmNzcGx1c0
BvcGVuc3NoLmNvbQAAdGDHlobgfgkKKQBo3UHmnEnNXczCMNdzJmeYJau67QM6xZcAU+d+
2mvhbksm5D34m75DWEngzBb3usJTqWJeeDdplHHRe3BKVCQ05LHqRYzcSdN6eoeZqoOBvR
# git cat-file -p ce0b590071e2dc845373734655192241a4ace94b tail -5
ChvXUk4jfiNp85RDZ1kljVecfdB2/6CHFRtxrKHJRDiIavYjucgHF1bjz0fqaOSGa90UYL
RZjZ0OhdHOQjNP5QErlIOcZeqcnwi0+RtCJ1D1wH2psuXIQEyr1mCA==
-----END SSH SIGNATURE-----
Add SPHINCS+.
# git cat-file -p ce0b590071e2dc845373734655192241a4ace94b wc -l
579
#
What about performance? Verification is really fast:
# time git verify-commit ce0b590071e2dc845373734655192241a4ace94b
Good "git" signature for simon@josefsson.org with SPHINCSPLUS key SHA256:rkAa0fX0lQf/7V7QmuJHSI44L/PAPPsdWpis4nML7EQ
real 0m0.010s
user 0m0.005s
sys 0m0.005s
#
On this machine, verifying an Ed25519 signature is a couple of times slower, and needs around 0.07 seconds.
Signing is slower, it takes a bit over 2 seconds on my laptop.
# echo "Hello world!" > msg
# time ssh-keygen -Y sign -f my_sphincsplus_key -n my-namespace msg
Signing file msg
Write signature to msg.sig
real 0m2.226s
user 0m2.226s
sys 0m0.000s
# echo 'my.name@example.org ssh-sphincsplus@openssh.com AAAAG3NzaC1zcGhpbmNzcGx1c0BvcGVuc3NoLmNvbQAAAEAltAX1VhZ8pdW9FgC+NdM6QfLxVXVaf1v2yW4v+tk2Oj5lxmVgZftfT37GOMOlK9iBm9SQHZZVYZddkEJ9F1D7' > allowed-signers
# cat msg ssh-keygen -Y verify -f allowed-signers -I my.name@example.org -n my-namespace -s msg.sig
Good "my-namespace" signature for my.name@example.org with SPHINCSPLUS key SHA256:4rNfXdmLo/ySQiWYzsBhZIvgLu9sQQz7upG8clKziBg
#
Welcome to our new world of Post-Quantum safe digital signatures of Git commits, and Happy Hacking!
A follow-up release 0.3.11 to the recent 0.3.10
release release of the anytime
package arrived on CRAN two
days ago. The package is fairly feature-complete, and code and
functionality remain mature and stable, of course.
anytime
is a very focused package aiming to do just one thing really
well: to convert anything in integer, numeric, character,
factor, ordered, input format to either POSIXct (when called as
anytime) or Date objects (when called as
anydate) and to do so without requiring a format
string as well as accomodating different formats in one input
vector. See the anytime page,
or the GitHub repo
for a few examples, and the beautiful documentation site
for all documentation.
This release simply skips one test file. CRAN labeled an error M1mac yet
it did not reproduce on any of the other M1 macOS I can access
(macbuilder, GitHub Actions) as this appeared related to a local setting
of timezone values I could not reproduce anywwhere. So the only way to
get rid of the fail is to not to run the test. Needless to say the
upload process was a little tedious as I got the passive-aggressive not
responding treatment on a first upload and the required email answer it
lead to. Anyway, after a few days, and even more deep breaths, it is
taken care of and now the package
result standing is (at least currently) pristinely clean.
The short list of changes follows.
Courtesy of my CRANberries, there is also a diffstat report of changes relative to the previous release. The issue tracker tracker off the GitHub repo can be use for questions and comments. More information about the package is at the package page, the GitHub repo and the documentation site.Changes in anytime version 0.3.11 (2024-12-18)
- Skip a test file
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. If you like this or other open-source work I do, you can now sponsor me at GitHub.
Boost is a very large and
comprehensive set of (peer-reviewed) libraries for the C++ programming
language, containing well over one hundred individual libraries. The BH package provides a
sizeable subset of header-only libraries for (easier, no linking
required) use by R. It is fairly
widely used: the (partial) CRAN mirror logs (aggregated from the cloud
mirrors) show over 38.5 million package downloads.
Version 1.87.0 of Boost was released last week following the regular
Boost release schedule of April, August and December releases. As
before, we packaged it almost immediately and started testing following
our annual update cycle which strives to balance being close enough to
upstream and not stressing CRAN and the user base too much. The reverse
depends check revealed six packages requiring changes or adjustments. We
opened issue
#103 to coordinate the issue (just as we did in previous years). Our
sincere thanks to Matt
Fidler who fixed two packages pretty much immediately.
As I had not heard back from the other maintainers since filing the
issue, I uploaded the package to CRAN suggesting that the coming
winter break may be a good opportunity for the four other packages to
catch up. CRAN concurred, and
1.87.0-1 is now available there.
There are no other changes apart from cosmetics in the
DESCRIPTION file. For once, we did not add any new Boost libraries. The short NEWS entry
follows.
Via my CRANberries, there is aChanges in version 1.87.0-1 (2024-12-17)
- Upgrade to Boost 1.87.0, patched as usual to comment-out diagnostic suppression messages per the request of CRAN
- Switched to Authors@R
diffstat report relative to the previous
release. Comments and suggestions about BH are welcome via the issue
tracker at the GitHub
repo.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. If you like this or other open-source work I do, you can now sponsor me at GitHub.
| Series: | Bright Falls #3 |
| Publisher: | Berkley Romance |
| Copyright: | October 2023 |
| ISBN: | 0-593-55058-7 |
| Format: | Kindle |
| Pages: | 381 |
No was never a very easy word for Stevie when it came to Adri, when it came to anyone, really. She could handle the little stuff do you want a soda, have you seen this movie, do you like onions on your pizza but the big stuff, the stuff that caused disappointed expressions and down-turned mouths... yeah, she sucked at that part. Her anxiety would flare, and she'd spend the next week convinced her friends hated her, she'd die alone and miserable, and wasn't worth a damn to anyone. Then, when said friend or family member eventually got ahold of her to tell her that, no, of course they didn't hate her, why in the world would she think that, her anxiety would crest once again, convincing her that she was terrible at understanding people and could never trust her own brain to make heads or tails of any social situation.This is a spot-on description of a particular type of anxiety, but also this is the perfect protagonist to pair with Iris. Throughout the series, Iris has always been the ride-or-die friend, the person who may have no idea how to help but who will show up anyway and at least try to distract you. Stevie's anxiety makes Iris feel protective, which reveals one of the best sides of Iris's personality, and then the protectiveness plays off against Iris's own relationship issues and tendency to avoid taking anything too seriously. It's one of those relationships that starts a bit one-sided and then becomes mutually supporting once Stevie gets her feet under her. That's a relationship pattern I really enjoy reading about. As with the rest of the series, the friendship dynamics are great. Here we get to see two friend groups at work: Iris's, which we've seen in the previous two volumes and which expanded interestingly in Astrid Parker Doesn't Fail, and Stevie's, which is new. I liked all of these people, even Adri in her own way (although she's the hardest to like). The previous happily-ever-afters do get a bit awkward here, but Blake tries to make that part of the plot and also avoids most of the problem of somewhat-boring romantic bliss by spreading the friendship connections a bit wider. Stevie's friend group formed at orientation at Reed College, and that let me put my finger on another property of this series: essentially all of the characters are from a very specific social class. They're nearly all arts people (bookstore owner, photographer, interior decorator, actress, writer, director), they've mostly gone to college, and while most of them don't have lots of money, there's always at least one person in each friend group with significant wealth. Jordan, from the previous book, is a bit of an exception since she works in a trade (a carpenter), but she still acts like someone from that same social class. It's a bit like reading Jane Austen novels and realizing that the protagonists are drawn from a very specific and very narrow portion of society. This is not a complaint, to be clear; I have no objections to reading about a very specific social class. But if one has already read lots of books about this class of people, I could see that diminishing the appeal of this series a bit. There are a lot of assumptions baked into the story that aren't really questioned, such as the ubiquity of therapists. (I don't know how Stevie affords one on a barista salary.) There are also some small things in the terminology (therapy speak, for example) and in the specific type of earnestness with which the books attempt to be diverse on most axes other than social class that I suspect may grate a bit for some readers. If that's you, this is your warning. There is a third-act breakup here, just like the previous volumes. There is also a defense of the emotional punch of third-act breakups in romance novels in the book itself, put into Iris's internal monologue, so I suspect that's the author's answer to critics like myself who don't like the trope. I was less frustrated by this one because it fit the drama level of the protagonists, but I'll also know to expect a third-act breakup in any Blake novel I read in the future. But, all that said, the summary once again is that I loved this book and could not put it down. Iris is dramatic and occasionally self-destructive but has a core of earnest empathy that makes her easy to like. She's exactly the sort of extrovert who is soothing to introverts rather than draining because she carries the extrovert load of social situations. Stevie is adorably earnest and thoughtful beneath her anxiety. They two of them are wildly different and yet remarkably good together, and I loved reading their story. Highly recommended, along with the whole series. Start with Delilah Green Doesn't Care; if you like that, you're in for a treat. Content note: This book is also rather sex-forward and pretty explicit in the sex scenes, maybe a touch more than Astrid Parker Doesn't Fail. If that is or is not your thing in romance novels, be aware going in. Rating: 9 out of 10
Welcome to post 45 in the $R^4 series!
We introduced r-ci
here in post
#32 here nearly four years ago. It has found pretty widespread use
and adoption, and we received a few kind words then (in the
linked issue) and also more
recently (in a follow-up comment) from which we merrily quote:
[ ] almost 3 years later on and I have had zero problems with this CI setup. For people who want reliable R software, resources like these are invaluable.And while we followed up with post #41 about r2u for simple continuous integration, we may not have posted when we based r-ci on r2u (for the obvious Linux usage case). So let s make time now for a (comparitively smaller) update, and an update usage examples. We made two changes in the last few days. One is a (obvious in hindsight) simplification. Given that the
bootstrap step
was always executed, and needed no parameters, we pulled it into a new
aggregated setup simply called r-ci that includes it so
that it can be omitted as a step in the yaml file. Second, we recently
needed Fortran on macOS too, and realized it was not installed by
default so we just added that too.
With that a real and used example is now as simple as the
screenshot to the left (and hence one paragraph shorter). The trained
eye will no doubt observe that there is nothing specific to a
given repo. And that is basically the key feature: we can simply copy
this file around and get fast and easy and
reliable CI by taking advantage of the underlying robustness of
r2u solving all
dependency automagically and reliably. The option to enable macOS is
also solid and compelling as the GitHub runners are fast (but more
expensive in how the count against the limit of minutes so again a
tradeoff to make), as is the option to run coverage if one so desires.
Some of my repos do too.
Take a look at the r-ci website which has
more examples for the other supported CI servics it can used with, and
feel free to ask questions as issue in the repo.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. If you like this or other open-source work I do, you can now sponsor me at GitHub. Please report excessive re-aggregation in third-party for-profit settings.
Next.