Fedora Security

• Thread Index

• End of the line for this mailing list
  • From: "Matthew Miller" <mattdm@xxxxxxxxxx>
• Re: Failing Unicode check in perl-Prima
  • From: Petr Pisar <ppisar@xxxxxxxxxx>
• Re: Failing Unicode check in perl-Prima
  • From: Tomas Hoger <thoger@xxxxxxxxxx>
• Re: Failing Unicode check in perl-Prima
  • From: Siddhesh Poyarekar <siddhesh@xxxxxxxxxx>
• Re: Failing Unicode check in perl-Prima
  • From: Kevin Fenzi <kevin@xxxxxxxxx>
• Re: Failing Unicode check in perl-Prima
  • From: "Siddhesh Poyarekar" <siddhesh@xxxxxxxxxx>
• Failing Unicode check in perl-Prima
  • From: Petr Pisar <ppisar@xxxxxxxxxx>
• Re: I'm starting up the security meetings again
  • From: Michel Alexandre Salim <salimma@xxxxxxxxxxxxxxxxx>
• Re: I'm starting up the security meetings again
  • From: JT <jt@xxxxxxxxxxx>
• Re: I'm starting up the security meetings again
  • From: Justin Forbes <jmforbes@xxxxxxxxxxx>
• Re: I'm starting up the security meetings again
  • From: JT <jt@xxxxxxxxxxx>
• Re: I'm starting up the security meetings again
  • From: "Major Hayden" <major@xxxxxxxx>
• I'm starting up the security meetings again
  • From: JT <jt@xxxxxxxxxxx>
• Re: How to detect users who violate the rules of the code of conduct?
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: How to detect users who violate the rules of the code of conduct?
  • From: Robert <robertdaleweir@xxxxxxxxx>
• Wanted to join the Security Team Apprenticeship program.
  • From: JT <jt@xxxxxxxxxxx>
• How to detect users who violate the rules of the code of conduct?
  • From: "Ricardo Pinto" <rdelemospinto@xxxxxxxxx>
• How to detect users who violate the rules of the code of conduct?
  • From: "Ricardo Pinto" <rdelemospinto@xxxxxxxxx>
• Re: lsetxattr failed, SELINUX_ERR op=setxattr invalid_context
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• lsetxattr failed, SELINUX_ERR op=setxattr invalid_context
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Introduction - Security Team
  • From: Marcelo Piedra <marcelopiedracr@xxxxxxxxx>
• Re: Preparing openvpn3 packaging for review - openssl challenges
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Re: Preparing openvpn3 packaging for review - openssl challenges
  • From: David Sommerseth <dazo@xxxxxxxxxxxx>
• Re: Preparing openvpn3 packaging for review - openssl challenges
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Re: Preparing openvpn3 packaging for review - openssl challenges
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Preparing openvpn3 packaging for review - openssl challenges
  • From: David Sommerseth <dazo@xxxxxxxxxxxx>
• Remove QtWebKit4
  • From: "Christian Stadelmann" <genodeftest@xxxxxxxxxxxxxxxxx>
• Re: sshd PermitRootLogin yes, security impact
  • From: David Kaufmann <astra@xxxxxxxx>
• sshd PermitRootLogin yes, security impact
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Enforcing system crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Enforcing system crypto policies
  • From: David Kaufmann <astra@xxxxxxxx>
• Enforcing system crypto policies
  • From: Frank Ueberschar <frank.ueberschar@xxxxxxxxxx>
• Re: Introduction
  • From: Blaise Pabon <blaise@xxxxxxxxx>
• Introduction
  • From: "Antonette Caldwell" <antonettecaldwell@xxxxxxxxxxx>
• Re: assessment for GNOME dialog asking for user passphrase
  • From: David Kaufmann <astra@xxxxxxxx>
• assessment for GNOME dialog asking for user passphrase
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• [Fedocal] Reminder meeting : Hope XII
  • From: jasoncallaway@xxxxxxxxxxxxxxxxx
• [Fedocal] Reminder meeting : Kubernetes hack session
  • From: jasoncallaway@xxxxxxxxxxxxxxxxx
• [Fedocal] Reminder meeting : Kubernetes hack session
  • From: jasoncallaway@xxxxxxxxxxxxxxxxx
• starting smb results in AVC denial send_msg to avahi
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• No Fedora Red Team meeting tomorrow
  • From: Jason Callaway <jasoncallaway@xxxxxxxxxxxxxxxxx>
• Re: Red Container on Github
  • From: "Jeremy Young" <jrm16020@xxxxxxxxx>
• Re: Red Container on Github
  • From: Jason Callaway <jcallawa@xxxxxxxxxx>
• Re: Red Container on Github
  • From: Jason Callaway <jasoncallaway@xxxxxxxxxxxxxxxxx>
• Red Container on Github
  • From: "Jeremy Young" <jrm16020@xxxxxxxxx>
• [Fedocal] Reminder meeting : BSides Delaware
  • From: jasoncallaway@xxxxxxxxxxxxxxxxx
• [Fedocal] Reminder meeting : FRT monthly team meeting
  • From: jasoncallaway@xxxxxxxxxxxxxxxxx
• [Fedocal] Reminder meeting : FCTL Development Sprint
  • From: jasoncallaway@xxxxxxxxxxxxxxxxx
• Red Team SIG calendar
  • From: Jason Callaway <jasoncallaway@xxxxxxxxxxxxxxxxx>
• Fedora Red Team meeting tomorrow
  • From: Jason Callaway <jcallawa@xxxxxxxxxx>
• Meetup at BruCon this week?
  • From: Till Maas <opensource@xxxxxxxxx>
• Re: Red Team SIG
  • From: "Paul W. Frields" <stickster@xxxxxxxxx>
• Re: Red Team SIG
  • From: Lorddemon <lorddemon@xxxxxxxxx>
• Re: Red Team SIG
  • From: Till Maas <opensource@xxxxxxxxx>
• Re: Red Team SIG
  • From: Jason Callaway <jcallawa@xxxxxxxxxx>
• Re: Red Team SIG
  • From: Hal Murray <hmurray@xxxxxxxxxxxxxxx>
• Re: rogue "Fedora" ami's in aws frontier regions
  • From: Bowe Strickland <bowe@xxxxxxxxxx>
• Re: Red Team SIG
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Red Team SIG
  • From: Jason Callaway <jcallawa@xxxxxxxxxx>
• Re: rogue "Fedora" ami's in aws frontier regions
  • From: Bowe Strickland <bowe@xxxxxxxxxx>
• Re: rogue "Fedora" ami's in aws frontier regions
  • From: Jason L Tibbitts III <tibbs@xxxxxxxxxxx>
• rogue "Fedora" ami's in aws frontier regions
  • From: Bowe Strickland <bowe@xxxxxxxxxx>
• Fwd: [oss-security] Qualys Security Advisory - The Stack Clash
  • From: Cliff Perry <cperry@xxxxxxxxxx>
• Re: Modularity and needed changes on CVE handling side?
  • From: Stanislav Ochotnicky <sochotni@xxxxxxxxxx>
• Re: Modularity and needed changes on CVE handling side?
  • From: Tomas Hoger <thoger@xxxxxxxxxx>
• Re: Modularity and needed changes on CVE handling side?
  • From: "Stanislav Ochotnicky" <sochotni@xxxxxxxxxxxxxxxxx>
• Re: Modularity and needed changes on CVE handling side?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Modularity and needed changes on CVE handling side?
  • From: Stanislav Ochotnicky <sochotnicky@xxxxxxxxxx>
• KeepassXC audit
  • From: Germano Massullo <germano.massullo@xxxxxxxxx>
• Re: Security team??
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: Security team??
  • From: Miloslav Trmac <mitr@xxxxxxxxxx>
• Ruxcon 2017 Call For Presentations
  • From: cfp@xxxxxxxxxxxxx
• Re: Security team??
  • From: David Eisenstein <deisenstein@xxxxxxx>
• Security team??
  • From: David Eisenstein <deisenstein@xxxxxxx>
• fedora crypto consolidation
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: today's high-publicity security issue
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• today's high-publicity security issue
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• TLS scan results for July 2016
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• TLS scan results for June 2016
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• TLS scan results for May 2016
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• cipherscan
  • From: cla@xxxxxxxxxxxxx
• TLS scan results for April 2016
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• TLS scan results for March 2016
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• TLS scan results for February 2016 (incomplete)
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• TLS scan results for January 2016
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• TLS scan results for December 2015
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• updating the fedora defensive guide
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: Maintainer for gnupg (and related) packages not responding – CVE unfixed
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Re: Maintainer for gnupg (and related) packages not responding – CVE unfixed
  • From: "Christian Stadelmann" <genodeftest@xxxxxxxxxxxxxxxxx>
• Re: Maintainer for gnupg (and related) packages not responding – CVE unfixed
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Maintainer for gnupg (and related) packages not responding – CVE unfixed
  • From: "Christian Stadelmann" <genodeftest@xxxxxxxxxxxxxxxxx>
• Re: LiveUSBCreator as Primary Downloadable
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: LiveUSBCreator as Primary Downloadable
  • From: Zachary Oglesby <zach@xxxxxxxxxx>
• LiveUSBCreator as Primary Downloadable
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Fwd: Retiring sectool -- Follow on for Apprentice wiki Feedback
  • From: "Corey 'linuxmodder' Sheldon" <sheldon.corey@xxxxxxxxx>
• Re: restricting the scope of CA certificates
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: restricting the scope of CA certificates
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: restricting the scope of CA certificates
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Re: restricting the scope of CA certificates
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: restricting the scope of CA certificates
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Re: restricting the scope of CA certificates
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: restricting the scope of CA certificates
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: restricting the scope of CA certificates
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• restricting the scope of CA certificates
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Entering a user namespace from a core_pattern helper
  • From: Jakub Filak <jfilak@xxxxxxxxxx>
• Re: GPU acceleration in Fedora Security Lab?
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: GPU acceleration in Fedora Security Lab?
  • From: Corey Sheldon <sheldon.corey@xxxxxxxxx>
• GPU acceleration in Fedora Security Lab?
  • From: "Roger Karlsson" <roger@xxxxxxxxxxxxx>
• Ruxcon 2016 Call For Presentations
  • From: cfp@xxxxxxxxxxxxx
• Re: NM generated IPv6 addresses leak your MAC address
  • From: P J P <pjp@xxxxxxxxxxxxxxxxx>
• Re: NM generated IPv6 addresses leak your MAC address
  • From: David Kaufmann <astra@xxxxxxxx>
• Re: NM generated IPv6 addresses leak your MAC address
  • From: Stephen John Smoogen <smooge@xxxxxxxxx>
• Use suid_dumpable=2 for development releases
  • From: Jakub Filak <jfilak@xxxxxxxxxx>
• Re: NM generated IPv6 addresses leak your MAC address
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• NM generated IPv6 addresses leak your MAC address
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Open source decision system engineering
  • From: olivier.avenel@xxxxxxxxxxxxx
• TLS scan results for November 2015
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• TLS scan results for October 2015
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• TLS scan results for September 2015
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• TLS scan results for August 2015
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• CFP: Security Devroom @ FOSDEM'16
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: selinux labels changed by restorecon after clean install
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• selinux labels changed by restorecon after clean install
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: firewall request
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: firewall request
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• firewall request
  • From: Andrew Walton <andrewfixcomputer@xxxxxxxxx>
• Re: More firewall request
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: More firewall request
  • From: Kurt Seifried <kseifried@xxxxxxxxxx>
• More firewall request
  • From: Andrew Walton <andrewfixcomputer@xxxxxxxxx>
• TLS scan results for July 2015
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Suspicious behavior of packagekit
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Suspicious behavior of packagekit
  • From: Lee Fuller <leefuller23@xxxxxxxxx>
• Suspicious behavior of packagekit
  • From: "S.Mohammad Emami Razavi" <emamirazavi@xxxxxxxxx>
• TLS scan results for June 2015
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• TLS scan results for May 2015
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Ruxcon 2015 Final Call For Presentations
  • From: cfp@xxxxxxxxxxxxx
• Re: rngd read errors at boot time
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: rngd read errors at boot time
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• RE: rngd read errors at boot time
  • From: "Brandon Vincent (Student)" <Brandon.Vincent@xxxxxxx>
• Re: rngd read errors at boot time
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: rngd read errors at boot time
  • From: "Menerick, John" <jmenerick@xxxxxxxxxxxx>
• RE: rngd read errors at boot time
  • From: "Brandon Vincent (Student)" <Brandon.Vincent@xxxxxxx>
• rngd read errors at boot time
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: [Guidelines change] Changes to the packaging guidelines
  • From: fche@xxxxxxxxxx (Frank Ch. Eigler)
• TLS scan results for April 2015
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Breakpoint 2015 Call For Presentations
  • From: cfp@xxxxxxxxxxxxx
• F23: disable RC4 and SSL 3.0 by default
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: critical path security update policy
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: critical path security update policy
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: critical path security update policy
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: critical path security update policy
  • From: "Jerry Bratton" <JerryLBratton@xxxxxxxx>
• Re: critical path security update policy
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• critical path security update policy
  • From: "Jerry Bratton" <JerryLBratton@xxxxxxxx>
• Ruxcon 2015 Call For Presentations
  • From: cfp@xxxxxxxxxxxxx
• Re: caml-crush in F22
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• caml-crush in F22
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: TLS scan results for March 2015
  • From: Joe Wulf <joe_wulf@xxxxxxxxx>
• TLS scan results for March 2015
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: TLS scan results for February 2015
  • From: Julien Vehent <julien@xxxxxxxxxxxxxx>
• Re: TLS scan results for February 2015
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: TLS scan results for February 2015
  • From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
• TLS scan results for February 2015
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Stephen John Smoogen <smooge@xxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Stephen John Smoogen <smooge@xxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Stephen John Smoogen <smooge@xxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Stephen John Smoogen <smooge@xxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Stephen John Smoogen <smooge@xxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Stephen John Smoogen <smooge@xxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Anaconda 22.17+ enforces "good" passwords
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Anaconda 22.17+ enforces "good" passwords
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• boston-area security event that might be of interest Boston College
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: System crypto policies vs gnutls upstream compatibility
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• System crypto policies vs gnutls upstream compatibility
  • From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
• Re: Android Emulator not working with 3.18.3-201.fc21 and onwards
  • From: Sudhir Khanger <ml@xxxxxxxxxxxxxxxxx>
• TLS scan results for January 2015
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• boston-area security conference call for papers
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• TLS scan results for December 2014
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Question about rpm package version comparaison for security update.
  • From: Paul Howarth <paul@xxxxxxxxxxxx>
• Question about rpm package version comparaison for security update.
  • From: MONLONG Pierre <pierre.monlong@xxxxxxxxxxxxxxx>
• System-wide crypto policy transition tracker
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: [clamav-users] Which anti-virus do you prefer on Linux desktop?
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Fwd: Re: [clamav-users] Which anti-virus do you prefer on Linux desktop?
  • From: Franklin Wang <franklinwang21st@xxxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: P J P <pj.pandit@xxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Simo Sorce <simo@xxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: P J P <pj.pandit@xxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Simo Sorce <simo@xxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: P J P <pj.pandit@xxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Simo Sorce <simo@xxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Kurt Seifried <kseifried@xxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Dennis Gilmore <dennis@xxxxxxxx>
• Re: RFC: Including Mozilla recommended cipher suites in mod_ssl conf file
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: RFC: Including Mozilla recommended cipher suites in mod_ssl conf file
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• TLS scan results for November 2014
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Ongoing open-firewall discussion
  • From: Stephen John Smoogen <smooge@xxxxxxxxx>
• Re: Ongoing open-firewall discussion
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• freeradius-client
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: RFC: Including Mozilla recommended cipher suites in mod_ssl conf file
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: RFC: Including Mozilla recommended cipher suites in mod_ssl conf file
  • From: Brandon Vincent <Brandon.Vincent@xxxxxxx>
• Re: RFC: Including Mozilla recommended cipher suites in mod_ssl conf file
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: RFC: Including Mozilla recommended cipher suites in mod_ssl conf file
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• RFC: Including Mozilla recommended cipher suites in mod_ssl conf file
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Kurt Seifried <kseifried@xxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Tristan Santore <tristan.santore@xxxxxxxxxxxxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Brandon Vincent <Brandon.Vincent@xxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Brandon Vincent <Brandon.Vincent@xxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: P J P <pj.pandit@xxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Tristan Santore <tristan.santore@xxxxxxxxxxxxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: P J P <pj.pandit@xxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Petr Lautrbach <plautrba@xxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Richard Z <rz@xxxxxxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Petr Lautrbach <plautrba@xxxxxxxxxx>
• Re: About sshd(8) PermitRootLogin=no
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• About sshd(8) PermitRootLogin=no
  • From: P J P <pj.pandit@xxxxxxxxxxx>
• Re: crypto policies for F21 without SSL 3.0?
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: crypto policies for F21 without SSL 3.0?
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: crypto policies for F21 without SSL 3.0?
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: crypto policies for F21 without SSL 3.0?
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: crypto policies for F21 without SSL 3.0?
  • From: Julien Vehent <julien@xxxxxxxxxxxxxx>
• Re: crypto policies for F21 without SSL 3.0?
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: crypto policies for F21 without SSL 3.0?
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• crypto policies for F21 without SSL 3.0?
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: Let's Encrypt
  • From: Kurt Seifried <kseifried@xxxxxxxxxx>
• Let's Encrypt
  • From: Pete Travis <me@xxxxxxxxxxxxxx>
• Re: defensive-coding update for F21
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [Secure Coding] master: GNUTLS: Document that the pitfalls have been addressed (9eb72b4)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• Re: defensive-coding update for F21
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: Fedora security vs Debian
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: defensive-coding update for F21
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [Report] FAD - 1 Nov 2014 - theme security
  • From: P J P <pj.pandit@xxxxxxxxxxx>
• Fwd: Fedora security vs Debian
  • From: Isaac Cortés González <w.isaac.cortes@xxxxxxxxx>
• Re: Fedora security vs Debian
  • From: Gene Czarcinski <gczarcinski@xxxxxxxxx>
• Re: Fedora security vs Debian
  • From: Kurt Seifried <kseifried@xxxxxxxxxx>
• Fedora security vs Debian
  • From: "max.lulu.07@xxxxxxxxxxx" <max.lulu.07@xxxxxxxxxxx>
• Re: Anything like security-announces on Fedora?
  • From: Richard Z <rz@xxxxxxxxxxxxxx>
• Re: Anything like security-announces on Fedora?
  • From: Kurt Seifried <kseifried@xxxxxxxxxx>
• Re: Anything like security-announces on Fedora?
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: Anything like security-announces on Fedora?
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Anything like security-announces on Fedora?
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: Anything like security-announces on Fedora?
  • From: Major Hayden <major@xxxxxxxx>
• Re: Anything like security-announces on Fedora?
  • From: Kurt Seifried <kseifried@xxxxxxxxxx>
• Re: Anything like security-announces on Fedora?
  • From: Major Hayden <major@xxxxxxxx>
• Re: Anything like security-announces on Fedora?
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Anything like security-announces on Fedora?
  • From: Kurt Seifried <kseifried@xxxxxxxxxx>
• Anything like security-announces on Fedora?
  • From: Richard Z <rz@xxxxxxxxxxxxxx>
• TLS scan results for October 2014
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• defensive-coding update for F21
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• changes for F21 in securing-tls
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• [Secure Coding] master: Update revision history in preparation of publication (0ef43f9)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Shell: Use a snippet for the input validation example (0c1d3d4)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Add support for shell snippets (0026cc0)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Shell: Fix internal reference (b7ec6fc)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Shell: Update section on input validation (e23c383)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Shell: Example code for recognizing non-negative integers (01cf74a)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Add a chapter on shell programming (2a82911)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Go Marshaling: Fix section title (00ae7f5)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Go: Fix typo (fab2049)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• Fedora Activity Day - 1st Nov 2014 - theme security
  • From: P J P <pj.pandit@xxxxxxxxxxx>
• TLS Scan results for September 2014
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Bash: CVE-2014-6277
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: TLS scan results for August 2014
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: TLS scan results for August 2014
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• TLS scan results for August 2014
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: question about uploading of core dumps to generate a backtrace for ABRT
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• Re: question about uploading of core dumps to generate a backtrace for ABRT
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• question about uploading of core dumps to generate a backtrace for ABRT
  • From: Jakub Filak <jfilak@xxxxxxxxxx>
• [Secure Coding] master: Go: Add section on deserialization (1865417)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• Re: proposed text for crypto-policies in Packaging Guidelines
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: proposed text for crypto-policies in Packaging Guidelines
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: proposed text for crypto-policies in Packaging Guidelines
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: proposed text for crypto-policies in Packaging Guidelines
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: proposed text for crypto-policies in Packaging Guidelines
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: proposed text for crypto-policies in Packaging Guidelines
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: proposed text for crypto-policies in Packaging Guidelines
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: proposed text for crypto-policies in Packaging Guidelines
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: proposed text for crypto-policies in Packaging Guidelines
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: proposed text for crypto-policies in Packaging Guidelines
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: proposed text for crypto-policies in Packaging Guidelines
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: proposed text for crypto-policies in Packaging Guidelines
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: proposed text for crypto-policies in Packaging Guidelines
  • From: Tristan Santore <tristan.santore@xxxxxxxxxxxxxxxxxxxxx>
• Re: proposed text for crypto-policies in Packaging Guidelines
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• proposed text for crypto-policies in Packaging Guidelines
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• TLS Survey for July 2014
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• [Secure Coding] master: Update revision history in preparation of publication (5bf22d9)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Update the copyright date (e2bab31)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• Ruxcon 2014 Final Call For Presentations
  • From: cfp@xxxxxxxxxxxxx
• Wanted: A small crew for working on security bugs in Fedora
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• [Secure Coding] master: Removed file not ready for publication (172ce9c)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Marked up more fo this chapter (a650892)
  • From: sparks@xxxxxxxxxxxxxxxxx
• TLS Survey for June 2014
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Need help building updated version (1.0.0m) of OpenSSL for FC16
  • From: Kurt Seifried <kseifried@xxxxxxxxxx>
• Need help building updated version (1.0.0m) of OpenSSL for FC16
  • From: "Bernal, Daniel L" <daniel.l.bernal@xxxxxxxxx>
• Re: question about audit _by default_ in Fedora cloud images
  • From: Miloslav Trmač <mitr@xxxxxxxx>
• Re: [sparks@xxxxxxxxxxxxxxxxx: Re: Reviewing/editing VPN information]
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: Reviewing/editing VPN information
  • From: Hal Murray <hmurray@xxxxxxxxxxxxxxx>
• Re: Reviewing/editing VPN information
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Auditing the Fedora Security Guide
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Reviewing/editing VPN information
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: question about audit _by default_ in Fedora cloud images
  • From: Major Hayden <major@xxxxxxxx>
• question about audit _by default_ in Fedora cloud images
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: Reviewing/editing VPN information
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Reviewing/editing VPN information
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: [Secure Coding] master: Added RSA key generation procedures (56f3511)
  • From: Pavel Kankovsky <peak@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Reviewing/editing VPN information
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Reviewing/editing VPN information
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: Review of obs-sign
  • From: Pavel Kankovsky <peak@xxxxxxxxxxxxxxxxxxxxxx>
• Reviewing/editing VPN information
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: [Secure Coding] master: Added RSA key generation procedures (56f3511)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [Secure Coding] master: Added RSA key generation procedures (56f3511)
  • From: Pavel Kankovsky <peak@xxxxxxxxxxxxxxxxxxxxxx>
• [Secure Coding] master: C: Add example for unsigned overflow check (e97e4dc)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Serialization: Add section on fragmentation and reassembly (01bd390)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Packaging: Adjust RPM flags of key-related files (f5803d1)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Packaging: Fix RPM macro issue (11ef1e6)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Packaging: Add section on delayed certificate generation (dc0ff1a)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• Re: available crypto policies
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: available crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: available crypto policies
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: available crypto policies
  • From: Kurt Seifried <kseifried@xxxxxxxxxx>
• Re: available crypto policies
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• OpenSSL MITM CCS injection attack (CVE-2014-0224)
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Review of obs-sign
  • From: Bruno Wolff III <bruno@xxxxxxxx>
• Re: Review of obs-sign
  • From: Simo Sorce <simo@xxxxxxxxxx>
• Re: Review of obs-sign
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: Review of obs-sign
  • From: Miroslav Suchý <msuchy@xxxxxxxxxx>
• Re: Review of obs-sign
  • From: Pavel Kankovsky <peak@xxxxxxxxxxxxxxxxxxxxxx>
• Re: available crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: available crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: available crypto policies
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: available crypto policies
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Re: available crypto policies
  • From: Till Maas <opensource@xxxxxxxxx>
• Re: available crypto policies
  • From: Till Maas <opensource@xxxxxxxxx>
• Re: available crypto policies
  • From: Till Maas <opensource@xxxxxxxxx>
• Re: available crypto policies
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: available crypto policies
  • From: Simo Sorce <simo@xxxxxxxxxx>
• Re: available crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: available crypto policies
  • From: Till Maas <opensource@xxxxxxxxx>
• [Secure Coding] master: Added instructions for generating ECDSA keys (d335815)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Added installation instructions (72a9fc4)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Merge branch 'master' of git+ssh://git.fedorahosted.org/git/secure-coding (cd5d541)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Added RSA key generation procedures (56f3511)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Add auto-generated XML for the Go code snippets (a9229ae)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• what do you think about disabling syscall auditing by default?
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• [Secure Coding] master: Added cipher suite list for HIGH, MEDIUM, LOW, and EXPORT. (76d3687)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Marked guide as draft (caf2443)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Merge branch 'master' of git+ssh://git.fedorahosted.org/git/secure-coding (547d801)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Started OpenSSL chapter and added it to the guide for testing (e9907e4)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Fixed the Rev Hx for initial creation (f62a564)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Added productnumber back in until I can figure out how to remove it and still make the guide build (41d933e)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Updated abstract and description (7c3af12)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Added myself to the author list (0c41b02)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Added copyright owner (167374c)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Finished annotating the ssl.conf file example (6f16df3)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Started working on explaining the mod_ssl config file. (25f7118)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Fixed broken ascii (40444c2)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Removed duplicate file (537169f)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Added intro and default ssl.conf file (3aacde3)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Added blank chapters for topics we want to cover. (001aa4a)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Changed from article to a book (c5afb3f)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Merge branch 'master' of git+ssh://git.fedorahosted.org/git/secure-coding (8341df7)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Starting new guide for Securing TLS (7ada5ed)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Add chapter on Go (13faeec)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Add a short chapter on Vala (2988ebd)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: sect-Defensive_Coding-C-Use-After-Free: New section ID (199b3ed)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• Re: developing the "critical updates repo" plan
  • From: Pavel Kankovsky <peak@xxxxxxxxxxxxxxxxxxxxxx>
• Re: developing the "critical updates repo" plan
  • From: Kevin Fenzi <kevin@xxxxxxxxx>
• Re: developing the "critical updates repo" plan
  • From: Dennis Gilmore <dennis@xxxxxxxx>
• Re: developing the "critical updates repo" plan
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: developing the "critical updates repo" plan
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: developing the "critical updates repo" plan
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: developing the "critical updates repo" plan
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: Review of obs-sign
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: developing the "critical updates repo" plan
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: developing the "critical updates repo" plan
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: developing the "critical updates repo" plan
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Re: developing the "critical updates repo" plan
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: developing the "critical updates repo" plan
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Review of obs-sign
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Review of obs-sign
  • From: Miroslav Suchý <msuchy@xxxxxxxxxx>
• developing the "critical updates repo" plan
  • From: Matthew Miller <mattdm@xxxxxxxxxx>
• Re: TLS Survey for May 2014
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: TLS Survey for May 2014
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• TLS Survey for May 2014
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Ruxcon 2014 Call For Papers
  • From: cfp@xxxxxxxxxxxxx
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Pavel Kankovsky <peak@xxxxxxxxxxxxxxxxxxxxxx>
• Breakpoint 2014 Call For Presentations
  • From: cfp@xxxxxxxxxxxxx
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Miloslav Trmač <mitr@xxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Fwd: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Aaron Zauner <azet@xxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Pavel Kankovsky <peak@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Bruno Wolff III <bruno@xxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Aaron Zauner <azet@xxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Fedora crypto policy vs the real world Was: available crypto policies
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: [Secure Coding] master: sect-Defensive_Coding-TLS-OpenSSL: Mention "openssl genrsa" entropy issue (564ffc8)
  • From: Pavel Kankovsky <peak@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [Secure Coding] master: sect-Defensive_Coding-TLS-OpenSSL: Mention "openssl genrsa" entropy issue (564ffc8)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [Secure Coding] master: TLS: More balanced advice on "openssl genrsa" and /dev/urandom (7f640d9)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• Re: [Secure Coding] master: sect-Defensive_Coding-TLS-OpenSSL: Mention "openssl genrsa" entropy issue (564ffc8)
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Re: [Secure Coding] master: sect-Defensive_Coding-TLS-OpenSSL: Mention "openssl genrsa" entropy issue (564ffc8)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [Secure Coding] master: sect-Defensive_Coding-TLS-OpenSSL: Mention "openssl genrsa" entropy issue (564ffc8)
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Re: [Secure Coding] master: sect-Defensive_Coding-TLS-OpenSSL: Mention "openssl genrsa" entropy issue (564ffc8)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [Secure Coding] master: sect-Defensive_Coding-TLS-OpenSSL: Mention "openssl genrsa" entropy issue (564ffc8)
  • From: Tomas Mraz <tmraz@xxxxxxxxxx>
• Re: [Secure Coding] master: RPM packaging: X.509 key pair generation (95c2976)
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: [Secure Coding] master: RPM packaging: X.509 key pair generation (95c2976)
  • From: Joe Orton <jorton@xxxxxxxxxx>
• Re: [Secure Coding] master: sect-Defensive_Coding-TLS-OpenSSL: Mention "openssl genrsa" entropy issue (564ffc8)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [Secure Coding] master: sect-Defensive_Coding-TLS-OpenSSL: Mention "openssl genrsa" entropy issue (564ffc8)
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Fedora crypto policy vs the real world Was: available crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• [Secure Coding] master: sect-Defensive_Coding-TLS-OpenSSL: Mention "openssl genrsa" entropy issue (564ffc8)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Custom memory allocators: Complete sentence (eff2f5c)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: RPM packaging: X.509 key pair generation (95c2976)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• Re: TCP connections restricted to specific users
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: TCP connections restricted to specific users
  • From: Pavel Kankovsky <peak@xxxxxxxxxxxxxxxxxxxxxx>
• TCP connections restricted to specific users
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Developing a security Bat Signal?
  • From: Matthew Miller <mattdm@xxxxxxxxxx>
• Re: Developing a security Bat Signal?
  • From: Tristan Santore <tristan.santore@xxxxxxxxxxxxxxxxxxxxx>
• Re: Developing a security Bat Signal?
  • From: Matthew Miller <mattdm@xxxxxxxxxx>
• Re: Developing a security Bat Signal?
  • From: Miloslav Trmač <mitr@xxxxxxxx>
• Re: Developing a security Bat Signal?
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: Developing a security Bat Signal?
  • From: "Jóhann B. Guðmundsson" <johannbg@xxxxxxxxx>
• Re: Developing a security Bat Signal?
  • From: Matthew Miller <mattdm@xxxxxxxxxx>
• Re: Developing a security Bat Signal?
  • From: "Jóhann B. Guðmundsson" <johannbg@xxxxxxxxx>
• Re: Developing a security Bat Signal?
  • From: Matthew Miller <mattdm@xxxxxxxxxx>
• RE: Developing a security Bat Signal?
  • From: Mark Cox <mjc@xxxxxxxxxx>
• Re: Developing a security Bat Signal?
  • From: Tristan Santore <tristan.santore@xxxxxxxxxxxxxxxxxxxxx>
• RE: Developing a security Bat Signal?
  • From: Mark Cox <mjc@xxxxxxxxxx>
• Re: Developing a security Bat Signal?
  • From: Major Hayden <major@xxxxxxxx>
• Developing a security Bat Signal?
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: available crypto policies
  • From: Aaron Zauner <azet@xxxxxxxx>
• Re: available crypto policies
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: available crypto policies
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: available crypto policies
  • From: Aaron Zauner <azet@xxxxxxxx>
• Re: Crypto guidelines for Fedora
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: available crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Crypto guidelines for Fedora
  • From: Pavel Kankovsky <peak@xxxxxxxxxxxxxxxxxxxxxx>
• Re: available crypto policies
  • From: Aaron Zauner <azet@xxxxxxxx>
• Re: Crypto guidelines for Fedora
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Crypto guidelines for Fedora
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: Crypto guidelines for Fedora
  • From: Pavel Kankovsky <peak@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Crypto guidelines for Fedora
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Enable GCC hardening by default
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Crypto guidelines for Fedora
  • From: Pavel Kankovsky <peak@xxxxxxxxxxxxxxxxxxxxxx>
• Re: available crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: available crypto policies
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: available crypto policies
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: available crypto policies
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: available crypto policies
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: available crypto policies
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: available crypto policies
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: available crypto policies
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• available crypto policies
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• [Secure Coding] master: Revert "Yeah, these files are located in their own fhosted repo" (87df308)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Yeah, these files are located in their own fhosted repo (c3c9bf0)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Adding Secure Ruby Development Guide (70b828b)
  • From: sparks@xxxxxxxxxxxxxxxxx
• opinions on tcp wrappers?
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• F20 efi shim vendor certificate
  • From: "Leibowitz, Michael" <michael.leibowitz@xxxxxxxxx>
• [Secure Coding] master: Fix typos in "Robust argument list processing" section (045ff4f)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• Re: btrfs snapshots, rollbacks
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: btrfs snapshots, rollbacks
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: btrfs snapshots, rollbacks
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: btrfs snapshots, rollbacks
  • From: Till Maas <opensource@xxxxxxxxx>
• Re: btrfs snapshots, rollbacks
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: btrfs snapshots, rollbacks
  • From: Miloslav Trmač <mitr@xxxxxxxx>
• Re: btrfs snapshots, rollbacks
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: btrfs snapshots, rollbacks
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: btrfs snapshots, rollbacks
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: btrfs snapshots, rollbacks
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: btrfs snapshots, rollbacks
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: btrfs snapshots, rollbacks
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• btrfs snapshots, rollbacks
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Fedora 20 updates-testing report
  • From: Michel Alexandre Salim <salimma@xxxxxxxxxxxxxxxxx>
• Re: Crypto guidelines for Fedora
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Re: Crypto guidelines for Fedora
  • From: Till Maas <opensource@xxxxxxxxx>
• Re: Introduction
  • From: Tomas Hoger <thoger@xxxxxxxxxx>
• Re: Introduction
  • From: Joerg Stephan <johe.stephan@xxxxxxxxx>
• Re: Security update process without CVEs
  • From: Tomas Hoger <thoger@xxxxxxxxxx>
• Re: Introduction
  • From: Tomas Hoger <thoger@xxxxxxxxxx>
• Fwd: Security update process without CVEs
  • From: Dan Scott <denials@xxxxxxxxx>
• Re: Updating CSI Security Policy
  • From: Stephen John Smoogen <smooge@xxxxxxxxx>
• Updating CSI Security Policy
  • From: Joerg Stephan <johe.stephan@xxxxxxxxx>
• Re: enforcing a consistent crypto policy
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• enforcing a consistent crypto policy
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: enforcing a consistent crypto policy
  • From: Hubert Kario <hkario@xxxxxxxxxx>
• Introduction
  • From: Joerg Stephan <johe.stephan@xxxxxxxxx>
• Re: Crypto guidelines for Fedora
  • From: Miloslav Trmač <mitr@xxxxxxxx>
• Re: Crypto guidelines for Fedora
  • From: Christopher Meng <cickumqt@xxxxxxxxx>
• Re: Crypto guidelines for Fedora
  • From: Miloslav Trmač <mitr@xxxxxxxx>
• Crypto guidelines for Fedora
  • From: Till Maas <opensource@xxxxxxxxx>
• cppcheck(1) thread on -devel list
  • From: P J P <pj.pandit@xxxxxxxxxxx>
• [Secure Coding] master: Fix typos spotted by Kamil Dudka (39e08eb)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• Re: fedoraproject.org on Malware Domain List
  • From: Kevin Fenzi <kevin@xxxxxxxxx>
• Re: fedoraproject.org on Malware Domain List
  • From: Rohan Sheth <rohan@xxxxxxxxxx>
• fedoraproject.org on Malware Domain List
  • From: Manuel Faux <manuel.faux@xxxxxxx>
• Adding category to wiki pages
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• scap-security-guide-0.1-3 in Fedora -stable repository (AKA "Houston, Tranquillity Base here. The Eagle has landed.")
  • From: Jan Lieskovsky <jlieskov@xxxxxxxxxx>
• [Secure Coding] master: C Language: Mention mixed signed/unsigned comparisons (ace93c0)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• scap-security-guide now available in Fedora updates-testing repository
  • From: Jan Lieskovsky <jlieskov@xxxxxxxxxx>
• Re: Inheritable file system capabilities
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: prelink performance gains
  • From: Josh Bressers <bressers@xxxxxxxxxx>
• Re: prelink performance gains
  • From: Tristan Santore <tristan.santore@xxxxxxxxxxxxxxxxxxxxx>
• Re: prelink performance gains
  • From: Josh Bressers <bressers@xxxxxxxxxx>
• Re: prelink performance gains
  • From: Tristan Santore <tristan.santore@xxxxxxxxxxxxxxxxxxxxx>
• prelink performance gains
  • From: Dhiru Kholia <dhiru.kholia@xxxxxxxxx>
• Inheritable file system capabilities
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: Kashyap Chamarthy <kashyapc@xxxxxxxxxxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: F19 Firewall
  • From: Jiri Popelka <jpopelka@xxxxxxxxxx>
• Re: F19 Firewall
  • From: Lance Lassetter <lancelassetter@xxxxxxxxx>
• Re: F19 Firewall
  • From: Lance Lassetter <lancelassetter@xxxxxxxxx>
• Re: F19 Firewall
  • From: Jiri Popelka <jpopelka@xxxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: Emergency destruction of LUKS partition
  • From: Lyos Gemini Norezel <lyos.gemininorezel@xxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: Matthew Miller <mattdm@xxxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: "Jóhann B. Guðmundsson" <johannbg@xxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: Matthew Miller <mattdm@xxxxxxxxxx>
• Re: Emergency destruction of LUKS partition
  • From: aragonx@xxxxxxxxxx
• Re: Emergency destruction of LUKS partition
  • From: aragonx@xxxxxxxxxx
• Re: F19 Firewall
  • From: Lance Lassetter <lancelassetter@xxxxxxxxx>
• Re: Emergency destruction of LUKS partition
  • From: Richard Guy Briggs <rgb@xxxxxxxxxx>
• Re: Emergency destruction of LUKS partition
  • From: Bruno Wolff III <bruno@xxxxxxxx>
• Re: Emergency destruction of LUKS partition
  • From: Luke Macken <lmacken@xxxxxxxxxx>
• Re: Emergency destruction of LUKS partition
  • From: Tristan Santore <tristan.santore@xxxxxxxxxxxxxxxxxxxxx>
• Re: Emergency destruction of LUKS partition
  • From: Joe Wulf <joe_wulf@xxxxxxxxx>
• Re: Emergency destruction of LUKS partition
  • From: Kurt Seifried <kseifried@xxxxxxxxxx>
• Re: Emergency destruction of LUKS partition
  • From: Miloslav Trmač <mitr@xxxxxxxx>
• Re: Emergency destruction of LUKS partition
  • From: Tristan Santore <tristan.santore@xxxxxxxxxxxxxxxxxxxxx>
• Emergency destruction of LUKS partition
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: F19 Firewall
  • From: Jiri Popelka <jpopelka@xxxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: leaving setfcap in docker containers
  • From: "Jóhann B. Guðmundsson" <johannbg@xxxxxxxxx>
• leaving setfcap in docker containers
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: F19 Firewall
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxx>
• F19 Firewall
  • From: P J P <pj.pandit@xxxxxxxxxxx>
• Re: F19 Firewall
  • From: Lance Lassetter <lancelassetter@xxxxxxxxx>
• Re: F19 Firewall
  • From: Jiri Popelka <jpopelka@xxxxxxxxxx>
• Re: F19 Firewall
  • From: Lance Lassetter <lancelassetter@xxxxxxxxx>
• Re: F19 Firewall
  • From: Miloslav Trmač <mitr@xxxxxxxx>
• Re: F19 Firewall
  • From: Matthew Miller <mattdm@xxxxxxxxxx>
• Re: F19 Firewall
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: F19 Firewall
  • From: Miloslav Trmač <mitr@xxxxxxxx>
• Re: F19 Firewall
  • From: Miloslav Trmač <mitr@xxxxxxxx>
• Re: F19 Firewall
  • From: Miloslav Trmač <mitr@xxxxxxxx>
• Re: F19 Firewall
  • From: Daniel J Walsh <dwalsh@xxxxxxxxxx>
• Re: F19 Firewall
  • From: Lance Lassetter <lancelassetter@xxxxxxxxx>
• Re: F19 Firewall
  • From: Kurt Seifried <kseifried@xxxxxxxxxx>
• Re: F19 Firewall
  • From: P J P <pjp@xxxxxxxxxxxxxxxxx>
• Re: F19 Firewall
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• F19 Firewall
  • From: P J P <pjp@xxxxxxxxxxxxxxxxx>
• Re: cracklib dicts size (and fedora password policy)
  • From: Miloslav Trmač <mitr@xxxxxxxx>
• Re: New contributor Loïc Maury
  • From: Loïc Maury <lmaury@xxxxxxxxx>
• Re: New contributor Loïc Maury
  • From: Tristan Santore <tristan.santore@xxxxxxxxxxxxxxxxxxxxx>
• New contributor Loïc Maury
  • From: Loïc Maury <lmaury@xxxxxxxxx>
• Re: Compilation of Git Clone copy of Secure Coding Handbook
  • From: Tristan Santore <tristan.santore@xxxxxxxxxxxxxxxxxxxxx>
• Re: Compilation of Git Clone copy of Secure Coding Handbook
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [Secure Coding] master: Update the README file (a2df781)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: C++: Mention front(), back() and data() member functions of vectors (7db67ea)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: C++: Subscripting to read the NUL character in std::string not supported (e6ed150)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• Re: [Secure Coding] master: Updated POT files (749d19d)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: [Secure Coding] master: Updated POT files (749d19d)
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Compilation of Git Clone copy of Secure Coding Handbook
  • From: Tristan Santore <tristan.santore@xxxxxxxxxxxxxxxxxxxxx>
• Compilation of Git Clone copy of Secure Coding Handbook
  • From: Tristan Santore <tristan.santore@xxxxxxxxxxxxxxxxxxxxx>
• Re: [Secure Coding] master: Updated POT files (749d19d)
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• [Secure Coding] master: Started marking up new Web Applications chapter (a1dc2ad)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Merge branch 'master' of git+ssh://git.fedorahosted.org/git/secure-coding (630f7d9)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Updated POT files (749d19d)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Merge branch 'master' of git+ssh://git.fedorahosted.org/git/secure-coding (afbe090)
  • From: sparks@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Updated copyright date (0d2ea66)
  • From: sparks@xxxxxxxxxxxxxxxxx
• Re: cracklib dicts size (and fedora password policy)
  • From: Kurt Seifried <kurt@xxxxxxxxxxxx>
• Re: cracklib dicts size (and fedora password policy)
  • From: Miloslav Trmač <mitr@xxxxxxxx>
• [Secure Coding] master: C++: Warn about functions that deal with unpaired iterators (2067762)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: C++: Add section on iterators (f2167f7)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Add material on std::string (594eead)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: C++ operator new[] has been fixed in recent GCC versions (e32825c)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• Reproducible Builds in Fedora
  • From: Dhiru Kholia <dhiru.kholia@xxxxxxxxx>
• [Secure Coding] master: Regenerate snippets (5b90f99)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] master: Actually use strncat in the strncat example (805f9a8)
  • From: fweimer@xxxxxxxxxxxxxxxxx
• [Secure Coding] tag 'v1.1-1' created
  • From: fweimer@xxxxxxxxxxxxxxxxx
• Re: Fedora Security SIG Update
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Fedora Security SIG Update
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: Fedora Security SIG Update
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Fedora Security SIG Update
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: Fedora Security SIG Update
  • From: "Eric H. Christensen" <sparks@xxxxxxxxxxxxxxxxx>
• Re: Fedora Security SIG Update
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: cracklib dicts size (and fedora password policy)
  • From: Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>
• Re: cracklib dicts size (and fedora password policy)
  • From: Kurt Seifried <kseifried@xxxxxxxxxx>
• Re: cracklib dicts size (and fedora password policy)
  • From: Matthew Miller <mattdm@xxxxxxxxxx>