General Linux Chat and Small Questions v. Year of the Linux Desktop! - Hardware & Software

Err, mosh uses AES-128 in OCB mode, it's perfectly fine crypto. SSH doesn't specify what cryptography can be used, but they typically use AES.

[QUOTE=nikomo;48297690]Err, mosh uses AES-128 in OCB mode, it's perfectly fine crypto. SSH doesn't specify what cryptography can be used, but they typically use AES.[/QUOTE] [url]https://tools.ietf.org/html/rfc4253#page-9[/url] Yes it does? You can also set this explicitly in the sshd_config and ssh_config files on your systems.

[QUOTE=benjojo;48297342]"Why use HTTPS when clients still support RC4" is basically what you are saying here, Slightly degraded security is better than zero security. It's all about threat modelling and figuring out what you are trying to protect and what you win and loose out of using something.[/QUOTE] Wouldn't supporting depricated security make you more vulnerable to downgrade attacks?

[QUOTE=mastersrp;48297735][url]https://tools.ietf.org/html/rfc4253#page-9[/url] Yes it does? You can also set this explicitly in the sshd_config and ssh_config files on your systems.[/QUOTE] The cipher listed as required in that document is no longer in popular usage, so it's clearly not being followed. I have absolutely no idea what the hell you're trying to say. mosh uses AES, most SSH uses AES but you can change it if you want, what is so difficult about this concept?

He thinks mosh is an unnecessary reinvention of the wheel. Or at least that's what I'm getting.

[QUOTE=lavacano;48299830]He thinks mosh is an unnecessary reinvention of the wheel. Or at least that's what I'm getting.[/QUOTE] This indeed, although it is a slightly better wheel for shit connections, it is pretty much this. Having this be an integrated part of SSH limits the amount of simultanious wheels running. However, it is also an additional attack surface to secure yourself on, which is just as problematic.

[QUOTE=Mega1mpact;48298761]Wouldn't supporting depricated security make you more vulnerable to downgrade attacks?[/QUOTE] For (ignoring fixed issues like [URL="https://en.wikipedia.org/wiki/FREAK"]FREAK[/URL]) downgrade attacks to happen, you need both sites to play ball with the crypto set you are trying to downgrade someone into doing. RC4 being something that is commonly supported on both sides makes it a nice target to be downgraded to, provided that both sides are willing to talk it. Either way. What I am more saying is that mosh does not have the deployment, nor is it under the same amount of scrutiny that OpenBSD SSH is. So you may benifit from the "Security By Obscurity" factor, or you may loose. I am personally very iffy around anything that tries to emulate or replicate [URL="https://en.wikipedia.org/wiki/Datagram_Transport_Layer_Security"]DTLS[/URL] Though that is not to say that OpenSSH has some crappyish defaults (RC4,3DES,Blowfish) when it comes to crypto ciphers, though the exchange what ciphers to use is [I]with[/I] [URL="http://security.stackexchange.com/questions/79997/openssh-downgrade-attack"]the key fingerprint exchange[/URL], making it slightly less bad. idk. Security is hard.

[code]braxen@vps:/$ sudo dpkg -C The following packages have been unpacked but not yet configured. They must be configured using dpkg --configure or the configure menu option in dselect for them to work: mountall filesystem mounting tool upstart event-based init daemon The following packages are only half configured, probably due to problems configuring them the first time. The configuration should be retried using dpkg --configure <package> or the configure menu option in dselect: plymouth boot animation, logger and I/O multiplexer braxen@vps:/$ sudo dpkg --configure plymouth Setting up plymouth (0.9.0-9) ... update-initramfs: deferring update (trigger activated) update-rc.d: error: expected NN after stop usage: update-rc.d [-n] [-f] <basename> remove update-rc.d [-n] <basename> defaults [NN | SS KK] update-rc.d [-n] <basename> start|stop NN runlvl [runlvl] [...] . update-rc.d [-n] <basename> disable|enable [S|2|3|4|5] -n: not really -f: force The disable|enable API is not stable and might change in the future. dpkg: error processing package plymouth (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for initramfs-tools (0.120) ... Errors were encountered while processing: plymouth braxen@vps:/$[/code] am i fucked? i can't do anything [B]edit[/B] fixed with this: [url]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783359[/url] hopefully

Do the logs say anything? i.e. /var/log/Xorg.[number].log and maybe dmesg?.

booting my live disk now

Hey does anybody know why this happens? Whenever I put my laptop to sleep it can wake back up and show the login screen just fine, but when I enter my password the screen will turn off completely (screen will turn black and the backlight will turn off) I can press ctrl+alt+f2 and the screen will turn on but if I try to go back it will turn off again. I'm using Xubuntu 14.04 and my laptop is a Lenovo Ideapad z585 with a Radeon hd 7640g.

[QUOTE=initrd;48302584]Do the logs say anything? i.e. /var/log/Xorg.[number].log and maybe dmesg?.[/QUOTE] Logs [url]https://drive.google.com/open?id=0B-UpzvBwI7R-emNkSURvX3dOMlE[/url] [url]https://drive.google.com/open?id=0B-UpzvBwI7R-Q1g5NmlwUnpudjQ[/url]

[URL="https://paste.ee/r/hCh0R"]Grepped logs[/URL]. [CODE][ 142.382] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.[/CODE] [QUOTE]GT220[/QUOTE] [QUOTE]What we've tried. Installing 331, 304, 346, nvidia-current(they have ALL resulted being dropped back into TTY)[/QUOTE] So the 0.log is the nvidia driver loading and failing to init the gpu; the 1.log is just nouveau working fine. After remembering having problems with my 9500GreenToaster and the new drivers google found [URL="https://www.phoronix.com/scan.php?page=news_item&px=MTYyODA"]this[/URL]. [QUOTE]NVIDIA is ceasing to support their older GeForce 8, 9, 200, and 300 series from their mainline driver[/QUOTE] So i went to the nvidia website and found that the newest driver for linux is 352.21, but the range where the GT220 is supported seems to be from 337.12 to 340.76 (← Which i'm using right now on Xubuntu 15.04). The problem seems to be that you aren't using a driver with support for your card (and don't have one available in additional drivers thing); maybe adding the [URL="http://https://launchpad.net/~xorg-edgers/+archive/ubuntu/ppa"]xorg-edgers[/URL] ppa and installing 340.76 will fix the problem.

I don't remember dpkg being that shitty :v:

Did he switch to nouveau before trying to do whatever he's doing in that?(From the additional drivers instead of apt). By the way the [B]links[/B] web browser seems to work with facepunch so he likely doesn't need to reboot to post. [QUOTE=Lyokanthrope;48311066]I don't remember dpkg being that shitty :v:[/QUOTE] [A-Z]*ubuntu tends to break when doing anything from the terminal; specially if it involves anything closed source/proprietary.

I dual-boot Mint 17 and Win7. How bad would upgrading to Win10 fuck me up?

[QUOTE=Amiga OS;48313079]It will probably shred your bootloader at least.[/QUOTE] Nothing [URL="http://ubuntuhandbook.org/index.php/2013/11/reinstall-grub-ubuntu-wont-boot/"]grub-install[/URL] can't fix from a live CD though.

Surprisingly, upgrading from 8.1 to 10 does not fuck up GRUB My evidence being that it asks me if I want to boot Fedora or Windows 8 (haven't renamed it yet), I haven't tried booting Fedora yet

makes enough sense, the only parts of the bootloader windows 10 would need to upgrade are the ones in the boot partition, the part it would burn onto the MBR or whatever are probably unchanged

[t]http://i.imgur.com/TcxrBC1.jpg[/t] lmao buildroot [editline]31st July 2015[/editline] Same command w/ the file on /tmp works fine, wtf.

[QUOTE=lavacano;48335485]makes enough sense, the only parts of the bootloader windows 10 would need to upgrade are the ones in the boot partition, the part it would burn onto the MBR or whatever are probably unchanged[/QUOTE] Thanks to UEFI, there's no MBR boot sector, just a FAT32 boot partition and the EFI boot entry in the firmware.

Something really wants to pull my heart back to linux: [img]http://i.imgur.com/54Y0wNg.png[/img] Put the archbang live 512MB image inside a 4GB Fat32 partion and ran with NeoGrub configured from EasyBCD. I love how lightweight it is while having audio and video playback in firefox, within reasonable ram usage. I might switch again sometime soon, as I love how snappy it is. Wine is getting better each release, and I don't really care about games nowadays. The animation-less snappiness might be a nostalgic affair reminding windows xp for me. Privacy concerns of windows 10 just pushes me away from it, even when it is a capable OS being fully functional with some features here and there. Microsoft is opensourcing .net framework more and more which I use somewhat for programming. However I love the native feel of programs, so it's time to practice on C++ and use a gui library. [editline]31st July 2015[/editline] I have nothing to lose. [editline]31st July 2015[/editline] Why are some people still against systemd?

[QUOTE=ichiman94;48339873]Why are some people still against systemd?[/QUOTE] A hate for binary logs, and mental retardation.

[QUOTE=ichiman94;48339873]Something really wants to pull my heart back to linux: ... Why are some people still against systemd?[/QUOTE] Let me ask you a better question: Why is everyone not programming in C? Think about that for a while.

[QUOTE=ichiman94;48339873]Why are some people still against systemd?[/QUOTE] I don't want it taking up [b]all[/b] of my core processes (syslogger, cron, etc) and not giving me the option to replace components that fail. Last I checked, that was still the current state of systemd.

[QUOTE=ichiman94;48339873][img]http://i.imgur.com/54Y0wNg.png[/img][/QUOTE] scrot is deprecated and unmaintained, you should use [url=https://github.com/naelstrof/maim]maim[/url] instead :). It's in the official repos with slop.

Returned to the dark side and am installing Ubuntu 14.04. As much as I like Arch Linux for being up to date, I do spend periods when I don't use it for long enough that things break. I'm quite happy to have something just work for once, especially seeing everything seems to target the latest Ubuntu LTS release...

[QUOTE=ben1066;48341060]Returned to the dark side and am installing Ubuntu 14.04. As much as I like Arch Linux for being up to date, I do spend periods when I don't use it for long enough that things break. I'm quite happy to have something just work for once, especially seeing everything seems to target the latest Ubuntu LTS release...[/QUOTE] There's a [I]wide[/I] middleground between ubuntu and arch ya know. Like... Debian. Or CentOS/Fedora.

[QUOTE=Levelog;48341073]There's a [I]wide[/I] middleground between ubuntu and arch ya know. Like... Debian. Or CentOS/Fedora.[/QUOTE] I am aware, this is as I said, in part to just being the target platform for a lot of things (including coreclr which I am currently contributing to). I run Debian stable happily on a VPS but that seems to fall behind even further than Ubuntu LTS versions between releases, though I'm not sure how unstable handles a long period between updates? Not tried Fedora or any RPM based distro before mind. Also kinda lied, still backing up data from the drive I need to install to so I guess if there is a good reason to try something else I'm open to.

[QUOTE=lavacano;48340381]I don't want it taking up [b]all[/b] of my core processes (syslogger, cron, etc) and not giving me the option to replace components that fail. Last I checked, that was still the current state of systemd.[/QUOTE] Don't worry, you can probably disable those components by now, patch a few things up, force it through a compilation and then install it so you can boot into kernel panic.