Re: [dev] less(1) replacement?
Thanks (Also to Eric). I was scratching my head for a while thinking "But you can use the tools in 9base interactively". It seems I was looking at it from the wrong direction. -- - fao_ PGP fingerprint: 739B 6C5C 3DE1 33FA "Too enough is always not much!" On 2017-08-26 1:46 pm, Anselm R Garbe wrote: On 25 August 2017 at 21:37, fao_wrote: On 2017-08-24 1:50 pm, Anselm R Garbe wrote: 9base is not intended for interactive use, so no, p does not really belong into 9base. 9base is intended to be a scripting environment. Excuse me if this is a stupid question, but: What's the difference? In my terminology "interactive use" of 9base would assume that you'd run rc as interactive shell in your terminal and use its userland from command line directly. But the actual main use case of 9base is just to be used in scripts. rc from 9base isn't particularly "convenient" for interactive use, as long as you don't run it from inside acme, 9term or rio. BR, Anselm
Re: [dev] less(1) replacement?
On 8/27/17, Laslo Hunholdwrote: > On Sat, 26 Aug 2017 23:59:27 +0200 > isabella parakiss wrote: > > Hey Isabella, > >> https://i.imgur.com/79U7mcO.png >> side by side screenshot against less >> your face looks hideous > > he did not mean the interface, but the code itself. And I personally > concur that this rather belongs to the uglier realm of bash-scripts. > Please refrain from personal insults. > > It's impressive how it has been made, but I'm sure "native" solutions > in C or other compiled languages should be preferred. Paging is not a > too difficult thing to solve, if I may make this statement. > > With best regards > > Laslo > > -- > Laslo Hunhold > > cool, let me just rewrite it in c++ or in javascript and then create a native solution with electron name 3 reasons why compiled languages should be preferred, but of course performance can't be in your list also it's funny that you talk about personal insults after your rape threats go fuck a cactus
Re: [dev] dl.suckless.org file integrity github project
On Sat, 26 Aug 2017 21:05:25 +0200 Laslo Hunholdwrote: > On Fri, 25 Aug 2017 17:13:38 +0200 > Mattias Andrée wrote: > > Dear Mattias, > > > Each user could have a directory called pgp-keys and dl.suckless.org > > could list those directories. This would allow us to store old keys > > in a structured manner. > > > > An alternative is that the owner of a repo commits his key to the > > repo under /.pgp-keys. > > this is absolute insanity! This completely defeats the purpose of it. > If for some reason the suckless.org server is compromised, the > attacker can sign the fraudulent commits with his key and just replace > the one for the corresponding user on dl.suckless.org. > > PGP only works if the hosting is diverse, i.e. if the key is for > instance hosted on every project member's homepage. Can't we just stop > with this pseudo-security stuff? > > If somebody fiddled with the git-repo in some way, people would notice, > because many many people have copies of the tree on their computer. If > somebody somehow modified tags, or rebranched the repository, it would > be noticed. This is much more logical security approach which is > already in place. > Still, I'm not against signing tags with PGP keys, and as always, in > case I get something wrong, please let me know. > > With best regards > > Laslo > The user's must be able to find the appropriate keys some way the first time, so suckless must at least have links to them. If suckless is compromised these can be replaced. PGP keys only ensure that future keys are not fraudulent as all new key should be signed by the old keys. SSL certificates ensures that the PGP keys are not tempered with by anyone outside suckless. Thus, hosting the keys one suckless.org, when it has HTTPS, is more secure that every ones private home pages outside suckless.org that do not have SSL certificates.
Re: [dev] less(1) replacement?
On Sat, 26 Aug 2017 23:59:27 +0200 isabella parakisswrote: Hey Isabella, > https://i.imgur.com/79U7mcO.png > side by side screenshot against less > your face looks hideous he did not mean the interface, but the code itself. And I personally concur that this rather belongs to the uglier realm of bash-scripts. Please refrain from personal insults. It's impressive how it has been made, but I'm sure "native" solutions in C or other compiled languages should be preferred. Paging is not a too difficult thing to solve, if I may make this statement. With best regards Laslo -- Laslo Hunhold
Re: [dev] less(1) replacement?
On 8/26/17, Anselm R Garbewrote: > On 26 August 2017 at 13:05, isabella parakiss wrote: >> i wrote a simple pager in ~100 lines >> https://github.com/izabera/bashutils/blob/master/pager >> >> inb4 it sucks because it's bash code > > Tbh, it looks hideous. Why on earth are you using bash? > > -Anselm > > https://i.imgur.com/79U7mcO.png side by side screenshot against less your face looks hideous
Re: [dev] dl.suckless.org file integrity github project
On Fri, 25 Aug 2017 13:54:41 +0200 Anselm R Garbewrote: Dear Anselm, > Either that, or perhaps we can reinstate the old fashion of > suckless.org/~user/ homedir. I gave it a bit more thought and realized that putting the keys all in one place defeats the purpose of PGP. If the server is compromised, an attacker would just have to additionally replace the keys in the homedirs besides replacing the signed release-tarballs with fraudulent ones that were signed with his "fraudulent" key. With best regards Laslo -- Laslo Hunhold
Re: [dev] dl.suckless.org file integrity github project
On Fri, 25 Aug 2017 17:13:38 +0200 Mattias Andréewrote: Dear Mattias, > Each user could have a directory called pgp-keys and dl.suckless.org > could list those directories. This would allow us to store old keys > in a structured manner. > > An alternative is that the owner of a repo commits his key to the > repo under /.pgp-keys. this is absolute insanity! This completely defeats the purpose of it. If for some reason the suckless.org server is compromised, the attacker can sign the fraudulent commits with his key and just replace the one for the corresponding user on dl.suckless.org. PGP only works if the hosting is diverse, i.e. if the key is for instance hosted on every project member's homepage. Can't we just stop with this pseudo-security stuff? If somebody fiddled with the git-repo in some way, people would notice, because many many people have copies of the tree on their computer. If somebody somehow modified tags, or rebranched the repository, it would be noticed. This is much more logical security approach which is already in place. Still, I'm not against signing tags with PGP keys, and as always, in case I get something wrong, please let me know. With best regards Laslo -- Laslo Hunhold
Re: [dev] less(1) replacement?
On 25 August 2017 at 21:37, fao_wrote: > On 2017-08-24 1:50 pm, Anselm R Garbe wrote: >> 9base is not intended for interactive use, so no, p does not really >> belong into 9base. 9base is intended to be a scripting environment. > > Excuse me if this is a stupid question, but: What's the difference? In my terminology "interactive use" of 9base would assume that you'd run rc as interactive shell in your terminal and use its userland from command line directly. But the actual main use case of 9base is just to be used in scripts. rc from 9base isn't particularly "convenient" for interactive use, as long as you don't run it from inside acme, 9term or rio. BR, Anselm
Re: [dev] less(1) replacement?
On 26 August 2017 at 13:05, isabella parakisswrote: > i wrote a simple pager in ~100 lines > https://github.com/izabera/bashutils/blob/master/pager > > inb4 it sucks because it's bash code Tbh, it looks hideous. Why on earth are you using bash? -Anselm
Re: [dev] [9base] [musl] "Undefined reference to sigsetjmp"
On 25 August 2017 at 22:17, fao_wrote: > When compiling 9base with > >> CC=musl-gcc >> PREFIX="" >> OBJTYPE=x86_64 > > > I get the error: > >> ../lib9/lib9.a(notify.o): In function `signotify`: >> notify.c:(.text+0x9a): undefined reference to `sigsetjmp` >> collect2: error: ld returned 1 exit status > > > Except: > $ grep -Rni "sigsetjmp" /usr/lib/musl/ >> >> /usr/lib/musl/include/setjmp.h:22:int sigsetjmp (sigjmp_buf, int); >> ... > > > On the offchance that `setjmp.h` was not included in `notify.c`, I > added it manually. It still failed with the same error. Nice spot, according to this[0] musl discourages legacy setjmp behaviour. Hence I guess it will need a bit of fiddling in 9base to make it p9setjmp-free. I will check this during next week. [0] http://wiki.musl-libc.org/wiki/Functional_differences_from_glibc BR, Anselm
Re: [dev] less(1) replacement?
On 8/24/17, fao_wrote: > Is the suckless project packing a replacement to my favorite pager, > less(1)? Or is the advice to just use something like screen or tmux. I > don't really want to bother installing and learning those when `less` > meets > my needs perfectly. > > As far as I can tell, there isn't. But I could have missed something, > given > how many unrelated results `suckless "less"` pulls up :) > > -- > - fao_ > PGP fingerprint: 739B 6C5C 3DE1 33FA > "Too enough is always not much!" > > i wrote a simple pager in ~100 lines https://github.com/izabera/bashutils/blob/master/pager inb4 it sucks because it's bash code