Re: copy and paste, under Wayland, and to and from an XTerm, was relating to dl audio and video
On 30/8/20 3:01 pm, Tim Connors via luv-main wrote: > It theoretically is not safe to simple paste the selection into an editor > before vetting it. Through CSS and javascript, what you select in a > browser and what ends up in the copy-paste buffer are frequently > different. I notice that XUbuntu 20.04 now has a paste preview window that shows up any time you paste data containing at least one carriage return so you can decide whether to permit the paste or block it. Very useful! Cheers, Andrew -- mailto:and...@sericyb.com.au Andrew Pam https://sericyb.com.au/ Manager, Serious Cybernetics https://glasswings.com.au/Partner, Glass Wings ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: copy and paste, under Wayland, and to and from an XTerm, was relating to dl audio and video
On Sun, 30 Aug 2020, Craig Sanders wrote: > On Tue, Aug 18, 2020 at 04:54:08PM +1000, Mark Trickett wrote: > > I do understand that there can be security issues if used without a measure > > of care and thoughtful, but it also has much merit when coping with some of > > the regular expressions that come up as examples in email and on web pages. > > the "security issues" comes from blindly executing code/commands that you > don't understand. > > treat everything as just an example that needs further research. never execute > something posted by someone else(*) unless you know what it does and how and > why. It theoretically is not safe to simple paste the selection into an editor before vetting it. Through CSS and javascript, what you select in a browser and what ends up in the copy-paste buffer are frequently different. That copy paste buffer may contain ANSI-escape sequences to exit your editor and run a command directly. https://news.ycombinator.com/item?id=10554679 https://security.stackexchange.com/questions/39118/how-can-i-protect-myself-from-this-kind-of-clipboard-abuse -- Tim Connors ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: copy and paste, under Wayland, and to and from an XTerm, was relating to dl audio and video
On Tue, Aug 18, 2020 at 04:54:08PM +1000, Mark Trickett wrote: > Many thanks for your excellent posts, I am learning more. However I have > Debian 10, nominally up to date, and it has Wayland with Gnome as the > desktop. I am finding it very frustrating that I cannot copy and paste to > and from the XTerm window. Sorry, i don't use Wayland, have no idea what could be going wrong with this. I can't see the point of Wayland. TBH, it seems like the systemd of X - a half-arsed crappy partial implementation of only the stuff that the devs personally use because there's no way that anyone else could ever need anything they don't use. Also, CADT syndrome: never fix anything. toss out the old garbage, make way for the shiny new garbage. Fixing bugs is boring. Reimplementing from scratch every year or two is fun and exciting and it'll be perfect. For sure, this time. > I used to be able to do with earlier terminal emulation under the XWindows > system. I used it to be able to copy text from a terminal into an email, and > commands back from email, ensuring that I did not make typos. That's weird. i'd be surprised if Wayland was actually incapable of doing something as basic as copy and paste between terminal windows, so it's probably a bug or a configuration error. Maybe try a different terminal instead of xterm. There are dozens to choose from. I mostly use roxterm (full-height apart from the space used by xfce4-panel, full-width, approx 250x60 depending on font size - great for viewing log files), but sometimes I use xfce4-terminal if i want a tall, narrow window (80 or 132 x 60) to fit beside something else. > I do understand that there can be security issues if used without a measure > of care and thoughtful, but it also has much merit when coping with some of > the regular expressions that come up as examples in email and on web pages. the "security issues" comes from blindly executing code/commands that you don't understand. treat everything as just an example that needs further research. never execute something posted by someone else(*) unless you know what it does and how and why. (*) ANYONE else. even if they're trustworthy and not malicious, they could be wrong, they might have made a mistake. craig -- craig sanders ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
What time of the day is best for our Online Main Meeting?
We have an upcoming Main Meeting in a few days and it will be the first time we are running it online! Traditionally we would start at 7pm and wrap at around 9pm followed by dinner at a local restaurant. (feels like the past life!) However, now the event is online and almost all the reasons led to a 7pm start are invalid! Now the question is: *What time is best to start an Online Main Meeting*? Options we can consider are: *12pm - 2pm* *5pm - 7pm* *7pm - 9pm* *8pm - 10pm* Please let me know by replying to this email or contacting the committee at . Ideally we will settle on a time that works the best for most of our community, especially those who would previously find it difficult to attend in-person meetings due to distance or family commitment, etc. For that reason I would like to hear from anyone who has a preference, especially if: - you live inside the curfew zone. - you are a parent or a carer - you work between 9 to 5 (if that still is a thing for some?) - or for any other reason there is a limit on the range of hours you can attend online meetings. It's worth noting that the meeting will be accessible on a desktop browser and Android phones and iPhones. + Alexar -- [image: image.jpg] *Alexar Pendashteh* technologist / social entrepreneur https://github.com/pendashteh ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
Re: [MLUG] Advice needed about ZFS
On Wed, Aug 26, 2020 at 10:43:30AM +, stripes theotoky wrote: > > I would suggest looking at something like a Network Attached Storage > > device, with multiple drives in a suitable RAID array. > > This is the ultimate plan to build a NAS from an HP Microserver. I am > leaning towards Nas4Free on an SSD or internal USB and 3, 6TB mirrors. This > is a project that has to wait because right now due to Covid19 and > Brexit we are not sure where we are. I am here and can't leave but > expecting to be out of work (which won't stop my research), my husband is > British/Australian, resident in Austria to avoid Brexit but is stranded by > Covid in Greece. When it all settles down and we have a home again building > this NAS is going to be pretty high on the list of things to do. In the meantime, you can use a largish (>= 4 or 6 TB) external USB drive set up to be a ZFS pool for backups. Then 'zfs send' your snapshots to the USB drive, and keep a multi-year snapshot history on them. Aggressively expire the snapshots in your laptop to minimise the amount of space they're taking. You can have multiple USB backup drives like this - each one has to be initialised with a full backup, but can then be incrementally updated with newer snapshots. Each backup pool should have a different name - like backup1, backup2, etc. You can automate much of this with some good scripting, but your scripts will need to query the backup destination pool (with 'zfs list') to find out what the latest backup snapshot on it is. Incremental 'zfs send' updates send the difference between two snapshots, so you need to know what the lastest snapshot on the backup pool is AND that snapshot has to sill exist on the source pool. You should use a different snapshot naming scheme for the backup snapshots. If your main snapshots are "@zfs-autosnap-MMDD" or whatever, then use "@backup-MMDD". Create that snapshot, and use it for a full zfs send, then create new "@backup-MMDD" snapshots just before each incremental send. e.g. the initial full backup on a pool called "source" to a pool called "backup", if you had done it yesterday: zfs snapshot source@backup-20200829 zfs send -v -R source@backup-20200829 | /sbin/zfs receive -v -d -F backup and to do an incremental backup of *everything* (including all snapshots created manually or by zfs-autosnap) from @backup-20200829 to today between the same pools: # source@backup-20200829 already exists from the last backup, no need to create it. zfs snapshot source@backup-20200830 zfs send -R -i source@backup-20200829 source@backup-20200830 | zfs receive -v -u -d backup ** NOTE: @backup-20200829 has to exist on both the source & backup pools ** Unless you need to make multiple backups to different pools, you can delete the source@backup-20200829 snapshot at this point because the next backup will be from source@backup-20200830 to some future @backup-MMDD snapshot. BTW, you don't have to backup to the top level of the backup pool. e.g. to backup to a dataset called "mylaptop" on pool backup: zfs create backup/mylaptop zfs snapshot source@backup-20200829 zfs send -R -i source@backup-20200829 source@backup-20200830 | zfs receive -v -u -d backup/mylaptop (you'd do this if you wanted to backup multiple machines to the same backup drive. or if you wanted to use it for backups AND for storage of other stuff like images or videos or audio files). and, oh yeah, get used to using the '-n' aka '--dry-run' and '-v'/'--verbose' options with both 'zfs send' and 'zfs receive' until you understand how they work and are sure they're going to do what you want. NOTE: as a single drive vdev, there will be no redundancy in the USB backup drive. but I'm guessing that since you're using a laptop, it's probably also a single drive and that you're only using ZFS for the auto compression and snapshot capabilities. If you want redundancy, you can always plug in two USB drives at a time and set them up as a zfs mirrored pool, but then you have to label them so that you know which pairs of drives belong together This is not as good as a NAS but it's cheap and easy and a lot better than nothing. I recommend using USB drive adaptors that allow you to use any drives in them (i.e. USB to SATA adaptors), not pre-made self-contained external drives (just a box with a drive in it and a USB socket or cable). Sometimes you see them with names like "disk docking station", with a power adaptor, a USB socket, and SATA slots for 1, 2, or 4 drives. Other forms include plain cables with a USB plug on one end and a SATA socket on the other. craig ps: If your backup pool was on some other machine somewhere on the internet, you can pipe the zfs send over ssh. e.g. zfs send -R -i source@backup-20200829 source@backup-20200830 | ssh remote-host zfs receive -u
Re: LUV Wiki
On 29/8/20 7:00 pm, Russell Coker via luv-main wrote: I'm getting the LUV Wiki going again. Would anyone like to help test it? Russell If all you mean is looking over to see how it appears on screen, I'll have a quick read if you send the link. I'll probably read it carefully as well, but doubt I'll know tall stories if I see one. -- Keith Bainbridge keithrbaugro...@gmail.com or ke1thozgro...@gmx.com ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
LUV Wiki
I'm getting the LUV Wiki going again. Would anyone like to help test it? The Wiki has been broken for years because the old Drupal installation required an old version of PHP and a routine system upgrade had installed a new version of MediaWiki that needed a newer PHP. I have configured things to support multiple versions of PHP running at the same time. Also while I was at it I set up HTTP/2 and mod_pagespeed. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/ ___ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
