Re: Saw-shaped load on idle computer

[Clint Pachl]

li...@wrant.com wrote on 11/16/16 18:07:

Tue, 15 Nov 2016 14:34:28 -0700 Clint Pachl 

Does /var/log/* have any clues?

No.


Philippe Meunier wrote on 11/15/16 06:11:

Hello,

I'm just curious: what is it in the kernel that wakes up about every
minute to do some work even on a completely idle machine?  I'm asking
because xload shows some curious looking saw shaped load like this:
http://www.ccis.northeastern.edu/home/meunier/xload.jpg
That's on an idle Thinkpad T43 running OpenBSD 6.0-release.  At first
I thought it might be something like cupsd, but even after killing
daemons one by one and going to single user mode these regular peaks
still continue.  So I guess it's due to some kernel thread?  I tried
to use "top -S" but couldn't figure out the source.  Does anyone have
any idea of how to find it?

Thanks,

Philippe

Hi Philippe,

It is most likely the result of running X while idling measuring idling..
Well, it is most interesting what you would be trying to measure with it.



But Philippe is noticing this behavior even in single user mode, right? 
In single user, init and a shell should be all that is running in userland.


If in single user, I would suspect hardware interrupting the kernel. 
Make sure your monitoring tool isn't the culprit.

Re: Unable to disable UDP ports 623 and 4500

[Foo74]

Hi Everyone,
Just to follow up and close on this thread.

UDP Port 4500 was indeed part of the kernel. It can be controlled with 
sysctl.conf settings and in particular the net.inet.esp.udpencap. When I set 
this to =NO the port is no longer active. (it is important which is why part of 
kernel and on by default but I just wanted to understand to control it)

Here are these esp settings (from man sysctl):
net.inet.esp.enable
net.inet.esp.udpencap
net.inet.esp.udpencap_port

UDP Port 623 had nothing to do with OpenBSD and was part of the hardware. It is 
part of Intelligent Platform Management Interface (IPMI) and it cannot always 
be disabled. If it is possible to disable it the option is through the BIOS.

Here is some info on it:
http://www.itworld.com/article/2708437/security/ipmi--the-most-dangerous-protocol-you-ve-never-heard-of.html
http://wiki.networksecuritytoolkit.org/index.php/Tunnelling_UDP_Traffic_Through_An_SSH_Connection
https://www.us-cert.gov/ncas/alerts/TA13-207A









 Original Message 
Subject: Unable to disable UDP ports 623 and 4500
Local Time: November 15, 2016 9:44 PM
UTC Time: November 16, 2016 5:44 AM
From: fo...@protonmail.ch
To: misc@openbsd.org 

Hi All,

I am exploring locking down an OpenBSD 6.0 server running on a Thinkpad w510 
with a i7-q720 processor.

I believe I have turned off everything except dhcp and sshd. When I run a 
netstat I don't see any services running. I have set everything =NO in the 
rc.conf.local (except dhcp and ssh).

However, when I port scan the machine I still see UDP ports 623 and 4500 open. 
I found this article that recommended disabling using mobike=NO in ipsec.conf 
but I cannot find anything in man page and tried it anyway and no change.

Any thoughts or ideas?

Below are the port scan and the netstat from the server:


Starting Nmap 7.01 ( https://nmap.org ) at 2016-11-15 21:28 PST
Nmap scan report for 192.168.0.127
Host is up (0.0042s latency).
Not shown: 998 closed ports
PORT STATE SERVICE
623/udp open|filtered asf-rmcp
4500/udp open|filtered nat-t-ike
MAC Address: F0:DE:F1:48:D2:10 (Wistron InfoComm (Kunshan)Co)

Nmap done: 1 IP address (1 host up) scanned in 173.95 seconds



# netstat -a
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address (state)
ip 0 0 *.* *.* 17
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp 0 0 192.168.0.127.ssh 192.168.0.112.33356 ESTABLISHED
tcp 0 0 *.ssh *.* LISTEN
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp6 0 0 *.ssh *.* LISTEN
Active UNIX domain sockets
Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr
0x803a2b00 stream 0 0 0x0 0x803a2b80 0x0 0x0
0x805d4800 stream 0 0 0x0 0x805d4200 0x0 0x0
0x805d4200 stream 0 0 0x0 0x805d4800 0x0 0x0
0x803a2b80 stream 0 0 0x0 0x803a2b00 0x0 0x0
#

Re: softraid(4) full-disk encryption on SSD

[lists]

> I'm taking the plunge now.

You're done with the swings.

Re: help

[Delan Azabani]

On 17 November 2016 at 11:25, steve kolars  wrote:
> The 4 lines in between the comments are straight out of several documents,
> but when I run "pfctl -nf f-n" these lines are flaged as syntax errors. Any
> assistance would be appreciated.

“proto tcp” needs to go after the “on [interface]” parameter.

pf.conf(5) could be clearer about the difference between “parameters”
(which are optional, but must be written in a particular order), and
“additional parameters” (which just need to come after the parameters
that aren’t additional). BNF is precise, but not always the nicest.

Re: OpenSMTPD Block Email Attachments

[lists]

> I have searched online for this and found no OpenSMTPD-related literature.

This is going to change.

Re: softraid(4) full-disk encryption on SSD

[Nick Holland]

On 11/16/16 11:52, Ax0n wrote:
> I'm taking the plunge now. Mostly, I was concerned about SSD longevity and
> if TRIM would be a problem due to the different way data is going to be
> accessed. It was the cheapest drive I could find locally anyway, and I keep
> good backups (dump to a much larger external drive that's also using
> softraid crypto) so I suppose if it burns up in a year it's not really that
> big of a problem.

Make good backups, and if it burns up in a year (which it may or may not
do regardless of what SSD-specific bullsh*t you do with it), say
"thanks!" and go buy yourself one twice as big, twice as fast and half
as expensive (and possibly more reliable).

If it doesn't fail in a year or two, I suggest removing the SSD and a
wool carpet and rubber shoes, or better yet, just look panicked, tell
your significant other it failed and hope they don't look to closely,
and rush out to buy the upgrade.  The panicked look is important, though.

Nick.

OpenSMTPD Block Email Attachments

[Tito Mari Francis Escaño]

Good day,
I was looking into how to block any email with attachment for later
verification and download by the recipient, would like to ask how
anybody has done that with OpenSMTPD and related support packages. I
have searched online for this and found no OpenSMTPD-related
literature. Hope somebody in the list could share their pointers,
challenges and configuration to learn on-the-field deployment
practices.
Thanks so much.

Re: Microsoft announced it is joining The Linux Foundation

[Tinker]

Leave this list please? Your entitlement to spam with stuff that's 
uninteresting and altogether irrelevant to OpenBSD is zero.


On 2016-11-17 07:28, SOUL_OF_ROOT 55 wrote:

Re: Saw-shaped load on idle computer

[lists]

Tue, 15 Nov 2016 14:34:28 -0700 Clint Pachl 
> Does /var/log/* have any clues?

No.

> Philippe Meunier wrote on 11/15/16 06:11:
> > Hello,
> >
> > I'm just curious: what is it in the kernel that wakes up about every
> > minute to do some work even on a completely idle machine?  I'm asking
> > because xload shows some curious looking saw shaped load like this:
> > http://www.ccis.northeastern.edu/home/meunier/xload.jpg
> > That's on an idle Thinkpad T43 running OpenBSD 6.0-release.  At first
> > I thought it might be something like cupsd, but even after killing
> > daemons one by one and going to single user mode these regular peaks
> > still continue.  So I guess it's due to some kernel thread?  I tried
> > to use "top -S" but couldn't figure out the source.  Does anyone have
> > any idea of how to find it?
> >
> > Thanks,
> >
> > Philippe  
> 

Hi Philippe,

It is most likely the result of running X while idling measuring idling..
Well, it is most interesting what you would be trying to measure with it.

Kind regards,
Anton

Re: Running OpenSMTPD at home behind a cloud proxy

[lists]

Wed, 16 Nov 2016 12:29:19 + (UTC) Stuart Henderson 
[...]
> Then the easiest way to get mail to/from your home server is probably to
> set up a VPN, giving you a simple fixed (non-internet-routable) IP address,
> configure the MTA on the VPS (smtpd or whatever else) to allow relay
> from that address, and configure it to send all incoming mail for your
> domain on to that address.
> 

Hi Stuart,

Many? people are jailed behind sick ISPs, and would need to run their own
servers at their own premises while using a good reputation remote system
just for the data centre IP.  What are their options to relay mail there?

Kind regards,
Anton

Re: softraid(4) full-disk encryption on SSD

[lists]

Wed, 16 Nov 2016 19:10:08 +0100 ludovic coues 
> Trim and ssd longevity and what not may have been an issue when ssd where a
> novelty.
> These day, it should last just as long as an hard drive. So make backups if
> what matters and don't worry about your disk.

Hi Ludovic,

You have to face it, the issue is both is the SSD medium and controller.

I give it a decade of backed up cached usage, in lieu of actual storage.

It is an industry shame point solid state tech is beaten by mechanicals.

Kind regards,
Anton

Re: Microsoft announced it is joining The Linux Foundation

[Riccardo Mottola]

Hi,

SOUL_OF_ROOT 55 wrote:

Can this be?  Microsoft announced it is joining The Linux Foundation



this is "misc" but still OpenBSD misc.

Riccardo

Re: Removal of old libraries

[lists]

Tue, 15 Nov 2016 00:29:56 -0700 Clint Pachl 
[...]
> This sounds like someone who is not confident in their backup/restore 
> procedure, if one even exists. I think you need to worry more about that 
> than me saving a few megabytes with my upgrade process.

Hi Clint,

You need not worry at all.  That is other people's data on their own sites.

> Like I mentioned a couple times in the thread, I have "level 0" dumps; 
> that's consistency. I would not classify that as "nothing." There is a 
> reason why restore(8) and ftp(1) are included on bsd.rd.

Whatever..  Nobody cares much about what you have.  We system operators care
about the choices, and options the operating system, and tool kits provide..

> Oh yeah, and before you know it your crufty libc.so.84.2 is 2 years old 
> and full of security vulnerabilities. Thank god your users can still use 
> it and you don't have to bother them with a recompile.

That is a system policy depending from site to site, you need not police it.

> I thought the philosophy of the project is to move forward for the sake 
> of proactive security and correctness, not to rely on buggy legacy code 
> because it's convenient and lazy.

You think too much.  There is no such thing as philosophy of the project and
this kind of over-hyped black and white thinking is... obsolete and useless.
There are many upgrade and maintain choices, don't try to sell bibles here..

Kind regards,
Anton

Re: Microsoft announced it is joining The Linux Foundation

[SOUL_OF_ROOT 55]

Microsoft joins The Linux Foundation as a Platinum member


reference:
http://venturebeat.com/2016/11/16/microsoft-joins-the-linux-foundation-as-a-p
latinum-member/

2016-11-16 20:21 GMT-03:00 SOUL_OF_ROOT 55 :

> At its Connect(); 2016 developer event in New York City today, Microsoft
> announced it is joining The Linux Foundation. And the company isn’t
joining
> just to say it did: Microsoft is joining at the Platinum level, the highest
> level of membership, which costs $500,000 annually. John Gossman, architect
> on the Microsoft Azure team, will sit on the foundation’s Board of
> Directors and help underwrite projects.
>
> Can this be?  Microsoft announced it is joining The Linux Foundation

Re: Microsoft announced it is joining The Linux Foundation

[Frederick W. Soucy]

On Wed, 16 Nov 2016 at 20:21:01 -0300, SOUL_OF_ROOT 55 wrote:
>At its Connect(); 2016 developer event in New York City today, Microsoft
>announced it is joining The Linux Foundation. And the company isn???t joining
>just to say it did: Microsoft is joining at the Platinum level, the highest
>level of membership, which costs $500,000 annually. John Gossman, architect
>on the Microsoft Azure team, will sit on the foundation???s Board of
>Directors and help underwrite projects.
>
>Can this be?  Microsoft announced it is joining The Linux Foundation
>

pretty sure this is misc @openbsd.org not @lkml.org
it would be nice if you would stop flooding this list with mail that at
best has very little to do with OpenBSD.

Microsoft announced it is joining The Linux Foundation

[SOUL_OF_ROOT 55]

At its Connect(); 2016 developer event in New York City today, Microsoft
announced it is joining The Linux Foundation. And the company isn’t joining
just to say it did: Microsoft is joining at the Platinum level, the highest
level of membership, which costs $500,000 annually. John Gossman, architect
on the Microsoft Azure team, will sit on the foundation’s Board of
Directors and help underwrite projects.

Can this be?  Microsoft announced it is joining The Linux Foundation

mmap() MAP_FIXED and RLIMIT_DATA

[Mickael Torres]

Hello,

The mmap man page says:
"If the MAP_FIXED flag is specified, the allocation will happen
at the specified address, replacing any previously established mappings
in its range."

However, a simple:

#include 
#include 
#include 

int main(void)
{
  void *ptr0;
  void *ptr1;

  ptr0 = mmap(0, 510 * 1024 * 1024,
  PROT_READ|PROT_WRITE, MAP_ANONYMOUS | MAP_PRIVATE, -1, 0);
  if (ptr0 == MAP_FAILED)
err(1, "first mmap():");
  ptr1 = mmap(ptr0, 510 * 1024 * 1024,
  PROT_READ|PROT_WRITE, MAP_FIXED | MAP_ANONYMOUS | 
MAP_PRIVATE, -1, 0);

  if (ptr1 == MAP_FAILED)
err(1, "second mmap():");
}

fails on the second mmap with ENOMEM (with a data limit of 512M).
It is my understanding from the man page that it should not happen, as 
it

is supposed to replace the old mapping, thus not taking more memory.

Is my understanding correct, or did I miss something ?

In uvm_mmap.c:

if ((flags & MAP_ANON) != 0 || (flags & __MAP_NOFAULT) != 0 ||
((flags & MAP_PRIVATE) != 0 && (prot & PROT_WRITE) 
!= 0)) {

if (p->p_rlimit[RLIMIT_DATA].rlim_cur < size ||
p->p_rlimit[RLIMIT_DATA].rlim_cur - size <
ptoa(p->p_vmspace->vm_dused)) {
return ENOMEM;
}
}
maxprot = PROT_MASK;
error = uvm_mmapanon(>p_vmspace->vm_map, , size, 
prot, maxprot,

flags, p->p_rlimit[RLIMIT_MEMLOCK].rlim_cur, p);

The size check is done without looking at a possible
replacement. What would be the best way to add this lookup without
duplicating code (maybe uvm_map_isavail()) too much ?

Mickael

Re: OpenBSD Ports "Libraries in packing-lists in the ports tree and libraries from installed packages don't match"

[Stuart Longland]

On 16/11/16 20:52, Marcus MERIGHI wrote:
> I have the gut feeling your are moving some Linux-isms to OpenBSD land.
> You are doing by far too much by yourself ;-)

That is quite probable, I've dabbled with OpenBSD (and other BSDs)
before, but that was some years ago.

> I need to add I've never used the loongson port.

That's understandable, they're a somewhat rare beast.  I'll have a look
at your notes later this week when I've got some time.
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.

Re: OpenBSD Ports "Libraries in packing-lists in the ports tree and libraries from installed packages don't match"

[Stuart Longland]

On 16/11/16 22:13, Stuart Henderson wrote:
> So in your case, you're running 6.0-release, so you need to be using
> packages from http://$MIRROR/pub/OpenBSD/6.0/packages/mips64el/

Ahh bingo, I did go looking for those and didn't find them, hence I
thought I'd be installing everything from ports.

*That* looks like a much better target.  Thanks. :-)
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.

Re: Because in this day and age, there’s no one else doing what OpenBSD is doing?

[Stuart Longland]

On 16/11/16 19:39, Boudewijn Dijkstra wrote:
> Op Tue, 15 Nov 2016 22:14:23 +0100 schreef SOUL_OF_ROOT 55
> :
>> Theo de Raadt wrote:
>>
>> *Because in this day and age, there's no one else doing what OpenBSD is
>> doing?*
> 
> The interview was published July 2005. Do you think that "this day and
> age" still applies?

The way the Linux distributions seem to be running into the systemd
abyss?  Perhaps yes. ;-)
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.

Re: softraid(4) full-disk encryption on SSD

[ludovic coues]

Trim and ssd longevity and what not may have been an issue when ssd where a
novelty.
These day, it should last just as long as an hard drive. So make backups if
what matters and don't worry about your disk.

On 16 Nov 2016 5:54 p.m., "Ax0n"  wrote:

> I'm taking the plunge now. Mostly, I was concerned about SSD longevity and
> if TRIM would be a problem due to the different way data is going to be
> accessed. It was the cheapest drive I could find locally anyway, and I keep
> good backups (dump to a much larger external drive that's also using
> softraid crypto) so I suppose if it burns up in a year it's not really that
> big of a problem.
>
> On Wed, Nov 16, 2016 at 10:33 AM, Marc Peters  wrote:
>
> > Am 11/16/16 um 17:07 schrieb Ax0n:
> > > I'm less concerned about swap, and more concerned about how a fully
> > > encrypted softraid Solid State Disk is going to act. I can't find a lot
> > > about FDE on SSD.
> > >
> >
> > It acts as a normal harddisk would, just faster :). I had one in my
> > worklaptop i used before for about two years and i have one in my
> > worklaptop. No problems.

Re: softraid(4) full-disk encryption on SSD

[Ax0n]

I'm taking the plunge now. Mostly, I was concerned about SSD longevity and
if TRIM would be a problem due to the different way data is going to be
accessed. It was the cheapest drive I could find locally anyway, and I keep
good backups (dump to a much larger external drive that's also using
softraid crypto) so I suppose if it burns up in a year it's not really that
big of a problem.

On Wed, Nov 16, 2016 at 10:33 AM, Marc Peters  wrote:

> Am 11/16/16 um 17:07 schrieb Ax0n:
> > I'm less concerned about swap, and more concerned about how a fully
> > encrypted softraid Solid State Disk is going to act. I can't find a lot
> > about FDE on SSD.
> >
>
> It acts as a normal harddisk would, just faster :). I had one in my
> worklaptop i used before for about two years and i have one in my
> worklaptop. No problems.

Re: softraid(4) full-disk encryption on SSD

[Marc Peters]

Am 11/16/16 um 17:07 schrieb Ax0n:
> I'm less concerned about swap, and more concerned about how a fully
> encrypted softraid Solid State Disk is going to act. I can't find a lot
> about FDE on SSD.
> 

It acts as a normal harddisk would, just faster :). I had one in my
worklaptop i used before for about two years and i have one in my
worklaptop. No problems.

Re: softraid(4) full-disk encryption on SSD

[Ax0n]

I'm less concerned about swap, and more concerned about how a fully
encrypted softraid Solid State Disk is going to act. I can't find a lot
about FDE on SSD.

On Wed, Nov 16, 2016 at 9:41 AM, trondd  wrote:

> On Wed, November 16, 2016 10:23 am, Jiri B wrote:
> > On Wed, Nov 16, 2016 at 09:14:51AM -0600, Ax0n wrote:
> >> I just purchased a SanDisk SSD for my daily-driver laptop which has been
> >> running -CURRENT well. I'm considering going with FDE and a fresh
> >> snapshot
> >> install, adding my packages then copying over what I need from my old
> >> spinning rust drive, mostly /home and the ssh host keys from /etc/ssh.
> >>
> >> Anything I should look out for? To be honest, this is my first
> >> experience
> >> installing anything onto an SSD so I'd be welcome to accept any pointers
> >> specific to OpenBSD. Searching misc@ for as long as I've been
> subscribed
> >> hasn't yielded any solid input on this.
> >
> > Not sure if encrypting swap makes still sense if you already have FDE.
> > What's recommended in this context?
> >
> > j.
> >
>
> It's been discussed previously.  Relavant comment from the thread:
>
> http://marc.info/?l=openbsd-misc=143206067713324=2
>
> And hint, you can search an online archive instead of being limited to
> searching "for as long as you've been subscribed" :)

Re: softraid(4) full-disk encryption on SSD

[Stefan Sperling]

On Wed, Nov 16, 2016 at 10:23:39AM -0500, Jiri B wrote:
> On Wed, Nov 16, 2016 at 09:14:51AM -0600, Ax0n wrote:
> > I just purchased a SanDisk SSD for my daily-driver laptop which has been
> > running -CURRENT well. I'm considering going with FDE and a fresh snapshot
> > install, adding my packages then copying over what I need from my old
> > spinning rust drive, mostly /home and the ssh host keys from /etc/ssh.
> > 
> > Anything I should look out for? To be honest, this is my first experience
> > installing anything onto an SSD so I'd be welcome to accept any pointers
> > specific to OpenBSD. Searching misc@ for as long as I've been subscribed
> > hasn't yielded any solid input on this.
> 
> Not sure if encrypting swap makes still sense if you already have FDE.
> What's recommended in this context?
> 
> j.
> 

I always leave swap crypt enabled anyway. Less hassle, and one more layer
for an attacker to poke through for finding leftover bits of data from RAM.

Re: softraid(4) full-disk encryption on SSD

[trondd]

On Wed, November 16, 2016 10:23 am, Jiri B wrote:
> On Wed, Nov 16, 2016 at 09:14:51AM -0600, Ax0n wrote:
>> I just purchased a SanDisk SSD for my daily-driver laptop which has been
>> running -CURRENT well. I'm considering going with FDE and a fresh
>> snapshot
>> install, adding my packages then copying over what I need from my old
>> spinning rust drive, mostly /home and the ssh host keys from /etc/ssh.
>>
>> Anything I should look out for? To be honest, this is my first
>> experience
>> installing anything onto an SSD so I'd be welcome to accept any pointers
>> specific to OpenBSD. Searching misc@ for as long as I've been subscribed
>> hasn't yielded any solid input on this.
>
> Not sure if encrypting swap makes still sense if you already have FDE.
> What's recommended in this context?
>
> j.
>

It's been discussed previously.  Relavant comment from the thread:

http://marc.info/?l=openbsd-misc=143206067713324=2

And hint, you can search an online archive instead of being limited to
searching "for as long as you've been subscribed" :)

Re: softraid(4) full-disk encryption on SSD

[Jiri B]

On Wed, Nov 16, 2016 at 09:14:51AM -0600, Ax0n wrote:
> I just purchased a SanDisk SSD for my daily-driver laptop which has been
> running -CURRENT well. I'm considering going with FDE and a fresh snapshot
> install, adding my packages then copying over what I need from my old
> spinning rust drive, mostly /home and the ssh host keys from /etc/ssh.
> 
> Anything I should look out for? To be honest, this is my first experience
> installing anything onto an SSD so I'd be welcome to accept any pointers
> specific to OpenBSD. Searching misc@ for as long as I've been subscribed
> hasn't yielded any solid input on this.

Not sure if encrypting swap makes still sense if you already have FDE.
What's recommended in this context?

j.

softraid(4) full-disk encryption on SSD

[Ax0n]

I just purchased a SanDisk SSD for my daily-driver laptop which has been
running -CURRENT well. I'm considering going with FDE and a fresh snapshot
install, adding my packages then copying over what I need from my old
spinning rust drive, mostly /home and the ssh host keys from /etc/ssh.

Anything I should look out for? To be honest, this is my first experience
installing anything onto an SSD so I'd be welcome to accept any pointers
specific to OpenBSD. Searching misc@ for as long as I've been subscribed
hasn't yielded any solid input on this.

TIA!
--ax0n

Re: Mount HDD USB on 6.0 Stable: Fail

[Stephane HUC "CIOTBSD"]

Hi...

David: thanks for this info.

It seems i found why the "bug"?

If the table of partition is "(ms)dos", the detection of USB HDD (or
pendrive) is correct, and mount!

If the table of partition is "GPT", the detection hang!

Alexey Vatchenko is warned about this problem, by personnal discussion
by emails. He will confirm ;)


On 11/16/16 13:55, David Coppa wrote:
> On Wed, 16 Nov 2016, Stephane HUC "CIOTBSD" wrote:
>
>> Question: How i can "write" fstype "NTFS" on the "defective" HDD?
>> It's really formated in NTFS - mode normal, on Win7!
>
> Try with "fdisk -e" under OpenBSD.
>
> Use "07" for the partition id and, for the other parameters (offset,
> size), just press enter to leave them unchanged.
>
> Example:
>
> # fdisk -e sd2
> Enter 'help' for information
> fdisk: 1> p
> Disk: sd2   geometry: 498/255/63 [8011774 Sectors]
> Offset: 0   Signature: 0xAA55
> Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [   start:size ]
> ---
> *0: 04  0  32  33 -498 181   1 [2048: 8009726 ] MSDOS  
>  1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>   
>  2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>   
>  3: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>   
> fdisk: 1> edit 0
> Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [   start:size ]
> ---
> *0: 04  0  32  33 -498 181   1 [2048: 8009726 ] MSDOS  
> Partition id ('0' to disable) [01 - FF]: [4] (? for help) 07
> Do you wish to edit in CHS mode? [n] 
> Partition offset [0 - 8011774]: [2048] 
> Partition size [1 - 8009726]: [8009726] 
> fdisk:*1> w
> Writing MBR at offset 0.
> fdisk: 1> q
> # fdisk sd2
> Disk: sd2  geometry: 498/255/63 [8011774 Sectors]
> Offset: 0   Signature: 0xAA55
> Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [   start:size ]
> ---
> *0: 07  0  32  33 -498 181   1 [2048: 8009726 ] NTFS  
>   
>  1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>   
>  2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>   
>  3: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>   
> # ^D
>
>
> Ciao!
> David
>

-- 
~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<<

Stephane HUC as PengouinPdt or CIOTBSD
b...@stephane-huc.net

Re: Mount HDD USB on 6.0 Stable: Fail

[David Coppa]

On Wed, 16 Nov 2016, Stephane HUC "CIOTBSD" wrote:

> Question: How i can "write" fstype "NTFS" on the "defective" HDD?
> It's really formated in NTFS - mode normal, on Win7!


Try with "fdisk -e" under OpenBSD.

Use "07" for the partition id and, for the other parameters (offset,
size), just press enter to leave them unchanged.

Example:

# fdisk -e sd2
Enter 'help' for information
fdisk: 1> p
Disk: sd2   geometry: 498/255/63 [8011774 Sectors]
Offset: 0   Signature: 0xAA55
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
---
*0: 04  0  32  33 -498 181   1 [2048: 8009726 ] MSDOS  
 1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused  
 2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused  
 3: 00  0   0   0 -  0   0   0 [   0:   0 ] unused  
fdisk: 1> edit 0
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
---
*0: 04  0  32  33 -498 181   1 [2048: 8009726 ] MSDOS  
Partition id ('0' to disable) [01 - FF]: [4] (? for help) 07
Do you wish to edit in CHS mode? [n] 
Partition offset [0 - 8011774]: [2048] 
Partition size [1 - 8009726]: [8009726] 
fdisk:*1> w
Writing MBR at offset 0.
fdisk: 1> q
# fdisk sd2
Disk: sd2  geometry: 498/255/63 [8011774 Sectors]
Offset: 0   Signature: 0xAA55
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
---
*0: 07  0  32  33 -498 181   1 [2048: 8009726 ] NTFS
 1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused  
 2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused  
 3: 00  0   0   0 -  0   0   0 [   0:   0 ] unused  
# ^D


Ciao!
David

Re: Running OpenSMTPD at home behind a cloud proxy

[Stuart Henderson]

On 2016-11-13, Joris Vanhecke  wrote:
> Hey all,
>
> I'd like to pull my emails out of the cloud and run them on a local
> server (pcengines APU2 looks good).
> My ISP blocks tcp ports below 1024 and sending email from a residential
> (dynamic) IP might mark my email as spam.
>
> Right now I'm thinking of renting a cheap VPS and using it as a proxy
> for my home server which would use a dynamic DNS.
> I don't really want a copy of the email on the VPS so I was planning to
> use relayd or socat to route incoming traffic to my local OpenSMTPD
> server.
>
> But I don't really see a way to proxy outgoing connections from smtpd...
>
> Any ideas?
>
> Thanks,
> Joris
>
>

You'll lose the source IP address by doing this using socat/relayd/etc,
potentially opening yourself up to running an open relay, and at best
making it harder to detect spam.

If you don't really trust the VPS (or the network it's on) at all then
you are lost, because somebody could just intercept the traffic on the way
in (possibly even MITMing TLS connections because certificate are rarely
checked for email).

If you're not overly concerned about that (which is a problem for
relayd/etc as well as a standard SMTP relay), but you don't really want
mail written in the clear to disk, you could use smtpd with queue encryption
and start it manually so you can enter the key each time, or you could
use bioctl to create an encrypted partition which would work with any MTA
which you mount manually after a reboot.

Then the easiest way to get mail to/from your home server is probably to
set up a VPN, giving you a simple fixed (non-internet-routable) IP address,
configure the MTA on the VPS (smtpd or whatever else) to allow relay
from that address, and configure it to send all incoming mail for your
domain on to that address.

Re: OpenBSD Ports "Libraries in packing-lists in the ports tree and libraries from installed packages don't match"

[Stuart Henderson]

On 2016-11-16, Stuart Longland  wrote:
>
> Ahh okay, I omitted this as I saw this as a userland issue not a kernel
> one, and dmesg can be rather long.

It's useful for any issues as it shows exactly what you're running.

> The dmesg in full:
>> [ using 587952 bytes of bsd ELF symbol table ]
>> Copyright (c) 1982, 1986, 1989, 1991, 1993
>>  The Regents of the University of California.  All rights reserved.
>> Copyright (c) 1995-2016 OpenBSD. All rights reserved.  http://www.OpenBSD.org
>> 
>> OpenBSD 6.0 (GENERIC) #627: Thu Jul 28 21:15:50 MDT 2016
>> dera...@loongson.openbsd.org:/usr/src/sys/arch/loongson/compile/GENERIC

So in your case, you're running 6.0-release, so you need to be using
packages from http://$MIRROR/pub/OpenBSD/6.0/packages/mips64el/

>> While you are on, say, a snapshot as of 2016-10-01 the project keeps
>> moving. Depending on the point in the release process it takes hours to
>> days until _your_ snapshot isn't the current snapshot anymore. 
>> 
>> packages(7) keep being built against the current snapshot, not _your_
>> snapshot. Library mismatches between *your* snapshot base system and the
>> *projects* current ports happen soon.
>
> Ahh, so the ports tree is rolling-release and not tied to a particular
> release of OpenBSD.  This makes sense.

The ports tree checked out without a CVS tag is for -current, for 6.0
you need to checkout with -r OPENBSD_6_0 (which gives you 6.0-stable).

>> But 404s? Have you checked whether the 404-files are on the servers with
>> a different version number possibly?
>
> I'll have to go over more thoroughly which packages were causing the
> download errors, when I saw them my first instinct was: "the ports are
> out of date, try updating those first in case they've fixed the download
> links".
>
> Upstream projects sometimes do move things around, and often without
> telling people, so didn't see this as being an issue.

Packages don't fetch anything from upstream, they are entirely fetched
from OpenBSD servers/mirrors. If you are seeing problems installing from
packages, please post a transcript of commands+errors (plus show which
path you're fetching from, either in /etc/pkg.conf or $PKG_PATH).

Ports do fetch from upstream and can be subject to them moving things
around, though there is a fallback to an OpenBSD mirror for almost
everything.

> Right, so openbsd-wip is the "unstable" tree?

It's a tree used by some people while they're working on new ports,
I don't think it has anything to do with what you're doing.

> I grabbed ports from
> https://github.com/openbsd/ports/ which I understood to just be ports
> CVS mirrored on git.  Three reasons I went the git repo:
>
> 1. I know git well
> 2. Using github means I'm not putting so much demand on the OpenBSD
> project CVS servers
> 3. If I find I need to make changes, I can branch it, and optionally,
> export those changes out as patches to be submitted back (e.g. new
> ports, fixes, etc) without needing to be on-line at the time.

Please don't use this. No conversion tools have yet been fully
successful at converting the OpenBSD tree on an ongoing basis. It's
regenerated from scratch periodically so is not considered stable,
and sometimes you can end up with the checkout not matching the files
you would get from cvs.

But you shouldn't need to build anything yourself anyway unless you're
working on ports yourself (there are a very few cases where licenses don't
permit redistribution but I don't think this applies to many things you'd
be particularly likely to run on loongson).

I think there is probably just some confusion between snapshots (which are
regularly updated binaries produced from -current development trees) and
release. (The two coincide for a couple of days when the release is tagged;
sometimes people familiar with the development process make a copy of this
at this point as a "preview", which is OK but they then need to be aware
of what's going on with respect to newer snapshots, package builds etc).

Re: Mount HDD USB on 6.0 Stable: Fail

[Stephane HUC "CIOTBSD"]

Just for info:

I have an USB Pendrive for µSDCard.
This run correctly:

# dmesg | tail -n 5
umass0 at uhub0 port 2 configuration 1 interface 0 "Generic Mass Storage
Device" rev 2.00/1.00 addr 6
umass0: using SCSI over Bulk-Only
scsibus4 at umass0: 2 targets, initiator 0
sd1 at scsibus4 targ 1 lun 0:  SCSI0
0/direct removable serial.14cd1212121220130416
sd1: 14992MB, 512 bytes/sector, 30703616 sectors

$ disklabel sd1

# /dev/rsd1c:
type: SCSI
disk: SCSI disk
label: Storage Device
duid: 
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 1911
total sectors: 30703616
boundstart: 0
boundend: 30703616
drivedata: 0

16 partitions:
#size   offset  fstype [fsize bsize  cpg]
  c: 307036160  unused
  i: 30701568 2048NTFS

$ mount
/dev/sd0a on / type ffs (local, wxallowed, softdep)
/dev/sd0l on /home type ffs (local, nodev, nosuid, wxallowed, softdep)
/dev/sd0d on /tmp type ffs (local, nodev, nosuid, softdep)
/dev/sd0f on /usr type ffs (local, nodev, wxallowed, softdep)
/dev/sd0g on /usr/X11R6 type ffs (local, nodev, softdep)
/dev/sd0h on /usr/local type ffs (local, nodev, wxallowed, softdep)
/dev/sd0k on /usr/obj type ffs (local, nodev, nosuid, wxallowed, softdep)
/dev/sd0i on /usr/ports type ffs (local, nodev, nosuid, wxallowed, softdep)
/dev/sd0j on /usr/src type ffs (local, nodev, nosuid, softdep)
/dev/sd0e on /var type ffs (local, nodev, nosuid, softdep)
fusefs on /vol/USBMeHM type fuse (local)

$ ls -lart /vol/USBMeHM/

total 1409597
-rwx--  1 my_userid   my_userid   21 Jan  1  1970 .cm0013*
drwx--  1 my_userid   my_userid 4096 Jan  1  1970 ./
-rwx--  1 my_userid   my_userid721705484 Nov 11 11:06
jwb_F_201611_01_r720P.mp4*
drwxr-xr-x  4 root  wheel512 Nov 16 12:49 ../

OK!

Question: How i can "write" fstype "NTFS" on the "defective" HDD?
It's really formated in NTFS - mode normal, on Win7!

On 11/16/16 11:14, Stephane HUC "CIOTBSD" wrote:
> Hi, Alexey
> 
> Sorry, but it's not run!
> 
> $ doas /usr/local/libexec/hotplug-diskmount cleanup 3AS
> 
> $ doas /usr/local/libexec/hotplug-diskmount cleanup sd1
> 
> $ doas /usr/local/libexec/hotplug-diskmount attach -u my_userid -m 0700
> -F sd1
> 
> $ ls -al
> /vol/ 
>   
> 
> total 16
> drwxr-xr-x   4 root  wheel  512 Nov 16 11:03 ./
> drwxr-xr-x  14 root  wheel  512 Nov  6 18:19 ../
> drwx--   2 root  wheel  512 Nov 16 11:03 .db/
> drwx--   2 zou   wheel  512 Nov 16 11:03 3AS/
> 
> $ ls -al
> /vol/3AS/ 
>   
> 
> total 8
> drwx--  2 zou   wheel  512 Nov 16 11:03 ./
> drwxr-xr-x  4 root  wheel  512 Nov 16 11:03 ../
> 
> $ mount
> /dev/sd0a on / type ffs (local, wxallowed, softdep)
> /dev/sd0l on /home type ffs (local, nodev, nosuid, wxallowed, softdep)
> /dev/sd0d on /tmp type ffs (local, nodev, nosuid, softdep)
> /dev/sd0f on /usr type ffs (local, nodev, wxallowed, softdep)
> /dev/sd0g on /usr/X11R6 type ffs (local, nodev, softdep)
> /dev/sd0h on /usr/local type ffs (local, nodev, wxallowed, softdep)
> /dev/sd0k on /usr/obj type ffs (local, nodev, nosuid, wxallowed, softdep)
> /dev/sd0i on /usr/ports type ffs (local, nodev, nosuid, wxallowed, softdep)
> /dev/sd0j on /usr/src type ffs (local, nodev, nosuid, softdep)
> /dev/sd0e on /var type ffs (local, nodev, nosuid, softdep)
> 
> hotplug-diskmount create the mounting point but not mount it,
> apparently, is'nt-it?!
> 
> Egual, i modified /etc/hotplug/attach, as:
> 
> #!/bin/sh
> #
> # /etc/hotplug/{attach,detach}
> 
> DEVCLASS=$1
> DEVNAME=$2
> LOGIN="my_userid"
> 
> case "${DEVCLASS}" in
> 2)
> /usr/local/libexec/hotplug-diskmount attach -u "$LOGIN" -g
> "$LOGIN" -m 0700 -r dirty "$DEVNAME"
> ;;
> esac
> 
> Restarting hotplugd, but i've same bad result. :(
> 
> 
> 
> And, yes. i change the term "my_userid" by my real userid ;-)
> 
> 
> On 11/16/16 10:52, Alexey Vatchenko wrote:
>> From my attach script:
>> /usr/local/libexec/hotplug-diskmount attach -u av -g av -m 750 -r
>> dirty -F "$DEVNAME"
>>
>> As a result:
>> /dev/sd2i on /vol/TransMemory type ntfs (local, nodev, nosuid, read-only)
>>
>> With FUSE,
>> /usr/local/libexec/hotplug-diskmount attach -u av -g av -m 750 -r
>> dirty "$DEVNAME"
>>
>> And the result:
>> fusefs on /vol/EDGE type fuse (local)
>>
>> On Tue, Nov 15, 2016 at 9:15 AM, Stephane HUC "CIOTBSD"
>> > wrote:
>>
>>
>> $ /usr/local/libexec/hotplug-diskmount attach -u $USER -m 0700 -F 3AS
>>
>>
>> Try the following way:
>>
>> $ doas   /usr/local/libexec/hotplug-diskmount attach -u zou -m 0700 -F sd1
>>
>> where zou - your login name (as i understand from your letter) and sd1
>> - 

Re: pkg_add -u error

[Grégoire Jadi]

On 09/19/16 16:32, Edgar Pettijohn wrote:
> I recently upgraded to the latest snapshot and when upgrading packages
> I saw this:
> 
> system(/bin/sh, -c, /usr/local/bin/mktexlsr > /dev/null 2>&1) failed:  
> exit(127)
> 
> Which makes sense because there is no /usr/local/bin/mktexlsr on my system.
> I searched for it with pkg_info -Q mktexlsr as well as other variations with
> no luck. Not sure where to go from here. Ignore post to ports@? 
> 
> Any suggestions?

You can use pkg_locate to find files in packages.

# pkg_add pkglocatedb
$ pkg_locate :/usr/local/bin/mktexlsr
texlive_base-2015:print/texlive/base:/usr/local/bin/mktexlsr

Best,

> Thanks,




signature.asc
Description: OpenPGP digital signature

[6.0 Stable] Thunderbird + Enigmail fail

[Stephane HUC "CIOTBSD"]

Hi all.

I've a pb to sign and cifer emails with Thunderbird+Enigmail.

TBird version: 45. 2.0
Enigmail as addon: 1.9.6

My ~/.gnupg/gpg.conf pastebined:
https://paste.debian-fr.xyz/?5cf0b21a0aca1c65#xICcOcZCf01WXBPRi9Ue1v4IQnNmC8ITNMcPJx20VIU=

My ~/.gnupg/dirmngr.conf:
hkp-cacert /home/my_userid/Documents/K/others/sks-keyservers.netCA.pem

The Enigmail.log pastebined:
https://paste.debian-fr.xyz/?843d63290a15daea#Gq9jaa4tQGlG/2T/SEwGMmyvl6kPb2pdofQ84TiBhE8=

I can not sign or cifer email.
As see in enigmail.log: gpg: échec de la signature : Inappropriate
ioctl for device

Where is the problem?!



Just for information, TB profile run correctly on Debian Jessie ;-)


-- 
~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<<

Stephane HUC as PengouinPdt or CIOTBSD
b...@stephane-huc.net

Re: Broadcom Wifi Chip Datasheets

[Stefan Sperling]

On Tue, Nov 15, 2016 at 10:08:02PM -0800, Chris Cappuccio wrote:
> https://twitter.com/marcan42/status/798720961562361857
> 
> "Cypress bought Broadcom's WiFi business and apparently published all their 
> formerly unobtainium datasheets":
> 
> http://www.cypress.com/search/all?f[0]=meta_type%3Atechnical_documents[1]=resource_meta_type%3A575[2]=field_related_products%3A110101
> 

Does any of these sheets have detailed information about how the MAC and PHY
registers are supposed to be used? I can't even see definitions (offsets)
for such registers in a few PDFs I have sampled, let alone descriptions
about hardware init sequences, interrupt flows, etc.

It seems these sheets are mostly targeting product integrators who
run stock drivers.

Well, apparently the SPI interface documentation helps our ARM devs,
at least :)

Re: OpenBSD Ports "Libraries in packing-lists in the ports tree and libraries from installed packages don't match"

[Marcus MERIGHI]

Hello Stuart Longland, 

(need to add the surname, there's a prominent Stuart (sthen@) around :-)

I have the gut feeling your are moving some Linux-isms to OpenBSD land.
You are doing by far too much by yourself ;-)

I need to add I've never used the loongson port.

INSTALL.loongson talks of using the mips64el packages.
(which currently have a timestamp of 2016-10-26)

The easy way:
1) get http://yourmirr.openbsd.org/pub/OpenBSD/snapshots/loongson/bsd.rd
2) put bsd.rd to /bsd.rd
3) boot bsd.rd ('boot bsd.rd' at boot> prompt)
4) follow instructions
5) reboot
6) pkg_add  
   [or pkg_add -u if you already have the packages installed]
   (this usually "just works" because the installer puts the selected
   mirror into /etc/pkg.conf)
7) happy using until you need another package or you want to test a
   newer snapshot (which is a good thing for the project). 

stua...@longlandclan.id.au (Stuart Longland), 2016.11.16 (Wed) 10:19 (CET):
> Hi Marcus,
> On 16/11/16 18:48, Marcus MERIGHI wrote:
> >> I initially installed Ports from the snapshot, but then encountered some
> >> > 404 errors where package sources were no longer available.  Thus, I
> >> > figured I'd grab a version off the git mirror (github).
> > Without a dmesg you are lowering your chances. 
> 
> Ahh okay, I omitted this as I saw this as a userland issue not a kernel
> one, and dmesg can be rather long.
 
It's the basic information they want and somewhat shows that you've read
openbsd.org/mail.html and therefore are a good internet citizen ;-)

> The dmesg in full:
> > [ using 587952 bytes of bsd ELF symbol table ]
> > Copyright (c) 1982, 1986, 1989, 1991, 1993
> > The Regents of the University of California.  All rights reserved.
> > Copyright (c) 1995-2016 OpenBSD. All rights reserved.  
> > http://www.OpenBSD.org
> > 
> > OpenBSD 6.0 (GENERIC) #627: Thu Jul 28 21:15:50 MDT 2016
> > dera...@loongson.openbsd.org:/usr/src/sys/arch/loongson/compile/GENERIC

This one's downloaded sunday 2016-11-13?! 
Currently the file sets on the servers have a date of 2016-11-15?

> > real mem = 1073741824 (1024MB)
> > avail mem = 1057538048 (1008MB)
> > mainbus0 at root: Lemote Yeeloong
> > cpu0 at mainbus0: STC Loongson2F CPU 797 MHz, STC Loongson2F FPU
> > cpu0: cache L1-I 64KB D 64KB 4 way, L2 512KB 4 way
> > bonito0 at mainbus0: memory and PCI-X controller, rev 1
> > pci0 at bonito0 bus 0
> > rl0 at pci0 dev 7 function 0 "Realtek 8139" rev 0x10: irq 5, address 
> > 00:23:8b:35:6f:71
> > rlphy0 at rl0 phy 0: RTL internal PHY
> > smfb0 at pci0 dev 8 function 0 "Silicon Motion LynxEM+" rev 0xb0
> > wsdisplay0 at smfb0 mux 1: console (std, vt100 emulation)
> > ohci0 at pci0 dev 9 function 0 "NEC USB" rev 0x44: irq 7, version 1.0
> > ehci0 at pci0 dev 9 function 1 "NEC USB" rev 0x05: irq 7
> > usb0 at ehci0: USB revision 2.0
> > uhub0 at usb0 "NEC EHCI root hub" rev 2.00/1.00 addr 1
> > glxpcib0 at pci0 dev 14 function 0 "AMD CS5536 ISA" rev 0x03: rev 3, 32-bit 
> > 3579545Hz timer, watchdog, gpio, i2c
> > isa0 at glxpcib0
> > pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> > pckbd0 at pckbc0 (kbd slot)
> > wskbd0 at pckbd0: console keyboard, using wsdisplay0
> > pms0 at pckbc0 (aux slot)
> > wsmouse0 at pms0 mux 0
> > mcclock0 at isa0 port 0x70/2: mc146818 or compatible
> > ykbec0 at isa0 port 0x381/3
> > gpio1 at glxpcib0: 32 pins
> > iic at glxpcib0 not configured
> > glxclk0 at glxpcib0: clock, prof
> > pciide0 at pci0 dev 14 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel 0 
> > wired to compatibility, channel 1 wired to compatibility
> > wd0 at pciide0 channel 0 drive 0: 
> > wd0: 16-sector PIO, LBA48, 305245MB, 625142448 sectors
> > wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> > pciide0: channel 1 ignored (disabled)
> > auglx0 at pci0 dev 14 function 3 "AMD CS5536 Audio" rev 0x01: isa irq 9, 
> > CS5536 AC97
> > ac97: codec id 0x414c4760 (Avance Logic ALC655 rev 0)
> > audio0 at auglx0
> > ohci1 at pci0 dev 14 function 4 "AMD CS5536 USB" rev 0x02: isa irq 11, 
> > version 1.0, legacy support
> > ehci1 at pci0 dev 14 function 5 "AMD CS5536 USB" rev 0x02: isa irq 11
> > usb1 at ehci1: USB revision 2.0
> > uhub1 at usb1 "AMD EHCI root hub" rev 2.00/1.00 addr 1
> > usb2 at ohci0: USB revision 1.0
> > uhub2 at usb2 "NEC OHCI root hub" rev 1.00/1.00 addr 1
> > usb3 at ohci1: USB revision 1.0
> > uhub3 at usb3 "AMD OHCI root hub" rev 1.00/1.00 addr 1
> > apm0 at mainbus0
> > uvideo0 at uhub0 port 1 configuration 1 interface 0 "SuYin USB 2.0 Camera" 
> > rev 2.00/10.17 addr 2
> > video0 at uvideo0
> > umass0 at uhub1 port 1 configuration 1 interface 0 "Generic USB2.0-CRW" rev 
> > 2.00/58.87 addr 2
> > umass0: using SCSI over Bulk-Only
> > scsibus0 at umass0: 2 targets, initiator 0
> > sd0 at scsibus0 targ 1 lun 0:  SCSI0 0/direct 
> > removable serial.0bda015811417340
> > urtw0 at uhub1 port 4 configuration 1 interface 0 "Realtek RTL8187B" rev 
> > 2.00/2.00 addr 3
> > urtw0: RTL8187B rev E, address 00:17:c4:4d:ea:a0
> 

Re: Because in this day and age, there’s no one else doing what OpenBSD is doing?

[Boudewijn Dijkstra]

Op Tue, 15 Nov 2016 22:14:23 +0100 schreef SOUL_OF_ROOT 55  
:

Theo de Raadt wrote:

*Because in this day and age, there's no one else doing what OpenBSD is
doing?*


The interview was published July 2005. Do you think that "this day and  
age" still applies?




--
Gemaakt met Opera's e-mailprogramma: http://www.opera.com/mail/

Re: Mount HDD USB on 6.0 Stable: Fail

[Stephane HUC "CIOTBSD"]

Hi, Alexey

Sorry, but it's not run!

$ doas /usr/local/libexec/hotplug-diskmount cleanup 3AS

$ doas /usr/local/libexec/hotplug-diskmount cleanup sd1

$ doas /usr/local/libexec/hotplug-diskmount attach -u my_userid -m 0700
-F sd1

$ ls -al
/vol/   


total 16
drwxr-xr-x   4 root  wheel  512 Nov 16 11:03 ./
drwxr-xr-x  14 root  wheel  512 Nov  6 18:19 ../
drwx--   2 root  wheel  512 Nov 16 11:03 .db/
drwx--   2 zou   wheel  512 Nov 16 11:03 3AS/

$ ls -al
/vol/3AS/   


total 8
drwx--  2 zou   wheel  512 Nov 16 11:03 ./
drwxr-xr-x  4 root  wheel  512 Nov 16 11:03 ../

$ mount
/dev/sd0a on / type ffs (local, wxallowed, softdep)
/dev/sd0l on /home type ffs (local, nodev, nosuid, wxallowed, softdep)
/dev/sd0d on /tmp type ffs (local, nodev, nosuid, softdep)
/dev/sd0f on /usr type ffs (local, nodev, wxallowed, softdep)
/dev/sd0g on /usr/X11R6 type ffs (local, nodev, softdep)
/dev/sd0h on /usr/local type ffs (local, nodev, wxallowed, softdep)
/dev/sd0k on /usr/obj type ffs (local, nodev, nosuid, wxallowed, softdep)
/dev/sd0i on /usr/ports type ffs (local, nodev, nosuid, wxallowed, softdep)
/dev/sd0j on /usr/src type ffs (local, nodev, nosuid, softdep)
/dev/sd0e on /var type ffs (local, nodev, nosuid, softdep)

hotplug-diskmount create the mounting point but not mount it,
apparently, is'nt-it?!

Egual, i modified /etc/hotplug/attach, as:

#!/bin/sh
#
# /etc/hotplug/{attach,detach}

DEVCLASS=$1
DEVNAME=$2
LOGIN="my_userid"

case "${DEVCLASS}" in
2)
/usr/local/libexec/hotplug-diskmount attach -u "$LOGIN" -g
"$LOGIN" -m 0700 -r dirty "$DEVNAME"
;;
esac

Restarting hotplugd, but i've same bad result. :(



And, yes. i change the term "my_userid" by my real userid ;-)


On 11/16/16 10:52, Alexey Vatchenko wrote:
> From my attach script:
> /usr/local/libexec/hotplug-diskmount attach -u av -g av -m 750 -r
> dirty -F "$DEVNAME"
>
> As a result:
> /dev/sd2i on /vol/TransMemory type ntfs (local, nodev, nosuid, read-only)
>
> With FUSE,
> /usr/local/libexec/hotplug-diskmount attach -u av -g av -m 750 -r
> dirty "$DEVNAME"
>
> And the result:
> fusefs on /vol/EDGE type fuse (local)
>
> On Tue, Nov 15, 2016 at 9:15 AM, Stephane HUC "CIOTBSD"
> > wrote:
>
>
> $ /usr/local/libexec/hotplug-diskmount attach -u $USER -m 0700 -F 3AS
>
>
> Try the following way:
>
> $ doas   /usr/local/libexec/hotplug-diskmount attach -u zou -m 0700 -F sd1
>
> where zou - your login name (as i understand from your letter) and sd1
> - currently attached device.

-- 
~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<<

Stephane HUC as PengouinPdt or CIOTBSD
b...@stephane-huc.net

Re: Why on earth would online voting be insecure?

[Rich Kulawiec]

On Mon, Nov 14, 2016 at 05:52:51PM -0500, Alan Corey wrote:
> It seems simple to me [...]

It seems simple because you haven't studied voting systems and their
requirements for privacy, security, integrity, reliability, etc.
You have also failed to consider that the privacy, security, integrity,
reliability, etc. problems that are now pervasive throughout computing
and Internet operations are antithetical to those.  In other words, the
things that voting systems need are just about exactly the things that
contemporary Internet computing environments lack.

I suggest if you're really interested in this issue that you start your
education here:

Douglas W. Jones on Voting and Elections
http://homepage.divms.uiowa.edu/~jones/voting/

That page has a large number of links to articles, reports, essays, papers,
etc. on these topics -- and to many sites which contain still more.  It's
an excellent jumping-off point for enquiry into many aspects of this
problem.  After you've read for a few months, I think you'll see that
the problem is anything but "simple".

---rsk

Re: Mount HDD USB on 6.0 Stable: Fail

[Alexey Vatchenko]

>From my attach script:
/usr/local/libexec/hotplug-diskmount attach -u av -g av -m 750 -r dirty -F
"$DEVNAME"

As a result:
/dev/sd2i on /vol/TransMemory type ntfs (local, nodev, nosuid, read-only)

With FUSE,
/usr/local/libexec/hotplug-diskmount attach -u av -g av -m 750 -r dirty
"$DEVNAME"

And the result:
fusefs on /vol/EDGE type fuse (local)

On Tue, Nov 15, 2016 at 9:15 AM, Stephane HUC "CIOTBSD" <
b...@stephane-huc.net> wrote:

>
> $ /usr/local/libexec/hotplug-diskmount attach -u $USER -m 0700 -F 3AS


Try the following way:

$ doas   /usr/local/libexec/hotplug-diskmount attach -u zou -m 0700 -F sd1

where zou - your login name (as i understand from your letter) and sd1 -
currently attached device.

Re: OpenBSD Ports "Libraries in packing-lists in the ports tree and libraries from installed packages don't match"

[Stuart Longland]

Hi Marcus,
On 16/11/16 18:48, Marcus MERIGHI wrote:
>> I initially installed Ports from the snapshot, but then encountered some
>> > 404 errors where package sources were no longer available.  Thus, I
>> > figured I'd grab a version off the git mirror (github).
> Without a dmesg you are lowering your chances. 

Ahh okay, I omitted this as I saw this as a userland issue not a kernel
one, and dmesg can be rather long.

The dmesg in full:
> [ using 587952 bytes of bsd ELF symbol table ]
> Copyright (c) 1982, 1986, 1989, 1991, 1993
>   The Regents of the University of California.  All rights reserved.
> Copyright (c) 1995-2016 OpenBSD. All rights reserved.  http://www.OpenBSD.org
> 
> OpenBSD 6.0 (GENERIC) #627: Thu Jul 28 21:15:50 MDT 2016
> dera...@loongson.openbsd.org:/usr/src/sys/arch/loongson/compile/GENERIC
> real mem = 1073741824 (1024MB)
> avail mem = 1057538048 (1008MB)
> mainbus0 at root: Lemote Yeeloong
> cpu0 at mainbus0: STC Loongson2F CPU 797 MHz, STC Loongson2F FPU
> cpu0: cache L1-I 64KB D 64KB 4 way, L2 512KB 4 way
> bonito0 at mainbus0: memory and PCI-X controller, rev 1
> pci0 at bonito0 bus 0
> rl0 at pci0 dev 7 function 0 "Realtek 8139" rev 0x10: irq 5, address 
> 00:23:8b:35:6f:71
> rlphy0 at rl0 phy 0: RTL internal PHY
> smfb0 at pci0 dev 8 function 0 "Silicon Motion LynxEM+" rev 0xb0
> wsdisplay0 at smfb0 mux 1: console (std, vt100 emulation)
> ohci0 at pci0 dev 9 function 0 "NEC USB" rev 0x44: irq 7, version 1.0
> ehci0 at pci0 dev 9 function 1 "NEC USB" rev 0x05: irq 7
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "NEC EHCI root hub" rev 2.00/1.00 addr 1
> glxpcib0 at pci0 dev 14 function 0 "AMD CS5536 ISA" rev 0x03: rev 3, 32-bit 
> 3579545Hz timer, watchdog, gpio, i2c
> isa0 at glxpcib0
> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> pckbd0 at pckbc0 (kbd slot)
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pms0 at pckbc0 (aux slot)
> wsmouse0 at pms0 mux 0
> mcclock0 at isa0 port 0x70/2: mc146818 or compatible
> ykbec0 at isa0 port 0x381/3
> gpio1 at glxpcib0: 32 pins
> iic at glxpcib0 not configured
> glxclk0 at glxpcib0: clock, prof
> pciide0 at pci0 dev 14 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel 0 
> wired to compatibility, channel 1 wired to compatibility
> wd0 at pciide0 channel 0 drive 0: 
> wd0: 16-sector PIO, LBA48, 305245MB, 625142448 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> pciide0: channel 1 ignored (disabled)
> auglx0 at pci0 dev 14 function 3 "AMD CS5536 Audio" rev 0x01: isa irq 9, 
> CS5536 AC97
> ac97: codec id 0x414c4760 (Avance Logic ALC655 rev 0)
> audio0 at auglx0
> ohci1 at pci0 dev 14 function 4 "AMD CS5536 USB" rev 0x02: isa irq 11, 
> version 1.0, legacy support
> ehci1 at pci0 dev 14 function 5 "AMD CS5536 USB" rev 0x02: isa irq 11
> usb1 at ehci1: USB revision 2.0
> uhub1 at usb1 "AMD EHCI root hub" rev 2.00/1.00 addr 1
> usb2 at ohci0: USB revision 1.0
> uhub2 at usb2 "NEC OHCI root hub" rev 1.00/1.00 addr 1
> usb3 at ohci1: USB revision 1.0
> uhub3 at usb3 "AMD OHCI root hub" rev 1.00/1.00 addr 1
> apm0 at mainbus0
> uvideo0 at uhub0 port 1 configuration 1 interface 0 "SuYin USB 2.0 Camera" 
> rev 2.00/10.17 addr 2
> video0 at uvideo0
> umass0 at uhub1 port 1 configuration 1 interface 0 "Generic USB2.0-CRW" rev 
> 2.00/58.87 addr 2
> umass0: using SCSI over Bulk-Only
> scsibus0 at umass0: 2 targets, initiator 0
> sd0 at scsibus0 targ 1 lun 0:  SCSI0 0/direct 
> removable serial.0bda015811417340
> urtw0 at uhub1 port 4 configuration 1 interface 0 "Realtek RTL8187B" rev 
> 2.00/2.00 addr 3
> urtw0: RTL8187B rev E, address 00:17:c4:4d:ea:a0
> vscsi0 at root
> scsibus1 at vscsi0: 256 targets
> softraid0 at root
> scsibus2 at softraid0: 256 targets
> pmon bootpath: /dev/disk/wd0
> boot device: wd0
> root on wd0a (43fc3fdb63b966d0.a) swap on wd0b dump on wd0b

> I think I've understood you are running a snapshot as of some point in
> time?

Yes, I basically downloaded a new snapshot on Sunday and unpacked that.
 Sadly, I didn't keep it around to refer to.

> While you are on, say, a snapshot as of 2016-10-01 the project keeps
> moving. Depending on the point in the release process it takes hours to
> days until _your_ snapshot isn't the current snapshot anymore. 
> 
> packages(7) keep being built against the current snapshot, not _your_
> snapshot. Library mismatches between *your* snapshot base system and the
> *projects* current ports happen soon.

Ahh, so the ports tree is rolling-release and not tied to a particular
release of OpenBSD.  This makes sense.

> But 404s? Have you checked whether the 404-files are on the servers with
> a different version number possibly?

I'll have to go over more thoroughly which packages were causing the
download errors, when I saw them my first instinct was: "the ports are
out of date, try updating those first in case they've fixed the download
links".

Upstream projects sometimes do move things around, and often without
telling people, so 

Re: OpenBSD Ports "Libraries in packing-lists in the ports tree and libraries from installed packages don't match"

[Marcus MERIGHI]

stua...@longlandclan.id.au (Stuart Longland), 2016.11.16 (Wed) 00:25 (CET):
> Hi all,
> 
> I've recently started using OpenBSD, installing it on an old Lemote
> Yeeloong, largely because of uncertainty in where Debian Linux is
> headded with this port.
> 
> So far so good, it's been largely smooth sailing.  I'm in the process of
> installing what I'd normally use on Linux.  Prior to this I was running
> Gentoo Linux with a n32 userland on the device, and some packages are
> seemingly incompatible with n32 (and also have problems on x86-64's x32
> userland).
> 
> I note OpenBSD/mips64 uses n64, so we'll see how that goes.  This was
> something I was unable to achieve directly with Gentoo.  (And yes, I
> recognise OpenBSD is not Linux, not expecting it to work like Linux either.)
> 
> I initially installed Ports from the snapshot, but then encountered some
> 404 errors where package sources were no longer available.  Thus, I
> figured I'd grab a version off the git mirror (github).

Without a dmesg you are lowering your chances. 

I think I've understood you are running a snapshot as of some point in
time?

While you are on, say, a snapshot as of 2016-10-01 the project keeps
moving. Depending on the point in the release process it takes hours to
days until _your_ snapshot isn't the current snapshot anymore. 

packages(7) keep being built against the current snapshot, not _your_
snapshot. Library mismatches between *your* snapshot base system and the
*projects* current ports happen soon. 
But 404s? Have you checked whether the 404-files are on the servers with
a different version number possibly?

Thus you need to install the wanted packages soon after putting a
snapshot on your machine.

(You could cvs check out the ports tree around the time you are
downloading the snapshot and *hope* that this ports tree matches your
snapshot base install and then build your packages yourself.)

> So I have a couple of packages (maybe about a dozen) installed via the
> snapshot ports and some via git ports.  This might be the root of my
> problems.

Are you talking about the openbsd-wip ports?
If yes I think you are doing something unsupported and you won't get
help from @openbsd people. 

While reading ports@ I often see that ports-people talk of things which
have been made ready in openbsd-wip for inclusion in the ports tree.

> I now have seen the following a couple of times:
> > ===>  Building package for py-cairo-1.10.0p1
> > Create /usr/local/ports/packages/mips64el/all/py-cairo-1.10.0p1.tgz
> > Error: Libraries in packing-lists in the ports tree
> >and libraries from installed packages don't match
> > --- /tmp/dep_cache.5mrOMvzTf/portstree-py-cairo-1.10.0p1Wed Nov 16 
> > 09:11:03 2016
> > +++ /tmp/dep_cache.5mrOMvzTf/inst-py-cairo-1.10.0p1 Wed Nov 16 09:11:04 
> > 2016
> > @@ -13,8 +13,8 @@
> >  -W expat.11.0
> >  -W fontconfig.10.0
> >  -W freetype.25.0
> > --W glib-2.0.4200.4
> > --W gobject-2.0.4200.4
> > +-W glib-2.0.4200.3
> > +-W gobject-2.0.4200.3
> >  -W m.9.0
> >  -W pcre.3.0
> >  -W pixman-1.32.6
> > *** Error 1 in /usr/ports/graphics/py-cairo 
> > (/usr/ports/infrastructure/mk/bsd.port.mk:3157 'wantlib-args')
> > *** Error 1 in /usr/ports/graphics/py-cairo 
> > (/usr/ports/infrastructure/mk/bsd.port.mk:1888 
> > '/usr/local/ports/packages/mips64el/all/py-cairo-1.10.0p1.tgz')
> 
> I understand this is due to a discrepancy between the versions normally
> used in packages and those actually installed.  I've been able to work
> around these using PKG_CREATE_NO_CHECKS=yes but I sense this is not a
> good idea long-term.
> 
> What's the best way of fixing the underlying problem?  Would manually
> updating (in this case) the glib and gobject ports fix it, or is there
> some other fix?

I think you'd better remove all packages, put the latest snapshot on,
reinstall the packages you want right away.
Be a happy user after that until you 1) notice you need software from
packages that are already ahead of your snapshot or 2) you have spare
time to install the current snapshot of the day just for fun and testing
(and increased likelyhood of help from @openbsd people, which are always
talking -current).

Marcus

> Regards,
> -- 
> Stuart Longland (aka Redhatter, VK4MSL)
> 
> I haven't lost my mind...
>   ...it's backed up on a tape somewhere.
> 
> 
> !DSPAM:582b99ba321761298142048!