On 2016-03-09, Christian Weisgerber wrote:
> I propose to delete audio/rplay.
sthen@ pointed out that x11/fvwm95 depends on this. That is optional,
the FvwmAudio module can be built without.
Still, I wonder, do we want to keep fvwm95? It's from 1996 (last
home page update in 2001). I have to
Our port is probably still vulnerable to CVE-2006-0709:
https://security-tracker.debian.org/tracker/CVE-2006-0709
https://rhn.redhat.com/errata/RHSA-2006-0217.html
There are two patches included in the Debian tickets and I can't tell
which was applied. They removed the port in 2009, so it's hard
Stuart Henderson wrote:
> On 2016/03/17 21:13, Michael McConville wrote:
> > I won't be so long-winded on this one, but basically:
> >
> > o it has patches removing gets(3)
> > o it hasn't been updated since 1997
> > o the source files are timestamped 1993-94
> > o it's obviously exposed to un
According to the timestamps, the code has been untouched since 1993. I
don't even really understand what does, but it's some kind of telecom
extension for X Windows. Sounds obselete and probably dangerous.
Any users?
On Thu, Mar 17, 2016 at 02:39:59PM -0700, Tor Perkins wrote:
>
> Hello,
>
> Palemoon is based on Firefox but offers the "Classic UI". It has no
> odious signing requirements for plugins. Most plugins work and there
> are no pending requirements to rewrite them to a new API. Here are
> some lin
Committed, thanks.
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
On 2016-03-17 18:20:12, Marc Espie wrote:
> On Thu, Mar 17, 2016 at 10:42:21AM -0600, Anthony J. Bentley wrote:
> > I understand that people sometimes, even frequently, need to work with
> > non-UTF encodings. But you can get that effect on OpenBSD with a UTF-8
> > locale and using iconv on incomi
It's only got fixing tweaks since it was imported in 1998, nothing
depends on it, and (this is a good red flag for deletion candidates) it
still has patches removing gets(3). The source files in the tarball are
timestamped 1993-94 and the opening paragraph of the README is:
> I found this in a zip
* On Sat Mar 19, 2016 at 12:09:06PM +1100 218 , Jaime Tarrant
(j...@cookiesystems.com) wrote:
> Date: Sat, 19 Mar 2016 12:09:06 +1100
> From: Jaime Tarrant
> To: ports@openbsd.org
> Subject: Re: pkg_add (_pfetch) - Permission denied for /root/.netrc
> User-Agent: Mutt/1.5.24 (2015-08-30)
>
> * On
Michael McConville writes:
> Could mail/exmh2 go too? The last release was in 2004, and its
> dependence on mail/metamail doesn't speak well of its security. It's a
> "Tcl/Tk interface to the MH mail system", which seems niche.
MH as a format is not that niche. But exmh might be.
--
Anthony J. B
> > I recall finding a better explanation (or coming up with one myself)
> > when I originally tried this a few months ago, but I've since forgotten.
> > Considering that PIE broke it when introduced, I wouldn't be surprised
> > if some of our linking features are related.
>
> It's testing that it
Jaime Tarrant wrote:
> I noticed that line 583 of file:
>
> /usr/libdata/perl5/OpenBSD/PackageRepository.pm
>
> references the user _pkgfetch, however there is no such user on my
> system (-current, updated a earlier today). Should this be the _pfetch
> user instead?
>
> I tested changing it to
* On Mon Feb 22, 2016 at 03:09:31PM -0700 33934 , Theo de Raadt
(dera...@cvs.openbsd.org) wrote:
> Date: Mon, 22 Feb 2016 15:09:31 -0700
> From: Theo de Raadt
> To: Marc Espie
> cc: Jiri B , ports@openbsd.org, z...@openbsd.org,
> st...@openbsd.org, Theo de Raadt
> Subject: Re: pkg_add (_pfetch
> Am 18.03.2016 um 18:26 schrieb Michael McConville :
>
> Our port is probably still vulnerable to CVE-2006-0709:
>
> https://security-tracker.debian.org/tracker/CVE-2006-0709
>
> https://rhn.redhat.com/errata/RHSA-2006-0217.html
>
> There are two patches included in the Debian tickets and I c
On 2016/03/18 11:16, Michael McConville wrote:
> According to the timestamps, the code has been untouched since 1993. I
> don't even really understand what does, but it's some kind of telecom
> extension for X Windows. Sounds obselete and probably dangerous.
>
> Any users?
>
It's terminal emulat
Bryan Linton writes:
> If someone were working with and depended upon using a terminal
> program that used ISO-2022-JP or EUC-JP and wasn't UTF-8 capable,
> then having a terminal that used those codesets natively would be
> a requirement.
luit(1) exists for exactly this reason.
--
Anthony J. Be
On Thu, Mar 17, 2016 at 10:42:21AM -0600, Anthony J. Bentley wrote:
> I understand that people sometimes, even frequently, need to work with
> non-UTF encodings. But you can get that effect on OpenBSD with a UTF-8
> locale and using iconv on incoming and outgoing data. I've been doing
> so for Japa
Joerg Jung writes:
> Hi,
Hi,
> please find attached a port for the tiny dstat utility, which is written
> for and requires x11/dwm.
>
> $ cat pkg/DESCR
> dstat is a lightweight utility to set the dwm status bar text. dstat displays
> the current network throughput, CPU usage, performance setti
This is a 21-year-old 362-line Perl script. Do people suspect that it's
still useful? I recall seeing other port scan detectors in the ports
tree, and I suspect they're better choices...
Le 2016-03-18 13:34, Jeremie Courreges-Anglas a écrit :
Solène Rapenne writes:
Hello,
Hi,
I installed x11/wmpinboard on -current and when starting it I get
a segfault.
Running it with ktrace give me those last lines (after a long config
file text which seems a config file)
26310 wmpinboa
On Thu, 17 Mar 2016 23:20:07 +
Stuart Henderson wrote:
> On 2016/03/17 19:05, Bryan C. Everly wrote:
> > Stuart,
> >
> > Thanks for getting back to me!
> >
> > I've attached a new tarball that contains the suggested fixes.
> > What do you think?
>
> OK with me. (Forgot to mention I'd pro
21 matches
Mail list logo