search for: fesco

...y more of a cfe-dev topic), As a follow-up to that old thread about -D_FORTIFY_SOURCE=n http://lists.llvm.org/pipermail/cfe-dev/2015-November/045845.html And, more recently, to this fedora thread where clang/llvm -D_FORTIFY_SOURCE support is claimed to be only partial: https://pagure.io/fesco/issue/2020 I dig into the glibc headers in order to have a better understanding of what's going on, and wrote my notes here: https://sergesanspaille.fedorapeople.org/fortify_source_requirements.rst TL;DR: clang does provide a similar compile-time checking as gcc, but no runtime checking....

...a 23: > https://fedoraproject.org/wiki/Changes/Standardized_passphrase_policy > > And the discussion for Workstation's behavior: > https://lists.fedoraproject.org/pipermail/desktop/2015-July/012588.html Kevin Fenzi responded to my post on Fedora testing saying that at least it is FESCO decisions this time, not just a one man one, and asked for patience. (My knee-jerk response is why are they even discussing it after last time, but I refrained.) Thank you for the links Chris. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver p...

...h and let the user decide. I don't like the change, but at the same time I do all of my installs with kickstart, and such installs are not affected. Kickstart files can contain a hashed password, and since a hashed password can't be checked, it can't be rejected. Thus, any decision FESCO makes won't affect me at all.

On Fri, Jan 30, 2015 at 03:39:47PM -0600, Frank Cox wrote: > On Fri, 30 Jan 2015 16:13:17 -0500 > Scott Robbins wrote: > > > You may have noticed how if Fedora, by some odd scheme, deems your password > > unworthy, you have to click Done two times. > > Centos 7 does that as well. Heh, I guess I've used good passwords in my installs then. -- Scott Robbins PGP

...As Martyn Plummer pointed out: There are currently 1533 packages/bundles on CRAN, not counting the recommended packages that are already distributed with R. Of these packages, 420 require to the R headers. Fedora only supplies RPMs for 9 of them. I'm not entirely sure if I need FESCo or FPC approval to take this action, if so, this is my notice of requesting it. ;) I'm also looking for feedback and comments, of course. Thanks, ~spot (Fedora R maintainer)

...roject.org/wiki/Changes/Standardized_passphrase_policy >> >> And the discussion for Workstation's behavior: >> https://lists.fedoraproject.org/pipermail/desktop/2015-July/012588.html > > Kevin Fenzi responded to my post on Fedora testing saying that at least it > is FESCO decisions this time, not just a one man one, and asked for > patience. (My knee-jerk response is why are they even discussing it after > last time, but I refrained.) Thank you for the links Chris. > I can certainly see why it can annoy certain people. I think a better solution to suit...

...ide. > > I don't like the change, but at the same time I do all of my installs > with kickstart, and such installs are not affected. Kickstart files can > contain a hashed password, and since a hashed password can't be checked, > it can't be rejected. Thus, any decision FESCO makes won't affect me at > all. One thing that people don't understand or don't want to address is that most KNOWN instances of a Linux machine being hacked/owned/pwned/taken over (substitute your word here) and then rooted happen because of weak passwords. It is certainly one'...

This might show up twice, I think I sent it from a bad address previously. If so, please accept my apologies. In Fedora 22, one developer (and only one) decided that if the password chosen during installation wasn't of sufficient strength, the install wouldn't continue. A bug was filed, and there was also a great deal of aggravation about it on the Fedora testing list. So, it was

...Y_SOURCE=n > > > > http://lists.llvm.org/pipermail/cfe-dev/2015-November/045845.html > > > > And, more recently, to this fedora thread where clang/llvm - > > D_FORTIFY_SOURCE > > support is claimed to be only partial: > > > > https://pagure.io/fesco/issue/2020 > > > > I dig into the glibc headers in order to have a better understanding of > what's > > going on, and wrote my notes here: > > > > > https://sergesanspaille.fedorapeople.org/fortify_source_requirements.rst > > > > TL;DR: clang does...