Re: [dev] [st] Two flaws with ISO 8613-6 colors, checking

2018-09-09 Thread Programmer
>Can you point me to the specific part in the specification which would >indicate this is a bug vs >the standard? The relevant material is on page 49 of the standard. You may find the standard here: https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.416-199303-I!!PDF-E&type=items ``A pa

[dev] [st] Two flaws with ISO 8613-6 colors, checking

2018-09-08 Thread Programmer
I'm curious about the state of my patches. I've not seen them added to the current version of st. Am I simply being impatient or is there something wrong with them? Also, my last questions don't seem to have been responded to. Are there any thoughts on them now?

Re: [dev] [st] Two flaws with ISO 8613-6 colors, proper

2018-07-26 Thread Programmer
On Thu, 26 Jul 2018 09:31:39 +0200, Hiltjo Posthuma wrote: > I'm curious, is there a specific program you use where this bug is noticable? I noticed this bug present in every terminal emulator I've tested; I've been writing a terminal abstraction library, as the language I'm using lacks a good

[dev] [st] Two flaws with ISO 8613-6 colors, proper

2018-07-25 Thread Programmer
Follows is the proper form of the st patch submitted earlier, st-fix_8613_colors-0.8.1.diff: diff -up st-0.8.1/st.c st-0.8.1-changed/st.c --- st-0.8.1/st.c Tue Mar 20 15:29:59 2018 +++ st-0.8.1-changed/st.c Wed Jul 25 13:55:16 2018 @@ -1157,7 +1157,7 @@ csiparse(void)

[dev] [st] Two flaws with ISO 8613-6 colors, continued

2018-07-13 Thread Programmer
7;ll still release these six changed lines to the public domain, for simplicity: diff -c /home/programmer/st-0.8.1/st.c\~ /home/programmer/st-0.8.1/st.c *** /home/programmer/st-0.8.1/st.c~ Tue Mar 20 15:29:59 2018 --- /home/programmer/st-0.8.1/st.c Fri Jul 13 19:32:43 2018 *** ***

[dev] [st] Two flaws with ISO 8613-6 colors

2018-05-23 Thread Programmer
The relevant material is on page 49 of the standard. The first of the two issues is the least concerning: ``A parameter substring for values 38 or 48 may be divided by one or more separators (03/10) into parameter elements''... Due to the ``may'', it seems fair to interpret this as allowing eith

Re: [dev] [dwmstatus] barM.c security and enhancement patch.

2015-06-14 Thread Programmer Nerd
I was not aware of this. I have pushed my changes to the wiki. Thank you for telling me about this. On Sun, Jun 14, 2015 at 2:45 AM, Christoph Lohmann <2...@r-36.net> wrote: > Greetings. > > On Sun, 14 Jun 2015 09:45:31 +0200 Programmer Nerd > wrote: >> I noticed that b

[dev] [dwmstatus] barM.c security and enhancement patch.

2015-06-13 Thread Programmer Nerd
I noticed that barM.c obtained from here dwm.suckless.org/dwmstatus/barM.c was using fixed buffers without concern for the length of said buffer creating the possibility of a buffer overflow. I have also declared global variables and functions static because there is only one file. This may lead t

Re: [dev] GSoC 2010

2010-03-03 Thread eze . programmer
I think this is a good project idea, and it would prove more than useful also im looking forward to the simple port scanner, these project ideas have caugth my attention. On Wed, Mar 03, 2010 at 03:41:12PM +0100, Nicolai Waniek wrote: > On 03/03/2010 02:46 PM, Peter John Hartman wrote: > > I agree

Re: [dev] AfD discussion of dwm Wikipedia article

2010-02-24 Thread eze . programmer
As you said, it is the first hit and it points to suckless.org i could not care less about what an article on wikipedia says about dwm, if a potential user reads the article, as long as the reference link points to suckless.org its cool with me. "...and nothing of value was lost" On Wed, Feb 24,