The open() system call in f8 really broken...

[Oliver Falk]

On 08/16/2007 05:16 PM, Steve Dickson wrote:
> Oliver Falk wrote:
>> Most developers I know, don't worry about >warnings<, but do if their
>> code aborts. If a developer then doesn't worry about the real (security)
>> problem, but only about the abort itself and just workaround that - it's
>> simply a fault... The other option? stderr "FIX YOUR OPEN :-P"; sleep
>> 600. :-)
>>
>> If you compile the whole Fedora tree, how many warnings will you see?
>> How many warnings are about 'better use mkstemp' - for security
>> reasons... If you don't abort you'll not catch the developers
>> attention... It's too bad, but true... Don't want to step on dev's toes
>> of course - it's for sure not true for *all* developers!
> I was talking about runtime warnings... Really nasty looking messages
> so they couldn't be ignored...

Oh well:
[of at pils ~]# banner nasty warning

#     #     #      #####   #######  #     #
##    #    # #    #     #     #      #   #
# #   #   #   #   #           #       # #
#  #  #  #     #   #####      #        #
#   # #  #######        #     #        #
#    ##  #     #  #     #     #        #
#     #  #     #   #####      #        #


#     #     #     ######   #     #  ###  #     #   #####
#  #  #    # #    #     #  ##    #   #   ##    #  #     #
#  #  #   #   #   #     #  # #   #   #   # #   #  #
#  #  #  #     #  ######   #  #  #   #   #  #  #  #  ####
#  #  #  #######  #   #    #   # #   #   #   # #  #     #
#  #  #  #     #  #    #   #    ##   #   #    ##  #     #
 ## ##   #     #  #     #  #     #  ###  #     #   #####


Yes, Steve I know what you meant - but I'm not sure if it will help -
especially GUI apps, where you wouldn't see the stderr... Many apps on
my desktop JustWork(tm), but in background they spot some ugly messages...

-of