Re: ftp.eu.openbsd.org no longer accepts anonymous ftp?

2017-08-21 Thread Stuart Henderson
On 2017-08-21, Janne Johansson  wrote:
> Fixed, now ftp works again, sorry for the glitch.

Use http for pkg_add anyway though, it's way faster than ftp.




amd(8): outdated FILES manpage's section?

2017-08-21 Thread Alessandro DE LAURENZIS

Dear misc@ readers,

Since this old commit [0] the default location for the real amd(8)'s 
mount points has been changed from "/a" to "/tmp_mnt".


This is correctly referenced in the man page, when the "-a" option is 
described, but the FILES section still lists "/a"; should it be updated 
as well? Something like:


--- /usr/src/usr.sbin/amd/amd/amd.8.origTue Jul 16 13:13:33 2013
+++ /usr/src/usr.sbin/amd/amd/amd.8 Mon Aug 21 18:32:51 2017
@@ -188,8 +188,8 @@
.Va ${domain} .
.El
.Sh FILES
-.Bl -tag -width /axx
-.It Pa /a
+.Bl -tag -width /tmp_mntxx
+.It Pa /tmp_mnt
directory under which filesystems are dynamically mounted
.El
.Sh SEE ALSO

Actually, neither the reference "Amd - The 4.4 BSD Automounter" reflects 
this change, but I think that's normal, because the "original" document 
should be preserved.


[0]: 
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.sbin/amd/amd/amd.c?rev=1.15&content-type=text/x-cvsweb-markup

--
Alessandro DE LAURENZIS
[mailto:jus...@atlantide.t28.net]
LinkedIn: http://it.linkedin.com/in/delaurenzis



Re: touchpad input driver: test results

2017-08-21 Thread Martin Pieuchot
Thanks for your work Ulf.

By the way I brought a new laptop, X1 Carbon gen2 for you from Toronto.

It's a gift from deraadt@.  It has a soft-button synaptics and a USB
touchscreen.

Cheers,
Martin


On 20/08/17(Sun) 22:17, Ulf Brosziewski wrote:
> As people might want to know what they have worked for, it's probably
> time for a summary of the first test results and my conclusions.
> (But please don't get that wrong: more tests and reports are and will be
> welcome.)
> 
> Hardware:  Most tests were made with (PS/2) Synaptics touchpads, and it
> seems there are no problems with common models of "OpenBSD laptops".
> Few quirks and bugs have been reported for older and less common ones,
> and concern things that should be handled by the hardware driver.  Alps
> and Elantech models are rare, and it looks like most Mac users are on
> holiday.
> 
> Driver mechanisms:  No serious problem has come up.  It has been
> observed that there are (too) long delays between the start of a scroll
> gesture and the first scroll event.  I'm already testing an improved
> version of the handler.  There will still be a short delay, because
> it reduces the risk that you produce scroll events unintentionally.
> 
> Features:  Not surprisingly, some people are missing certain features.
> What has been mentioned is 1) "disable-while-typing", 2) edge areas
> (where initial contacts don't move the pointer or generate tap events),
> 3) multi-finger clicks, and 4) "coasting" (that is, scrolling continues
> for some time after the scrolling fingers have been lifted).  Up to now
> my impression is that 1) and/or 2) could be prominent, maybe 3).
> However, there are no decisions about additional features yet, each one
> would need some care.
> 
> 1) and 2) are different approaches to the same task: suppressing outputs
> of accidental contacts, usually palm or thumb contacts, so in this
> context one might also think of: 5) palm and thumb detection based on
> contact width, pressure, and other attributes, perhaps.  1) is based on
> a simple principle, but it needs coordination with another driver, and I
> am not sure whether it is a good solution, or despair.  What's a
> reasonable timeout here?  If it's too short, it only mitigates the
> problem, if it's too long, it can be a nuisance.  5) might work well for
> some users, with some touchpads, but it may be difficult to find useful
> generalizations.  I'm currently checking variants of 2), the basic
> mechanism is already present in the driver (it's required for software
> buttons and edge scroll areas).  But again, it's too early for
> conclusions, and surely we want to avoid a patchwork of half-general and
> half-successful solutions.
> 
> Default configuration:  The defaults, including the "hidden" ones, seem
> to be acceptable for many models.  I will increase the default scroll
> speed (moderately).  In some cases, the height of the button area on
> clickpads is problematic.  This is not as trivial as it may seem.
> Coordinate limits are not always correct, and resolution values can be
> unreliable - if they are present at all.  There is actually a good deal
> of guess work in the configuration.  Improving that will need more work
> on the hardware drivers.
> 
> As I have written, not all touchpad drivers cooperate with the input
> driver up to now.  I hope this will change soon.  It's not ready yet,
> but some work on imt/hidmt has already been done, with help of Remi.
> 
> Thanks again for the friendly, competent, and helpful feedback!
> 
> 
> On 07/31/2017 11:02 PM, Ulf Brosziewski wrote:
> > In the long run the synaptics driver, which handles touchpad inputs in
> > X, may be a dead end of the input framework, and it's time to prepare
> > an alternative.  The kernel contains an internal touchpad input driver
> > now, it's a part of wsmouse(4).  It provides standard features -
> > two-finger/edge scrolling, software buttons for clickpads, tapping -
> > and various kinds of plankton required for usability.
> > 
> > If you have a new snapshot (from July 27 or later) on a laptop with a
> > Synaptics, Apple, Alps, or Elantech-4 touchpad, you could help with
> > tests [...]
> 



Re: [PATCH] Off-by-one bug in httpd, ldapd, relayd, smtpd, switchd and ypldap

2017-08-21 Thread Gilles Chehade
On Sat, Aug 19, 2017 at 04:20:31PM -0500, Kris Katterjohn wrote:
> On Fri, Aug 18, 2017 at 09:24:33AM -0700, Chris Cappuccio wrote:
> > This looks correct. Also, there's more:
> 
> Thanks for looking and catching what I missed.  It hit me a while after
> I sent my original email that relayd likely has the same bug.  D'oh.
> 
> Here is an updated patch for httpd, ldapd, relayd, smtpd, switchd and
> ypldap, which all seem to have the off-by-one bug for port number
> checking (where 65535 is unusable and called invalid, at least when
> specifying it as a number).  Again, I cannot build and actually test
> this right now.
> 
> Cheers,
> Kris Katterjohn
> 

ok gilles@

chris, are you taking care of committing this ?


> Index: usr.sbin/httpd/parse.y
> ===
> RCS file: /cvs/src/usr.sbin/httpd/parse.y,v
> retrieving revision 1.91
> diff -u -p -r1.91 parse.y
> --- usr.sbin/httpd/parse.y11 Aug 2017 18:48:56 -  1.91
> +++ usr.sbin/httpd/parse.y19 Aug 2017 20:15:31 -
> @@ -1118,7 +1118,7 @@ medianamesl : numberstring  
> {
>   ;
>  
>  port : PORT NUMBER {
> - if ($2 <= 0 || $2 >= (int)USHRT_MAX) {
> + if ($2 <= 0 || $2 > (int)USHRT_MAX) {
>   yyerror("invalid port: %lld", $2);
>   YYERROR;
>   }
> Index: usr.sbin/ldapd/parse.y
> ===
> RCS file: /cvs/src/usr.sbin/ldapd/parse.y,v
> retrieving revision 1.24
> diff -u -p -r1.24 parse.y
> --- usr.sbin/ldapd/parse.y6 Apr 2017 12:22:32 -   1.24
> +++ usr.sbin/ldapd/parse.y19 Aug 2017 20:15:31 -
> @@ -161,7 +161,7 @@ port  : PORT STRING   {
>   free($2);
>   }
>   | PORT NUMBER   {
> - if ($2 <= 0 || $2 >= (int)USHRT_MAX) {
> + if ($2 <= 0 || $2 > (int)USHRT_MAX) {
>   yyerror("invalid port: %lld", $2);
>   YYERROR;
>   }
> Index: usr.sbin/relayd/parse.y
> ===
> RCS file: /cvs/src/usr.sbin/relayd/parse.y,v
> retrieving revision 1.215
> diff -u -p -r1.215 parse.y
> --- usr.sbin/relayd/parse.y   27 May 2017 08:33:25 -  1.215
> +++ usr.sbin/relayd/parse.y   19 Aug 2017 20:15:32 -
> @@ -338,7 +338,7 @@ port  : PORT STRING {
>   free($2);
>   }
>   | PORT NUMBER {
> - if ($2 <= 0 || $2 >= (int)USHRT_MAX) {
> + if ($2 <= 0 || $2 > (int)USHRT_MAX) {
>   yyerror("invalid port: %d", $2);
>   YYERROR;
>   }
> Index: usr.sbin/smtpd/parse.y
> ===
> RCS file: /cvs/src/usr.sbin/smtpd/parse.y,v
> retrieving revision 1.197
> diff -u -p -r1.197 parse.y
> --- usr.sbin/smtpd/parse.y11 Jul 2017 06:08:40 -  1.197
> +++ usr.sbin/smtpd/parse.y19 Aug 2017 20:15:33 -
> @@ -480,7 +480,7 @@ opt_if_listen : INET4 {
>   }
>   listen_opts.options |= LO_PORT;
>  
> - if ($2 <= 0 || $2 >= (int)USHRT_MAX) {
> + if ($2 <= 0 || $2 > (int)USHRT_MAX) {
>   yyerror("invalid port: %" PRId64, $2);
>   YYERROR;
>   }
> Index: usr.sbin/switchd/parse.y
> ===
> RCS file: /cvs/src/usr.sbin/switchd/parse.y,v
> retrieving revision 1.5
> diff -u -p -r1.5 parse.y
> --- usr.sbin/switchd/parse.y  6 Aug 2017 17:31:19 -   1.5
> +++ usr.sbin/switchd/parse.y  19 Aug 2017 20:15:33 -
> @@ -144,7 +144,7 @@ listen: LISTEN ON STRING opttls port {
>   ;
>  
>  port : PORT NUMBER {
> - if ($2 <= 0 || $2 >= (int)USHRT_MAX) {
> + if ($2 <= 0 || $2 > (int)USHRT_MAX) {
>   yyerror("invalid port: %lld", $2);
>   YYERROR;
>   }
> Index: usr.sbin/ypldap/parse.y
> ===
> RCS file: /cvs/src/usr.sbin/ypldap/parse.y,v
> retrieving revision 1.22
> diff -u -p -r1.22 parse.y
> --- usr.sbin/ypldap/parse.y   30 May 2017 09:33:31 -  1.22
> +++ usr.sbin/ypldap/parse.y   19 Aug 2017 20:15:33 -
> @@ -171,7 +171,7 @@ port  : PORT STRING   
> {
>   free($2);
>   }
>   | PORT NUMBER   {
> - if ($2 <= 0 || $2 >= (int)USHRT_MAX) {
> +   

Re: ftp.eu.openbsd.org no longer accepts anonymous ftp?

2017-08-21 Thread Janne Johansson
Fixed, now ftp works again, sorry for the glitch.


2017-08-20 19:33 GMT+02:00 Janne Johansson :

> Will fix, have to handle strange 1:1 NAT after move to a new ftp.eu.
>
>
> 2017-08-19 12:16 GMT+02:00 Peter N. M. Hansteen :
>
>> On 08/19/17 11:44, Andreas Thulin wrote:
>> > Also, yesterday's
>> >
>> > # pkg_add -u
>> >
>> > failed for me, apparently for that same reason.
>>
>> Yes, that would happen. Then again, changing ftp:// to https:// in
>> /etc/installurl would make pkg_add -u work.
>>
>> - P
>> --
>> Peter N. M. Hansteen, member of the first RFC 1149 implementation team
>> http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
>> "Remember to set the evil bit on all malicious network traffic"
>> delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
>>
>>
>
>
> --
> May the most significant bit of your life be positive.
>



-- 
May the most significant bit of your life be positive.