1,585 karma · joined January 21, 2012
- https://dankaminsky.com/2012/08/15/dakarand/ - https://github.com/stribika/dakarand
You really do need the additional constraint of the Hurwitz form to restrict the possibilities to R, C, H, O ...
(Of course this has nothing to do with the work of Furey - I'm just seconding that the claim in the article is incomplete and inexact as worded.)
Informally, a compound command is a list of commands (`( ... )` or `{ ... }`) or a looping or conditional construct. See [1] for a precise definition.
[1]: https://tiswww.case.edu/php/chet/bash/bashref.html#Compound-...
[1]: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3...
That said, I'm curious what are the nifty tricks that one can do by using functions as "aliases" for compound commands -- I cannot see much of a difference between `function sleep1 () { while true; do "$@"; sleep 1; done; }` and the similar definition without the curly braces. Only once in my life I have had to use the `function foo () ( ... )` syntax (i.e., using subshell instead of normal `{ ... }` grouping).
Feel free to reach out to me if you would like more info.
However, I think this might be a bit misleading for people who do not know Cython:
> the Cython language, which is a Python-ish programming language, but not Python.
Actually, http://cython.org/ states:
""" The Cython language is a superset of the Python language that additionally supports calling C functions and declaring C types on variables and class attributes. """
In my experience with Cython, this description is quite accurate: code can be annotated with C types and then compiled to efficient C code by Cython; if you don't use annotations, then you can still compile to C code but with less speed advantage.
I haven't used Cython since version 0.17 (quite old now) but IIRC the major drawback was that it was mainly targeting writing extension modules for Python; it could generate self-standing executables, but would still require a Python interpreter to be embedded in any compiled code (that was the price for seamless interoperability between Cython/compiled code and "pure Python" code).
E.g., the README states that 'cd/' is an alias for '(cd "/")' which seems to imply that one has to wrap every command in '()' and quote every filename... not very practical for a shell!
See, è.g., https://wiki.bitlbee.org/HowtoHipchat
S3IT is a core facility at the University of Zurich with the ambitious goal of supporting research use of IT across the University. This includes providing services in high-performance and cloud computing, data management, software development and higher-level functions related to computing and data interpretation.
Our technology stack currently includes Openstack, Ceph, Elasticsearch/Logstash/Kibana (ELK), Check_MK, CFEngine 3, Percona, Pacemaker/Corosync, Ubuntu. We love to Python and use it to automate the services.
We are currently looking for an OpenStack ops team lead to continue developing our private OpenStack installation with new service offerings, and keep the existing ones up to their excellent track record of stability.
More details and application info at: http://www.jobs.uzh.ch/jobDetail.php?jobID=7184
- Debian is prevalently not vulnerable: https://security-tracker.debian.org/tracker/CVE-2016-7117 (except the "oldstable" release)
- for Ubuntu, the situation is more complicated, as it depends on the actual kernel package installed: https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2... For the "linux" kernel package (prob the most common), the situation looks like this at the moment::
Upstream: released (4.6~rc1)
Ubuntu 12.04 LTS (Precise Pangolin): needed
Ubuntu 14.04 LTS (Trusty Tahr): released (3.13.0-86.130)
Ubuntu Touch 15.04: DNE
Ubuntu Core 15.04: pending (3.19.0-59.65)
Ubuntu 16.04 LTS (Xenial Xerus): released (4.4.0-22.39)
Ubuntu 16.10 (Yakkety Yak): not-affected (4.4.0-22.39)
- for CentOS/RHEL, my understanding is that fixed kernels have not yet been released: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-7117I guess the post on securityfocus (also not reachable) slipped out before end of embargo time?
Python `-OO` strips docstrings, `-O` basically only disables assertions. See: http://stackoverflow.com/a/4777156/459543
That's not the conclusion I draw from the article.
I rather read it as warning that even innocent and quite common operations like realloc() or using buffered I/O can have security implications, so one need to be extra extra extra careful when writing code that handles sensitive data. In other words, security can be even harder than security professionals think.
Apparently these code examples accompany the author's "book" on GUI Rebol programming.
S3IT is a core facility at the University of Zurich with the ambitious goal of supporting research use of IT across the University. This includes providing services in high-performance and cloud computing, data management, software development and higher-level functions related to computing and data interpretation.
We are currently looking to expand our core team with:
* a cloud systems engineer, http://www.s3it.uzh.ch/about/jobs/senior-cloud-systems-engin...
* a junior systems administrator, http://www.s3it.uzh.ch/about/jobs/junior-systems-administrat...
Our technology stack currently includes Openstack, Ceph, Elasticsearch/Logstash/Kibana (ELK), Check_MK, CFEngine 3, MariaDB with Galera, Pacemaker/Corosync, Ubuntu. We love to Python and use it to automate the services.
For more information please see http://www.s3it.uzh.ch/about/jobs/ or email jobs@s3it.lists.uzh.ch
The shootout, however, is from August 2013 so getting a bit old by now.