Re: Philip Brown...United Way of Manatee County
Dave Horsfall wrote: In other words, the FreeBSD lists, by permitting non-subscribers to post to them, are spam-magnets. And the spammers know this. Yep. Most FreeBSD mailing lists do not use e.g. greylisting or something along those lines. And as a result, a lot of spam gets through. Personally I would definitely welcome a scheme where new posters need to be approved by moderators who can blacklist spammers and whitelist genuine submitters, but there probably isn't enough manpower to make that happen. I for one would be perfectly happy to help, but it would take (a hell of a lot) more than just little old me to do the job. AvW -- I'm not completely useless, I can be used as a bad example. pgp3gzmsK8v22.pgp Description: PGP signature
Re: devel/dbus no longer starts at system poweron
On Mon, Mar 2, 2015 at 12:53 PM, Jeffrey Bouquet via freebsd-ports freebsd-ports@freebsd.org wrote: On 03/02/15 06:57, Beeblebrox wrote: Using dbus-1.8.12, /etc/rc.conf has (dbus_enable=YES, slim_enable=YES). This works no more. X.Org starts, but cannot login to any Desktop because dbus actually is not running and has not started. Kill Xorg, then manually service onestart dbus, and slim. I can then start to my desktop managers. what do dmesg and /var/log/messages say? Erich This problem was resolved some time back (through an update I believe) but is now back. No error message is registered in /var/log/messages or any other log. However, combing through the output on TTY0, I found this: Starting dbus Shared object 'libexpat.so.1' not found required by 'dbus-daemon' /etc/rc: WARNING: failed to start dbus After system is booted, form any TTY*, # service dbus onestart results in normal startup. Not setting any dbus_flags and not using gdm_enable. # pkg info -l expat expat-2.1.0_2: /usr/local/bin/xmlwf /usr/local/include/expat.h /usr/local/include/expat_external.h /usr/local/lib/libexpat.a /usr/local/lib/libexpat.so /usr/local/lib/libexpat.so.1 /usr/local/lib/libexpat.so.1.6.0 /usr/local/lib/libexpat.so.6 /usr/local/libdata/pkgconfig/expat.pc /usr/local/man/man1/xmlwf.1.gz (files separately confirmed with ls /usr/local/lib/*expat*) I've the same problem (libexpat and dbus-daemon) and posted to the freebsd-current list a few days ago. Rebuilt every dependency... etc. One other port also does not start *uuid* ... This is almost certainly an issue with a circular dependency in the startup scripts. The immediate problem is that things that require non-base dependencies are starting before ldconfig is run (started?). I have noted a circular dependency between dbus and webcamd. I have not had time to track it down. These are a real pain to track down as you need to examine the full dependency graph to be sure of finding the issue. You can check for circular dependencies with the command: rcorder /etc/rc.d/* /usr/local/etc/rc.d/* /dev/null This only reports the errors (if any), not the cause. To track that down the actual cause, you will likely have to dig through the full output (no /dev/null). Circular dependencies result in undefined behavior and the ordering can be changed radically in very unexpected ways by adding/updating/deleting ports. Minor changes to rcorder.c could also change these. I think the best answer is to provide an option to have rcorder print the full dependency tree for all ports involved in the circular dependency so it can be more easily tracked. I have no idea how difficult this might be, but, without examining the code, it looks like it should not be too hard. (Easily said by someone who can read but not really write decent C code.) -- Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
configure of x11-themes/fvwm-themes fails
shige 03/03 2015
I tried to install /usr/ports/x11-themes/fvwm-themes on FreeBSD-10.1
(sparc64), but the following messages appeared at configure:
...
checking for fvwm-config... /usr/local/bin/fvwm-config
checking for FvwmM4... /usr/local/libexec/fvwm/2.6.5/FvwmM4
configure: error:
You have fvwm-2.6.5, which is not up to date
You need at least fvwm-2.5.8
=== Script configure failed unexpectedly.
Please report the problem to po...@freebsd.org [maintainer]
and attach the /usr/ports/x11-themes/fvwm-themes/work/
fvwm-themes-0.7.0/config.log including the output of the
failure of your make command. Also, it might be a good idea
to provide an overview of all packages installed on your
system (e.g. a /usr/local/sbin/pkg-static info -g -Ea).
*** Error code 1
The configure of fvwm-themes-0.7.0 has the following line:
if (echo $REQUIRED_FVWM_VERSION; echo $FVWM_VERSION) \
| sed 's/\./ /g' | uniq | sort -n +0 -1 +1 -2 +2 -3 -c 2/dev/null; then
but for BSD sort, I think it should be
if (echo $REQUIRED_FVWM_VERSION; echo $FVWM_VERSION) \
| sed 's/\./ /g' | uniq | sort -n +0 -3 -c 2/dev/null; then
++
Shigeharu TAKENO NIigata Institute of Technology
kashiwazaki,Niigata 945-1195 JAPAN
sh...@iee.niit.ac.jp TEL(FAX): +81-257-22-8161
++
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.57. Invocation command line was
$ ./configure --x-libraries=/usr/local/lib --x-includes=/usr/local/include
--prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/
--build=sparc64-portbld-freebsd10.1
## - ##
## Platform. ##
## - ##
hostname = nmes03
uname -m = sparc64
uname -r = 10.1-RELEASE
uname -s = FreeBSD
uname -v = FreeBSD 10.1-RELEASE #0 r274401: Wed Nov 12 03:17:34 UTC 2014
r...@releng1.nyi.freebsd.org:/usr/obj/sparc64.sparc64/usr/src/sys/GENERIC
/usr/bin/uname -p = sparc64
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /sbin
PATH: /bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /usr/games
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /root/bin
## --- ##
## Core tests. ##
## --- ##
configure:1146: loading site script /usr/ports/Templates/config.site
| # $FreeBSD: head/Templates/config.site 349240 2014-03-26 11:16:42Z bapt $
| # Do not add:
| # - toolchain related
| # - arch-dependent values
| # - anything =no unless guaranteed to never be
| # implemented in FreeBSD
| # - also avoid working values
| # This file must reflect the oldest supported Release.
| #
| #MAINTAINER= port...@freebsd.org
|
| # Path
| : ${ac_cv_path_BZIP2=/usr/bin/bzip2}
| : ${ac_cv_path_EGREP=/usr/bin/egrep}
| : ${ac_cv_path_FGREP=/usr/bin/fgrep}
| : ${ac_cv_path_GREP=/usr/bin/grep}
| : ${ac_cv_path_GZIP=/usr/bin/gzip}
| : ${ac_cv_path_MKTEMP_COMMAND=/usr/bin/mktemp}
| : ${ac_cv_path_SED=/usr/bin/sed}
| : ${ac_cv_path_install=/usr/bin/install}
| : ${ac_cv_path_mkdir=/bin/mkdir}
| : ${ac_cv_prog_AWK=/usr/bin/awk}
| : ${ac_cv_prog_SED=/usr/bin/sed}
| : ${am_cv_prog_tar_ustar=/usr/bin/tar}
| : ${cl_cv_prog_LN=/bin/ln}
| : ${cl_cv_prog_cp='/bin/cp -p'}
| : ${lt_cv_path_MAGIC_CMD=/usr/bin/file}
|
| # Headers
| : ${ac_cv_header_alloca_h=no}
| : ${ac_cv_header_arpa_inet_h=yes}
| : ${ac_cv_header_arpa_nameser_h=yes}
| : ${ac_cv_header_ctype_h=yes}
| : ${ac_cv_header_dirent_h=yes}
| : ${ac_cv_header_dlfcn_h=yes}
| : ${ac_cv_header_elf_h=yes}
| : ${ac_cv_header_errno_h=yes}
| : ${ac_cv_header_fcntl_h=yes}
| : ${ac_cv_header_float_h=yes}
| : ${ac_cv_header_floatingpoint_h=yes}
| : ${ac_cv_header_getopt_h=yes}
| : ${ac_cv_header_glob_h=yes}
| : ${ac_cv_header_inttypes_h=yes}
| : ${ac_cv_header_langinfo_h=yes}
| : ${ac_cv_header_libgen_h=yes}
| : ${ac_cv_header_libutil_h=yes}
| : ${ac_cv_header_limits_h=yes}
| : ${ac_cv_header_login_cap_h=yes}
| : ${ac_cv_header_math_h=yes}
| : ${ac_cv_header_memory_h=yes}
| : ${ac_cv_header_minix_config_h=no}
| : ${ac_cv_header_net_if_h=yes}
| : ${ac_cv_header_net_if_media_h=yes}
| : ${ac_cv_header_net_if_tap_h=yes}
| : ${ac_cv_header_net_if_tun_h=yes}
| : ${ac_cv_header_netdb_h=yes}
| : ${ac_cv_header_netinet_in_h=yes}
| : ${ac_cv_header_paths_h=yes}
| : ${ac_cv_header_poll_h=yes}
| : ${ac_cv_header_pwd_h=yes}
| : ${ac_cv_header_readpassphrase_h=yes}
| : ${ac_cv_header_resolv_h=yes}
| : ${ac_cv_header_rpc_types_h=yes}
| : ${ac_cv_header_sched_h=yes}
| : ${ac_cv_header_search_h=yes}
| : ${ac_cv_header_security_pam_appl_h=yes}
| :
mail/roundcube selfsigned TLS problem after upgrade to php56 (SOLVED)
Hi, my roundcube was connecting happily to dovecot2 server over TLS for a few years, until recent upgrade of php ports (5.4 - 5.6) and roundcube (1.0.5 - 1.1.0). Luckily, all I needed to add to roundcube config was: $config['imap_conn_options'] = array( 'ssl' = array( 'verify_peer' = true, 'verify_depth' = 3, 'cafile' = '/etc/ssl/public/dovecot.pem', ), ); I found this information on archlinux forums: https://bbs.archlinux.org/viewtopic.php?id=193012 Hope this saves some time to someone, I had my webmail non-functional longer than I'd like to because of this change. Regards, -- Marko Cupać https://www.mimar.rs ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mail/roundcube selfsigned TLS problem after upgrade to php56 (SOLVED)
On 2/03/2015 8:15 PM, Marko Cupać wrote: On Mon, 2 Mar 2015 09:56:05 +0100 Marko Cupać marko.cu...@mimar.rs wrote: Hi, my roundcube was connecting happily to dovecot2 server over TLS for a few years, until recent upgrade of php ports (5.4 - 5.6) and roundcube (1.0.5 - 1.1.0). Luckily, all I needed to add to roundcube config was: $config['imap_conn_options'] = array( 'ssl' = array( 'verify_peer' = true, 'verify_depth' = 3, 'cafile' = '/etc/ssl/public/dovecot.pem', ), ); I found this information on archlinux forums: https://bbs.archlinux.org/viewtopic.php?id=193012 Hope this saves some time to someone, I had my webmail non-functional longer than I'd like to because of this change. Regards, Similar goes for managesieve plugin: $config['managesieve_conn_options'] = array( 'ssl' = array( 'verify_peer' = true, 'verify_depth' = 3, 'cafile' = '/etc/ssl/public/dovecot.pem', ), ); Probably also for all other plugins that have something to do with TLS. Perhaps there's something that can be improved in ports if someone would like to create an issue in Bugzilla, ideally with a patch. Perhaps a pkg-message? Perhaps a section, example, or note in the configuration .sample? -- koobs ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Philip Brown...United Way of Manatee County
On Mon, 2 Mar 2015, Guido Falsi wrote: To My Fellow Non-profit Leaders United Way Partners, My name is Philip Brown and our United Way team recently attended a [...] And what does this have to do with FreeBSD? Absolutely nothing. :) Looks like it's just some spam which got through to the list. In other words, the FreeBSD lists, by permitting non-subscribers to post to them, are spam-magnets. And the spammers know this. Tut tut... -- Dave Horsfall DTM (VK2KFU) Bliss is a MacBook with a FreeBSD server. http://www.horsfall.org/spam.html (and check the home page whilst you're there) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: devel/dbus no longer starts at system poweron
On 03/02/15 06:57, Beeblebrox wrote: Using dbus-1.8.12, /etc/rc.conf has (dbus_enable=YES, slim_enable=YES). This works no more. X.Org starts, but cannot login to any Desktop because dbus actually is not running and has not started. Kill Xorg, then manually service onestart dbus, and slim. I can then start to my desktop managers. what do dmesg and /var/log/messages say? Erich This problem was resolved some time back (through an update I believe) but is now back. No error message is registered in /var/log/messages or any other log. However, combing through the output on TTY0, I found this: Starting dbus Shared object 'libexpat.so.1' not found required by 'dbus-daemon' /etc/rc: WARNING: failed to start dbus After system is booted, form any TTY*, # service dbus onestart results in normal startup. Not setting any dbus_flags and not using gdm_enable. # pkg info -l expat expat-2.1.0_2: /usr/local/bin/xmlwf /usr/local/include/expat.h /usr/local/include/expat_external.h /usr/local/lib/libexpat.a /usr/local/lib/libexpat.so /usr/local/lib/libexpat.so.1 /usr/local/lib/libexpat.so.1.6.0 /usr/local/lib/libexpat.so.6 /usr/local/libdata/pkgconfig/expat.pc /usr/local/man/man1/xmlwf.1.gz (files separately confirmed with ls /usr/local/lib/*expat*) I've the same problem (libexpat and dbus-daemon) and posted to the freebsd-current list a few days ago. Rebuilt every dependency... etc. One other port also does not start *uuid* ... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: devel/dbus no longer starts at system poweron
Using dbus-1.8.12, /etc/rc.conf has (dbus_enable=YES, slim_enable=YES). This works no more. X.Org starts, but cannot login to any Desktop because dbus actually is not running and has not started. Kill Xorg, then manually service onestart dbus, and slim. I can then start to my desktop managers. what do dmesg and /var/log/messages say? Erich This problem was resolved some time back (through an update I believe) but is now back. No error message is registered in /var/log/messages or any other log. However, combing through the output on TTY0, I found this: Starting dbus Shared object 'libexpat.so.1' not found required by 'dbus-daemon' /etc/rc: WARNING: failed to start dbus After system is booted, form any TTY*, # service dbus onestart results in normal startup. Not setting any dbus_flags and not using gdm_enable. # pkg info -l expat expat-2.1.0_2: /usr/local/bin/xmlwf /usr/local/include/expat.h /usr/local/include/expat_external.h /usr/local/lib/libexpat.a /usr/local/lib/libexpat.so /usr/local/lib/libexpat.so.1 /usr/local/lib/libexpat.so.1.6.0 /usr/local/lib/libexpat.so.6 /usr/local/libdata/pkgconfig/expat.pc /usr/local/man/man1/xmlwf.1.gz (files separately confirmed with ls /usr/local/lib/*expat*) -- FreeBSD_amd64_11-Current_RadeonKMS Please include my email when responding (use Reply To All) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mail/roundcube selfsigned TLS problem after upgrade to php56 (SOLVED)
On Mon, 2 Mar 2015 09:56:05 +0100 Marko Cupać marko.cu...@mimar.rs wrote: Hi, my roundcube was connecting happily to dovecot2 server over TLS for a few years, until recent upgrade of php ports (5.4 - 5.6) and roundcube (1.0.5 - 1.1.0). Luckily, all I needed to add to roundcube config was: $config['imap_conn_options'] = array( 'ssl' = array( 'verify_peer' = true, 'verify_depth' = 3, 'cafile' = '/etc/ssl/public/dovecot.pem', ), ); I found this information on archlinux forums: https://bbs.archlinux.org/viewtopic.php?id=193012 Hope this saves some time to someone, I had my webmail non-functional longer than I'd like to because of this change. Regards, Similar goes for managesieve plugin: $config['managesieve_conn_options'] = array( 'ssl' = array( 'verify_peer' = true, 'verify_depth' = 3, 'cafile' = '/etc/ssl/public/dovecot.pem', ), ); Probably also for all other plugins that have something to do with TLS. -- Marko Cupać https://www.mimar.rs ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ games/lgeneral | 1.2.3 | 1.2.5 +-+ print/lilypond-devel| 2.19.11 | 2.19.16 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: mail/roundcube selfsigned TLS problem after upgrade to php56 (SOLVED)
On Mon, 2 Mar 2015 10:15:11 +0100 Marko Cupać marko.cu...@mimar.rs wrote: On Mon, 2 Mar 2015 09:56:05 +0100 Marko Cupać marko.cu...@mimar.rs wrote: Hi, my roundcube was connecting happily to dovecot2 server over TLS for a few years, until recent upgrade of php ports (5.4 - 5.6) and roundcube (1.0.5 - 1.1.0). Luckily, all I needed to add to roundcube config was: $config['imap_conn_options'] = array( 'ssl' = array( 'verify_peer' = true, 'verify_depth' = 3, 'cafile' = '/etc/ssl/public/dovecot.pem', ), ); I found this information on archlinux forums: https://bbs.archlinux.org/viewtopic.php?id=193012 Hope this saves some time to someone, I had my webmail non-functional longer than I'd like to because of this change. Regards, Similar goes for managesieve plugin: $config['managesieve_conn_options'] = array( 'ssl' = array( 'verify_peer' = true, 'verify_depth' = 3, 'cafile' = '/etc/ssl/public/dovecot.pem', ), ); Probably also for all other plugins that have something to do with TLS. I wrote blog post about this: https://www.mimar.rs/en/sysadmin/2015/php-5-6-x-ssltls-peer-certificates-and-hostnames-verified-by-default/ The ones who think he did it for clicks and ads have dirty mind. The blog is (and will remain) ad-free ;) -- Marko Cupać https://www.mimar.rs ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
net-mgmt/monitoring-pluginss: check_snmp always fails with: CRTICAL - Plugin timed out while executing system call
Having port net-mgmt/icinga2 in addition with net-mgmt/monitoring-plugins
running and monitoring installed on most recent CURRENT and 10.1-p6 systems, I
face a nasty bug/error/misconfiguration I cannot fathom and I need some
help/ideas.
The service I configured is taken from the handbook (Icinga2) and looks like
apply Service snmp {
import generic-service
check_command = snmp
/* sysUpTimeInstance(0), see also http://www.oid-info.com/get/ */
vars.snmp_oid = 1.3.6.1.2.1.1.3.0
assign where host.vars.snmp_community !=
}
and a specific host definition looks like
object Host B4132-SW01 {
import generic-host
address = 192.168.178.238
groups += [ switches ]
vars.snmp_community = public
vars.sla = 24x7
}
The problem is that almost every command out of the port
net-mgmt/monitoring-plugins works as expected - but check_snmp not! It always
fails with
CRITICAL - Plugin timed out while executing system call
I checked the plugin /usr/local/libexec/nagios/check_snmp manually and fed it
with parameters and it returns correct values.
So, since even the examples from the handbook don't work, I consider a bug.
Has anyone any ideas?
I have rebuilt icinga2, net-snmp (on 10.1.-p6, on CURRENT it is broken) and
monitoring plugins.
Please CC me.
Thanks in advance,
O. Hartmann
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Philip Brown...United Way of Manatee County
On 03/02/15 15:40, Scott Furry wrote: On 02/03/2015 07:00, Philip Brown wrote: To My Fellow Non-profit Leaders United Way Partners, My name is Philip Brown and our United Way team recently attended a [...] To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org And what does this have to do with FreeBSD? Absolutely nothing. :) Looks like it's just some spam which got through to the list. -- Guido Falsi m...@madpilot.net ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Предложение за вашият сайт и бизнес
Click on the link below to open the message in a browser: http://mandrillapp.com/track/click/30119679/shoutout.wix.com?p=eyJzIjoiVVZtWXpQXzY0cHJRMHZ1dFZvMThGWF9pdGJVIiwidiI6MSwicCI6IntcInVcIjozMDExOTY3OSxcInZcIjoxLFwidXJsXCI6XCJodHRwOlxcXC9cXFwvc2hvdXRvdXQud2l4LmNvbVxcXC9zb1xcXC8yS2xSY2hfdj9jaWQ9NmRjMzYyYWYtMDE0MC00ZmI5LWI5ZjQtMTdkNmRmNjlhMjYyXCIsXCJpZFwiOlwiNTg2YzE5NDdjNTc5NDM5ZDg2NTRhYWFhMWIwZjIxZWRcIixcInVybF9pZHNcIjpbXCI1MWNkZjgwNzNmMGEyZGVjMTNiNGJiMmVlOWYzOWIxYjdmZjBkMjJkXCJdfSJ9 You've received this email because you are a subscriber of http://mandrillapp.com/track/click/30119679/visitsltd.wix.com?p=eyJzIjoicDFISFhzSTVSLU5NcnVKYm5PU2tsZVhmOU53IiwidiI6MSwicCI6IntcInVcIjozMDExOTY3OSxcInZcIjoxLFwidXJsXCI6XCJodHRwOlxcXC9cXFwvdmlzaXRzbHRkLndpeC5jb21cXFwvcGFnZTY4XCIsXCJpZFwiOlwiNTg2YzE5NDdjNTc5NDM5ZDg2NTRhYWFhMWIwZjIxZWRcIixcInVybF9pZHNcIjpbXCI0ZjY3ZWQyOTg2OTdhY2UzZDQzYmE0NGRmZmQ1ZGE0MGExY2MxZGM5XCJdfSJ9. If you feel you received it by mistake or wish to unsubscribe, click http://www.wix.com/my-account/contacts/unsubscribe?siteName=page68metaSiteId=a0cc8375-c0ac-4253-8af5-1cd899dd3160unsubscribeToken=abcefd4d5885911e7f4ea863ecce180388e169a39e4c714f1a99cb3376c2b70631537871f41fe118cae8efec71c23c5d19e3cd905de8f76b4c090ed10d388503eaca9dd65b7196d2f0f425d87018ded8445fe65559299dd1ed48d4aea7087f26ad46fbe86ddf2e00dda25ab30c12acb4d46e12d4e9bca406dc8e7a36bd96f805ab8fd4afbcec4dd2b0e30913a63c96fd4045a78aca1ebb2e12dd3e813aa45e2cf4c75ecddb570f39f34160d3b57016baeca4e54f7dfacaf2948510b3df01399d205e8b4948b66044c4025d01c7f104d2a8abcc80d36c25035b638d74d6b184332454553abd408576885fd045b0d668b223b151e6b1b88b51bbb9df26b1d9e1f17ca01d7ca9dd31023935fcda392cb313488c1517387d06354abf4660a3708fe7157d2055d0ddd8df79319dd8f6e620b9273dce92baf6998d28a78ff1e91e17482620b1587e0aa257a623c65bd55c02a9b0190c250f422854fddaa18569e38fed8198edf4a1b89be40d2000aa0b6f09b3. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: reposado-0.0.20130415
Hi! Greg Neagle has released an update to reposado (https://github.com/wdas/reposado) involving a new option to remove config-data attributes from product dist files five days ago. When will we see this update in the FreeBSD ports tree? There's a PR now, if it's approved, I'll commit it: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197328 Committed (maintainer timeout). -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD Port: netqmail-tls-1.06.20110119
Hello, I thought I'd send you a quick email to let you know that this port seems to be full of security holes. While it seems to work in normal operations, I experienced numerous spam attacks caused by an apparent failure of AUTH(STARTTLS). Folks were authorizing using unknown accounts and passwords (backdoors?) and I faced a flood of spam as a result. I was able to log one account that was being used, and I was unable to block the attack even when I removed the account. These attacks continued even after I updated every email account to use a random 20 char password. The second issue I see here is that anyone that successfully authorizes can send email using any address they wish, which is why I was getting SPAM generated using fake email address as the originator. The port I am using is FreeBSD tahoestores.net 9.2-RELEASE-p10 FreeBSD 9.2-RELEASE-p10 #0: Tue Jul 8 10:48:24 UTC 2014 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 and is the version of qmail is netqmail-tls-1.06.20110119. I would be happy to send you more detailed configurations docs. For now, I have had to drop tls support. Thanks Joel Rodriguez Gossamer Computer Services ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
