Archive for November, 2004
- neue variable in preferences die rahmen-farbe festlegt
- full ATOM support
- trackback/pingback support
- automatic referer spam detection
This patch adds the feature of “Hidden sites” to antville 1.1. A “hidden site” is not password protected but should not be easy to locate to the general public. Hidden sites are not linked form the sites main index and are protected from spiders via the robots.txt file.
If hidden sites are activated in antville’s main preferences administrators of trusted sites can activate the hiding feature in their site’s preferences. Untrusted sites can’t change their hiding preferences.
Hidden sites are useful if you want data to be easily accessible (e.g. for your grandparents) but dont want it to end up somewhere in search engines, Web archives or easily locatable for just everybody (e.g. because you site contains stories of you children which might they consider embarrassing when in 10 years their schoolmates start digging them out).
A more hackish variant of this patch was successfully in use for more than a year.
To use it you have to change the database structure of your antville database slightly by executing
alter table AV_SITE add column SITE_ISHIDDEN tinyint(1) null; at the SQL prompt.
Get the patch at http://c0re.23.nu/c0de/misc/antville-1.1-hiding.patch
We spend the weekend updating blogs.23.nu to a brand new FreeBSD 5.3 and antville 1.1.
Upgrading antville was a nightmare. There seems to be no migration path from 1.0.1 to 1.1. Seems people using antville in production are all doing incremental upgrades via CVS. In the end this meant writing a few hundred lines of code to massage the database into shape for 1.1. Also it is next to impossible to migrate the old skins to antville 1.1 automatically. Gnarf.
Now we have to port our extensions to antville over to 1.1.
We are back from Japan. We missed the big rain, but Nicky didn’t resist the peer pressure and bought an Sharp Zaurus SL-C 3000. I bought 10.000 small gadges; usually with the reasoning “I need that for my research”. Nice being in Japan, nice being back home.
I held the presentation from PacSec again this time in my forensics class and hopefully there will be video footage of that lecture become available shortly.
Dear Dr. Dornseif,
We have learned of your published research on quantum cryptography. Nova Science Publishers, Inc. currently publishes about 500 new titles each year. We would like to invite your participation in our publishing program. In particular, I have in mind a new article for an edited collection (invitation only) being assembled under my direction tentatively entitled, “Progress in Quantum Cryptography Research.” The contributions for this edited book and a follow-up volume are intended to range from 5,000-25,000 words. If you are interested in participating, please consult the Notes for Contributors at the bottom of this letter. Publication is about 6-9 months after the close of the volume. We would welcome the opportunity of working with you.
We would also welcome your participation by serving as the editor of a collected work or by proposing a monograph, a textbook (targeted adoption) or a new online or paper journal idea. In any case, we request as much detail as may exist on the proposed contents even if that is a brief description of the scope.
I look forward to learning your thoughts on this idea.
President and Editor-in-Chief
Nova Science Publishers, Inc.
400 Oser Avenue, Suite 1600
Hauppauge, NY 11788
Tel: 631- 231-7269
Notes for Contributors to Edited Collections
The deadline is April 9, 2005 for this volume with a follow-up volume (a completely separate publication) planned with a deadline of February 14, 2006.
1. Contributors’ names are listed on the cover of the book, which will be hardcover.
2. There are no page charges.
3. A free copy of the published book is sent to each contributor.
4. The scientific community is the intended audience.
5. The choice of theme and approach are at the discretion of the author but acceptance is only upon submission of the draft abstract. The line-up of chapters is a constantly changing landscape since discussions, commitments and submissions continue on a daily basis right up to and sometimes beyond the close of each volume.
6. Research results (studies) are the primary type of article desired but review articles are also welcome.
7. Before December 31, 2004, a draft abstract on the following form is required for the first volume consisting of : 1. 150-400 words; 2. Author affiliations; and 3. Estimated date of chapter submission and Copyright Transfer. Please include the abstract as part of an email and not as an attachment if possible. Acceptance of topics is based partially on which topics have already been accepted for particular volumes. The reply to the draft abstract will contain details about reference styles and other relevant technical details. A reply and decision may be expected within 7 days if the word Abstract is contained within the Subject Line of the email.
Draft Abstract and Copyright Transfer Form
NOVA grants to the author (and to all coauthors) the right to present orally, in any forum, all or part of the work. It is also stipulated that all graphics including figures, tables and charts may be republished without permission from Nova Science.
In consideration of the fact that NOVA undertakes to publish my article/chapter:
1. I affirm that the material in the work has not been previously published and that I (and my coauthors) own and have not transferred elsewhere any rights to the abstract or the work). 2. I affirm that I (and my coauthors) have obtained written permission to use any previously copyrighted material included in the article and that such documentation will be forwarded to NOVA for its files. I further affirm that I (and my coauthors) have stated any possible conflicts of interest within the article. 3. I (and my coauthors) hereby assign and transfer to NOVA all rights of copyright ownership to the article, including without limitation all rights of reproduction, derivation, distribution, sale, and display of the work, in whole or in part, including recompilation, in any and all forms of media now or hereafter known, including digital media, as protected by the laws of the United States and foreign countries. These rights will become the property of NOVA from the date of acceptance of the article for publication and extend for the life of the copyright. I understand that NOVA as copyright owner, has authority to grant permission to reproduce the article.
Chapter/article title: __________________________________________________________
I sign for (type name, and date) and accept responsibility for transferring copyright of this article to NOVA.
Authors names and Affiliations:
Estimated Date of Submission:
Draft Abstract (150-500 words):
8. Contributors are encouraged to submit chapters ranging from 5,000-25,000 words. In general, the longer the paper the better. Submissions of less than 5,000 words (references are included in the word count) will be returned. In the event of Latex or similar program use, or when a chapter contains numerous tabular data, graphics, or mathematical formula, a page range of 10-50 pages is acceptable.
9. Coauthors may be added without discussion.
10. Publication is by invitation only.
11. Copyright is transferred to Nova via email. A form will be sent via email at along with the electronic page proofs. No permission will be required for reuse of tabular or graphic data.
12. Ten free offprints are sent to the first listed author of each chapter. Additional personalized chapter offprints are available.
13. MS Word or Latex are the preferred input programs. If Latex, Nova requests use of the Nova macro. This is ARTICLE.STY set at 5.5 inches (13.97 cm) and letter size (not A4 paper). Please try to use outside justified page headers. If you would like to add any packages to this macro beyond those already specified, it is mandatory that the corresponding .sty files be submitted with the chapter. Nova currently uses the Windows Operating System.
14. Nova will review the English for style, if such a request is clearly marked at the beginning of the article.
15. Color graphics are allowed.
Dick Gabriel has published his excellent book “Patterns of Software” as
a freely downloadable PDF file on his website http://www.dreamsongs.com/ [Lambda the Ultimate]
Since ssh can provide you with an 8-bit clean channel you basically can transport anythong through an ssh tunnel. Let me illustrate. Assume you have the host houton which is reachable via the Internet and untertasse which is reachable only via houston. Wit a single command you can get a shell on untertasse:
% ssh -CAXt dornseif@houston ssh -X md@untertasse
This asks ssh to connect you as user ‘dornseif’ to houston and from there immediately go on connecting you as ‘md’ to untertasse. Parameter -C requests compression of the ssh connection, -A asks ssh to forward authentication information from houston to untergrund -X allows you to start any X Windows programs untertasse and get them displayed on your local machine and -t tells ssh ensure that you are treated as a human and not as an shell script doing some automatic connecting.
Lets say there is a third host, untergrund which is only reachable via untertasse where you log in as ‘drt’. No Problem:
% ssh -CAXt dornseif@houston ssh -CAXt md@untertasse ssh -X drt@untergrund
Voila, a shell on untergrund.
That was fun, but what was that with being 8bit clean? Basically you can transfer arbitrary files by piping them through the line of sshs. Try:
% cat Desktop/towit_large.jpg | ssh -CAXt dornseif@houston ssh -CAXt md@untertasse ssh -X drt@untergrund dog towit_large.jpg
What is that dog? The opposite of cat: it reads from stdin and writes to a file. In case you don’t have a dog at hand, try something more conventional:
% tar cf - Desktop/towit_large.jpg | ssh -CAXt dornseif@houston ssh -CAXt md@untertasse ssh drt@untergrund tar xvf -
Works like a charm. But then again …. it’s not that elegant. There are programs like cvs, rsync and even scp which all assumme they have something ‘rsh alike’ and use this to transfer data. usually you can give them the name of the ‘rsh alike’ program via an environment variable (e.g. RSYNC_RSH) or an parameter (often -e).. We can give our whole insane ssh pipeline as an ‘rsh alike’ program:
%rsync -e 'ssh -CAXt dornseif@houston ssh -AXt md@untertasse ssh' Desktop/towit_large.jpg drt@untergrund:
So our first two hops are putt into the -e parameter and the last one is given in the traditional rsync command line. This even works with scp!
If you are transferring many files and want to save you some typing do:
export RSYNC_RSH='ssh -CAXt dornseif@houston ssh -AXt md@untertasse ssh' or setenv RSYNC_RSH 'ssh -CAXt dornseif@houston ssh -AXt md@untertasse ssh' then rsync -e Desktop/towit_large.jpg drt@untergrund: