Hi all .
i add some .
USB memory only 2GB running openbsd works as dhcpd + nat .
namely
sd1 at scsibus2 targ 1 lun 0: SCSI0
0/direct removable serial.1d0d0211078C0D1310DE
sd1: 1900MB, 512 bytes/sector, 3891200 sectors
root on sd1a (4ef3e82a493a09dc.a) swap on sd1b dump on sd1b
# df
Filesystem
Em 27-06-2014 19:48, Stuart Henderson escreveu:
> "yes, cracking a stolen hash is faster, but it's not what the average user
> should worry about"
>
> I disagree, that is *exactly* what the average user should worry about.
> And knowing that some people use xkcd style passwords, who would start on
On 2014-06-27, Giancarlo Razzolini wrote:
> Perhaps you should take a look at this funny and very accurate xkcd
> comic strip:
>
> http://xkcd.com/936/
"yes, cracking a stolen hash is faster, but it's not what the average user
should worry about"
I disagree, that is *exactly* what the average u
For people who might stumble on this thread I ended up using Nginx with
a configuration file which looks similar to this.
Predrag
# $OpenBSD: nginx.conf,v 1.16 2014/01/28 14:48:53 stephan Exp $
#user www;
worker_processes 4;
#syslog local5 nginx;
#error_log logs/error.log;
#er
On 6/27/14, Theo de Raadt wrote:
>> On 2014-06-26, Scott Vanderbilt wrote:
>> > Having done a little man page reading on boot-time configuration, I
>> > learned about the existence of ukc. I'm wondering whether something
>> > like
>> >
>> >ukc> disable acpi0
>> >
>> > might circumvent the ker
On Fri, Jun 27, 2014 at 12:37:33PM -0700, Scott Vanderbilt wrote:
> On 6/27/2014 12:10 PM, Stuart Henderson wrote:
> >On 2014-06-26, Scott Vanderbilt wrote:
> >>Having done a little man page reading on boot-time configuration, I
> >>learned about the existence of ukc. I'm wondering whether somethi
On Fri, Jun 27, 2014 at 01:15:59PM -0600, Theo de Raadt wrote:
> > On 2014-06-26, Scott Vanderbilt wrote:
> > > Having done a little man page reading on boot-time configuration, I
> > > learned about the existence of ukc. I'm wondering whether something like
> > >
> > >ukc> disable acpi0
> >
On 6/27/2014 12:10 PM, Stuart Henderson wrote:
On 2014-06-26, Scott Vanderbilt wrote:
Having done a little man page reading on boot-time configuration, I
learned about the existence of ukc. I'm wondering whether something like
ukc> disable acpi0
might circumvent the kernel panic and allow
Em 27-06-2014 11:50, Stefan Wollny escreveu:
> Hi misc@-readers!
>
> I have once more read man afterboot(8) and a question came up related
> to the superuser's password.
>
> In section 'root password' advisory is given to "choose a password
> that has digits and special characters (not space)". Thi
> On 2014-06-26, Scott Vanderbilt wrote:
> > Having done a little man page reading on boot-time configuration, I
> > learned about the existence of ukc. I'm wondering whether something like
> >
> >ukc> disable acpi0
> >
> > might circumvent the kernel panic and allow the boot to successfully
On 2014-06-26, Scott Vanderbilt wrote:
> Having done a little man page reading on boot-time configuration, I
> learned about the existence of ukc. I'm wondering whether something like
>
>ukc> disable acpi0
>
> might circumvent the kernel panic and allow the boot to successfully
> complete. I
Unfortunately, not. It was a fresh install from a CD image to a hard
drive which I then shipped to the ISP for installation, which replaced a
failing drive in my machine co-located there.
In any event, bypassing acpi in ukc got the machine up again, and I was
able to upgrade to the latest snap
On Fri, Jun 27, 2014 at 12:56:33PM -0400, Ted Unangst wrote:
> On Fri, Jun 27, 2014 at 16:50, Stefan Wollny wrote:
> > Hi misc@-readers!
> >
> > I have once more read man afterboot(8) and a question came up related
> > to the superuser's password.
> >
> > In section 'root password' advisory is g
On Fri, Jun 27, 2014 at 16:50, Stefan Wollny wrote:
> Hi misc@-readers!
>
> I have once more read man afterboot(8) and a question came up related
> to the superuser's password.
>
> In section 'root password' advisory is given to "choose a password
> that has digits and special characters (not spa
On Fri, Jun 27, 2014 at 6:12 AM, Josh Grosse wrote:
> On 2014-06-27 08:21, Kent Fritz wrote:
>> Seeing the same here. I tested re-creating my keys, and the problem
>> seems to be with password. With password, it fails; without, it
>> works.
>
>
> If I didn't have passphrases, I wouldn't use ssh-
Hi misc@-readers!
I have once more read man afterboot(8) and a question came up related
to the superuser's password.
In section 'root password' advisory is given to "choose a password
that has digits and special characters (not space)". This last advice
is what I do not understand - all of my pas
I know on my laptop no acpi meant doesn't work. My saving grace is I
always keep a kernel from the previous snapshot I tried as obsd. So if
bsd doesn't work, I just boot from that. Do you have an older snapshot
kernel you can tell tech support to boot into?
On Thu, Jun 26, 2014 at 7:36 PM, Scott V
I can also confirm that newest snapshot works now.
On Thu, Jun 26, 2014 at 7:45 AM, Nils R wrote:
> Works now with the latest snapshot (dsdt.c rev. 1.211), thanks!
On 2014-06-27 08:21, Kent Fritz wrote:
On Fri, Jun 27, 2014 at 4:29 AM, Christian Weisgerber
wrote:
It's most likely fallout from the ssh changes on June 23:
Yes, there were significant revisions, and they are integrated, as I
cannot back off ssh-add.c r1.110 alone.
I'd mucked about with k
On Fri, Jun 27, 2014 at 4:29 AM, Christian Weisgerber
wrote:
> On 2014-06-27, Josh Grosse wrote:
>
>> I just updated from a June 17 to June 26 snapshot. The ssh-add utility
>> now fails immediately: [...]
>>
>> Between these two snapshots there was a major bump for libcrypto from 28.0
>> to 29.0
On 2014-06-27, Josh Grosse wrote:
> I just updated from a June 17 to June 26 snapshot. The ssh-add utility
> now fails immediately: [...]
>
> Between these two snapshots there was a major bump for libcrypto from 28.0
> to 29.0, but that may not be relevant.
It's most likely fallout from the ssh
Hi,all.
I was able to do it thanks to the instruction of misc all
.I report it.
In addition , this openBSD is running on USB memory only .
sd1 at scsibus2 targ 1 lun 0: SCSI4
0/direct removable serial.85641000CE38A0VNSTPO
sd1: 30944MB, 512 bytes/sector, 63373312 sectors
OpenBSD
0
C Cyprus
P Nicosia
T Strovolos
I Socrates Papachilleos
M socratesp1...@gmail.com
B +35799222339
N Over 10 years of experience Technical Support and Consulting for Linux/
OpenBSD networking and Server Administration. Providing fully
customized solutions for Routers/Firewalls,VPN servers, IDS s
One of the best pads around are Fujipoly [1] with thermal conductivity
of 17 W/mK.
These made a big difference on several laptop workstations that were
having overheating issues.
Some default pads are good enough, but in some cases thermal
conductivity is a problem and you just need a better
It think the designer wanted to keep the board compatible with the old
case, or the other way around. To cool the CPU more one needs better pads (
i doubt there are much better, since the industry has standards) or adds a
fan.
Current situation is like this:
\__/ - CPU
--
25 matches
Mail list logo
